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