Annotation of www/22.html, Revision 1.5
1.1 deraadt 1: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML Strict//EN">
2: <html>
3: <head>
4: <title>OpenBSD 2.2 Release</title>
5: <link rev=made href=mailto:www@openbsd.org>
6: <meta name="resource-type" content="document">
7: <meta name="description" content="the main OpenBSD page">
8: <meta name="keywords" content="openbsd,main">
9: <meta name="distribution" content="global">
10: <meta name="copyright" content="This document copyright 1996 by OpenBSD.">
11: </head>
12:
13: <BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#23238E">
14:
15: <img alt="[OpenBSD]" SRC="images/smalltitle.gif">
16:
17: <p>
18: <h2><font color=#0000e0>The OpenBSD 2.2 Release:</font></h2>
19: <p>
20:
21: Released sometime around December 1, 1997.<br>
22: Copyright 1997, Theo de Raadt.
23: <p>
24:
25: <h3><font color=#e00000>
26: To get the files for this release:
27: <ul>
28: <li>See the information on the <a href=ftp.html>The FTP page</a> for
29: a list of mirror machines
30: <li>Go to the <font color=#0000e0>pub/OpenBSD/2.2/</font> directory on
31: one of the mirror sites
32: <li>Briefly read the rest of this document.
1.4 weingart 33: <li>Have a look at <a href=errata.html>The Errata page</a> for a list of bugs
34: and workarounds.
1.1 deraadt 35: </ul>
36: </font></h3>
37:
38: All applicable copyrights and credits can be found in the applicable
39: file sources found in the files src.tar.gz and srcsys.tar.gz.
40: <p>
41: Following this are the instructions if you had purchased a CDROM set
1.3 deraadt 42: from <a href=orders.html>http://www.OpenBSD.org/orders.html</a>,
43: instead of attempting to do
1.1 deraadt 44: an alternate form of install. The instructions for doing an ftp (or
45: other style of) install are very similar; the CDROM instructions are
46: left intact so that you can see how much easier it would have been if
47: you had purchased a CDROM instead.
48: <p>
49: <hr>
50: Please refer to the following files on the two CDROM's for extensive
51: details on how to install OpenBSD 2.2 on your machine:
52: <p>
53: <dl>
54: <li> CD1:2.2/i386/INSTALL.i386
55: <li> CD1:2.2/arc/INSTALL.arc
56: <li> CD1:2.2/mac68k/INSTALL.mac68k
57: <li> CD1:2.2/pmax/INSTALL.pmax
58: <li> CD1:2.2/sparc/INSTALL.sparc
59: <li> CD1:2.2/mvme68k/INSTALL.mvme68k
60: <p>
61: <li> CD2:2.2/amiga/INSTALL.amiga
62: <li> CD2:2.2/hp300/INSTALL.hp300
63: <li> CD2:2.2/alpha/INSTALL.alpha
64: </dl>
65: <hr>
66: <p>
67: Quick installer information for people familiar with OpenBSD, and the
68: use of the new "disklabel -E" command. If you are at all confused when
69: installing OpenBSD, read the relevant INSTALL.* file as listed above!
70: <p>
71: <h3><font color=#e00000>i386:</font></h3>
72: <p>
73: Play with your BIOS options, and see if you can enable booting off a
74: CD; try using CD1. If not, write CD1:2.2/i386/floppy22.fs to a
75: floppy, then boot that. If you are mixing OpenBSD with another
76: operating system, you will surely need to read the INSTALL.i386
77: document.
78: <p>
1.5 ! weingart 79: To make a floppy under MS-DOS, use /2.2/tools/rawrite.exe. Under
! 80: Unix, use "dd if=<file> of=/dev/<device> bs=32k" (where device could
! 81: be "floppy" or "rfd0c" or "rfd0a"). Use properly formatted perfect
! 82: floppies with NO BAD BLOCKS or you will lose.
! 83: <p>
1.1 deraadt 84: <h3><font color=#e00000>ARC:</font></h3>
85: <p>
86: Using CD1, tell the BOOT ROM to load the file CD1:\2.2\arc\bsd.rd. If
1.5 ! weingart 87: that does not work, create a MS-DOS filesystem using your vendor's arc
1.1 deraadt 88: setup program, copy CD1:2.2/arc/bsd.rd to there and attempt to boot
89: it.
90: <p>
91: <h3><font color=#e00000>SPARC:</font></h3>
92: <p>
93: To boot off CD1, type "boot cdrom 2.2/sparc/bsd.rd", or
94: "b sd(0,6,0)2.2/sparc/bsd.rd" depending on your ROM version.
95: Alternatively, write CD1:2.2/sparc/floppy22.fs to a floppy and boot it
96: using "boot fd()" or "boot floppy" depending on your ROM version.
97: Finally, a third alternative is to write CD1:2.2/sparc/kc.fs and
98: CD1:2.2/sparc/inst.fs to two seperate floppies. Then insert "kc.fs",
99: and boot as described above. As soon as the floppy drive ejects a
100: floppy, insert "inst.fs". Answer a bunch of questions. Reboot from
101: the "kc.fs" floppy. This time, when the floppy is ejected simply
102: re-insert "kc.fs" again and answer a different set of questions.
103: <p>
104: <h3><font color=#e00000>PMAX:</font></h3>
105: <p>
106: Write the simpleroot22.fs onto the start of the disk using dd on another
107: machine. After moving the disk drive, use "boot -f rz(0,0,0)/bsd"
108: (2100/3100) or "boot 5/rz0a/bsd" (5000). Alternatively, install via
109: network as described in detail in INSTALL.pmax.
110: <p>
111: <h3><font color=#e00000>AMIGA:</font></h3>
112: <p>
113: Create BSD partitions according to INSTALL.amiga's preparation section.
114: Mount the CD2 under AmigaOS as device CD0: Next, execute the following
115: CLI command: "CD0:2.2/amiga/utils/loadbsd CD0:2.2/amiga/bsd.rd".
116: <p>
117: <h3><font color=#e00000>HP300:</font></h3>
118: <p>
119: You can boot over the network by following the instructions in
120: INSTALL.hp300.
121: <p>
122: <h3><font color=#e00000>ALPHA:</font></h3>
123: <p>
124: Your alpha must use SRM firmware (not ARC). If you have a CDROM, you
125: can try "boot -fi 2.2/alpha/bsd.rd dkaX" (use "show device" to find your
126: CDROM drive identifier). Otherwise, write CD2:2.2/alpha/floppy.fs to a
127: floppy and boot that by typing "boot dva0". If this fails, you can place
128: bsd.rd on some other device and boot it, or use the provided simpleroot.
129: <p>
130: <h3><font color=#e00000>MAC68K:</font></h3>
131: <p>
132: Boot MacOS as normal and partition your disk with the appropriate A/UX
133: configurations. Then, extract the Macside utilities from
134: CD1:2.2/mac68k/utils onto your hard disk. Run Mkfs to create your
135: filesystems on the A/UX partitions you just made. Then, use the
136: BSD/Mac68k Installer to copy all the sets in CD1:2.2/mac68k/ onto your
137: partitions. Finally, you will be ready to configure the BSD/Mac68k
138: Booter with the location of your kernel and boot the system.
139: <p>
140: <h3><font color=#e00000>MVME68K:</font></h3>
141: <p>
142: Theo has no real idea. In the rush to get everything else done, the
143: install stuff for the mvme68k was never completed. Enough pieces are
144: included so that a really skilled person could find a way to install
145: it; perhaps using netbooting. Good luck!
146: <hr>
147: <p>
148: <h3><font color=#e00000>NOTES ABOUT THE SOURCE CODE:</font></h3>
149: <p>
150: src.tar.gz contains a source archive starting at /usr/src. This file
151: contains everything you need except for the kernel sources, which are
152: in a seperate archive. To extract:
153: <p>
1.2 deraadt 154: <pre>
155: # mkdir -p /usr/src
156: # cd /usr/src
157: # tar xvfz /tmp/src.tar.gz
158: </pre>
1.1 deraadt 159: <p>
160: srcsys.tar.gz contains a source archive starting at /usr/src/sys.
161: This file contains all the kernel sources you need to rebuild kernels.
162: To extract:
163: <p>
1.2 deraadt 164: <pre>
165: # mkdir -p /usr/src/sys
166: # cd /usr/src/sys
167: # tar xvfz /tmp/srcsys.tar.gz
168: </pre>
1.1 deraadt 169: <p>
170: Both of these trees are a regular CVS checkout. Using these trees it
171: is possible to get a head-start on using the anoncvs servers as
1.3 deraadt 172: described at <a href=anoncvs.html>http://www.OpenBSD.org/anoncvs.html</a>.
173: Using these files
1.1 deraadt 174: results in a much faster initial CVS update than you could expect from
175: a fresh checkout of the full OpenBSD source tree.
176: <p>
177: <hr>
178: <p>
179: <h3><font color=#e00000>PORTS TREE</font></h3>
180: <p>
181: A ports tree archive is also provided. To extract:
182: <p>
1.2 deraadt 183: <pre>
184: # cd /usr
185: # tar xvfz /tmp/ports.tar.gz
186: # cd ports
187: # ls
188: ...
189: </pre>
1.1 deraadt 190: <p>
191: The ports/ subdirectory is a checkout of the OpenBSD ports tree. Go
1.3 deraadt 192: read <a href=ports.html>http://www.OpenBSD.org/ports.html</a>
193: if you know nothing about ports
1.1 deraadt 194: at this point. This text is not a manual of how to use ports.
195: Rather, it is a set of notes meant to kickstart the user on the
196: OpenBSD ports system.
197: <p>
198: Certainly, the OpenBSD ports system is not complete. This is because
199: the full integration of ports into the OpenBSD environment is a very
200: young project as of this release. We believe the ports that are
201: provided here are stable, but it is most important to realize that
202: ports will continue to grow a great deal in functionallity in the
203: future.
204: <p>
205: As we said, ports will be growing a lot in the future. The ports/
206: directory represents a CVS (see the manpage for cvs(1) if you aren't
207: familiar with CVS) checkout of our ports. As with our complete source
208: tree, we will soon be making ports available via anoncvs. So, in
209: order to keep current with the, you must make the ports/ tree
210: available on a read-write medium and update the tree with a command
211: like:
212: <p>
1.2 deraadt 213: <pre>
214: # cd [portsdir]/; cvs -d anoncvsserver.openbsd.org:/cvs update -PAd
215: </pre>
1.1 deraadt 216: <p>
217: [Of course, you must replace the local directory and server name here
218: with the location of your ports collection and a nearby anoncvs
219: server.]
220: <p>
221: Again, it's important to see the webpage for specific instructions as
222: this is a very new service which hasn't yet been ironed out
223: completely.
224: <p>
225: Finally, despite ports' youth, help is never far. If you're
226: interested in seeing a port added, would like to help out, or just
227: would like to know more, the mailing list ports@openbsd.org is a good
228: place to know.
![[BACK]](/icons/back.gif){kind=icon}
Return to 22.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www