Annotation of www/25.html, Revision 1.5
1.1 deraadt 1: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML Strict//EN">
2: <html>
3: <head>
4: <title>OpenBSD 2.5 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 1999 by OpenBSD.">
11: </head>
12:
13: <BODY BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#24248E">
14:
1.4 deraadt 15: <img alt="[OpenBSD]" src="images/logo25.gif">
1.5 ! deraadt 16: <hr>
1.1 deraadt 17:
18: <p>
1.5 ! deraadt 19: <a href=images/openbsd25_cover.gif><img src=images/cd25-s.gif height=90></a>
1.1 deraadt 20: <h2><font color=#0000e0>The OpenBSD 2.5 Release:</font></h2>
21: <p>
22:
1.2 deraadt 23: Released May 19, 1999.<br>
24: Copyright 1997-1999, Theo de Raadt.
1.1 deraadt 25: <p>
26:
27: <a href=orders.html>To order a 2.5 CDROM, click here.</a>
28:
29: <h3><font color=#0000e0>
30: To get the files for this release:
31: <ul>
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>
1.3 deraadt 35: <font color=#e00000>ISBN 0-9683637-3-3</font>.
1.1 deraadt 36: <li>See the information on <a href=ftp.html>The FTP page</a> for
37: a list of mirror machines
38: <li>Go to the <font color=#e00000>pub/OpenBSD/2.5/</font> directory on
39: one of the mirror sites
40: <li>Briefly read the rest of this document.
41: <li>Have a look at <a href=errata.html>The 2.5 Errata page</a> for a list
42: of bugs and workarounds.
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 which you would have on a piece of
50: paper if you had purchased a CDROM set
51: from <a href=orders.html>http://www.OpenBSD.org/orders.html</a>,
52: instead of doing an alternate form of install. The instructions for
53: doing an ftp (or other style of) install are very similar; the CDROM
54: instructions are left intact so that you can see how much easier it
55: would have been if 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.5 on your machine:
60: <p>
61: <dl>
62: <li> CD1:2.5/i386/INSTALL.i386
63: <li> CD1:2.5/sparc/INSTALL.sparc
64: <li> CD1:2.5/powerpc/INSTALL.powerpc
65: <p>
66: <li> CD2:2.5/alpha/INSTALL.alpha
67: <li> CD2:2.5/amiga/INSTALL.amiga
68: <li> CD2:2.5/mac68k/INSTALL.mac68k
69: <li> CD2:2.5/hp300/INSTALL.hp300
70: <p>
71: <li>A pmax release is available on the ftp sites, but not on the CDs.
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.5/i386/floppy25.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>
87: To make a floppy under MS-DOS, use /2.5/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>
92: <h3><font color=#e00000>SPARC:</font></h3>
93: <p>
94: To boot off CD1, type "boot cdrom 2.5/sparc/bsd.rd", or
95: "b sd(0,6,0)2.5/sparc/bsd.rd" depending on your ROM version.
96: Alternatively, write CD1:2.5/sparc/floppy25.fs to a floppy and boot it
97: using "boot fd()" or "boot floppy" depending on your ROM version.
98: Finally, a third alternative is to write CD1:2.5/sparc/kc.fs and
99: CD1:2.5/sparc/inst.fs to two separate floppies. Then insert "kc.fs",
100: and boot as described above. As soon as the floppy drive ejects a
101: floppy, insert "inst.fs". Answer a bunch of questions. Reboot from
102: the "kc.fs" floppy. This time, when the floppy is ejected simply
103: re-insert "kc.fs" again and answer a different set of questions.
104: <p>
105: <h3><font color=#e00000>AMIGA:</font></h3>
106: <p>
107: Create BSD partitions according to INSTALL.amiga's preparation section.
108: Mount the CD2 under AmigaOS as device CD0: Next, execute the following
109: CLI command: "CD0:2.5/amiga/utils/loadbsd CD0:2.5/amiga/bsd.rd".
110: <p>
111: <h3><font color=#e00000>HP300:</font></h3>
112: <p>
113: You can boot over the network by following the instructions in
114: INSTALL.hp300.
115: <p>
116: <h3><font color=#e00000>ALPHA:</font></h3>
117: <p>
118: Your alpha must use SRM firmware (not ARC). If you have a CDROM, you
119: can try "boot -fi 2.5/alpha/bsd.rd dkaX" (use "show device" to find your
120: CDROM drive identifier). Otherwise, write CD2:2.5/alpha/floppy.fs to a
121: floppy and boot that by typing "boot dva0". If this fails, you can place
122: bsd.rd on some other device and boot it, or use the provided simpleroot.
123: <p>
124: <h3><font color=#e00000>MAC68K:</font></h3>
125: <p>
126: Boot MacOS as normal and partition your disk with the appropriate A/UX
127: configurations. Then, extract the Macside utilities from
128: CD1:2.5/mac68k/utils onto your hard disk. Run Mkfs to create your
129: filesystems on the A/UX partitions you just made. Then, use the
130: BSD/Mac68k Installer to copy all the sets in CD1:2.5/mac68k/ onto your
131: partitions. Finally, you will be ready to configure the BSD/Mac68k
132: Booter with the location of your kernel and boot the system.
133: <p>
134: <h3><font color=#e00000>NOTES ABOUT THE SOURCE CODE:</font></h3>
135: <p>
136: src.tar.gz contains a source archive starting at /usr/src. This file
137: contains everything you need except for the kernel sources, which are
138: in a separate archive. To extract:
139: <p>
140: <pre>
141: # mkdir -p /usr/src
142: # cd /usr/src
143: # tar xvfz /tmp/src.tar.gz
144: </pre>
145: <p>
146: srcsys.tar.gz contains a source archive starting at /usr/src/sys.
147: This file contains all the kernel sources you need to rebuild kernels.
148: To extract:
149: <p>
150: <pre>
151: # mkdir -p /usr/src/sys
152: # cd /usr/src
153: # tar xvfz /tmp/srcsys.tar.gz
154: </pre>
155: <p>
156: Both of these trees are a regular CVS checkout. Using these trees it
157: is possible to get a head-start on using the anoncvs servers as
158: described at <a href=anoncvs.html>http://www.OpenBSD.org/anoncvs.html</a>.
159: Using these files
160: results in a much faster initial CVS update than you could expect from
161: a fresh checkout of the full OpenBSD source tree.
162: <p>
163: <hr>
164: <p>
165: <h3><font color=#e00000>PORTS TREE</font></h3>
166: <p>
167: A ports tree archive is also provided. To extract:
168: <p>
169: <pre>
170: # cd /usr
171: # tar xvfz /tmp/ports.tar.gz
172: # cd ports
173: # ls
174: ...
175: </pre>
176: <p>
177: The ports/ subdirectory is a checkout of the OpenBSD ports tree. Go
178: read <a href=ports.html>http://www.OpenBSD.org/ports.html</a>
179: if you know nothing about ports
180: at this point. This text is not a manual of how to use ports.
181: Rather, it is a set of notes meant to kickstart the user on the
182: OpenBSD ports system.
183: <p>
184: Certainly, the OpenBSD ports system is not complete. This is because
185: the full integration of ports into the OpenBSD environment is still a
186: young project as of this release. We believe the ports that are
187: provided here are stable, but it is most important to realize that
188: ports will continue to grow a great deal in functionality in the
189: future.
190: <p>
191: As we said, ports will be growing a lot in the future. The ports/
192: directory represents a CVS (see the manpage for cvs(1) if you aren't
193: familiar with CVS) checkout of our ports. As with our complete source
194: tree, our ports tree is available via anoncvs. So, in
195: order to keep current with it, you must make the ports/ tree
196: available on a read-write medium and update the tree with a command
197: like:
198: <p>
199: <pre>
200: # cd [portsdir]/; cvs -d anoncvsserver.openbsd.org:/cvs update -PAd
201: </pre>
202: <p>
203: [Of course, you must replace the local directory and server name here
204: with the location of your ports collection and a nearby anoncvs
205: server.]
206: <p>
207: Again, it is important to see the webpage for specific instructions as
208: this is a new service which hasn't yet been ironed out
209: completely.
210: <p>
211: Finally, despite ports' youth, help is never far. If you're
212: interested in seeing a port added, would like to help out, or just
213: would like to know more, the mailing list ports@openbsd.org is a good
214: place to know.