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