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