Annotation of www/25.html, Revision 1.2
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:
15: <img alt="[OpenBSD]" src="images/logo25.jpg">
16:
17: <p>
18: <h2><font color=#0000e0>The OpenBSD 2.5 Release:</font></h2>
19: <p>
20:
1.2 ! deraadt 21: Released May 19, 1999.<br>
! 22: Copyright 1997-1999, Theo de Raadt.
1.1 deraadt 23: <p>
24:
25: <hr>
26: <a href=orders.html>To order a 2.5 CDROM, click here.</a>
27: <a href=images/openbsd25_cover.gif>
28: To see a picture of the 2.5 CDROM, click here.</a>
29: <hr>
30:
31:
32: <h3><font color=#0000e0>
33: To get the files for this release:
34: <ul>
35: <li><strong>Order a CDROM from our ordering system.</strong>
36: If you want to try to get a bookstore local to you to carry it,
37: have them order<br>
38: <font color=#e00000>ISBN 0-9683637-2-5</font>.
39: <li>See the information on <a href=ftp.html>The FTP page</a> for
40: a list of mirror machines
41: <li>Go to the <font color=#e00000>pub/OpenBSD/2.5/</font> directory on
42: one of the mirror sites
43: <li>Briefly read the rest of this document.
44: <li>Have a look at <a href=errata.html>The 2.5 Errata page</a> for a list
45: of bugs and workarounds.
46: </ul>
47: </font></h3>
48:
49: All applicable copyrights and credits can be found in the applicable
50: file sources found in the files src.tar.gz and srcsys.tar.gz.
51: <p>
52: Following this are the instructions which you would have on a piece of
53: paper if you had purchased a CDROM set
54: from <a href=orders.html>http://www.OpenBSD.org/orders.html</a>,
55: instead of doing an alternate form of install. The instructions for
56: doing an ftp (or other style of) install are very similar; the CDROM
57: instructions are left intact so that you can see how much easier it
58: would have been if you had purchased a CDROM instead.
59: <p>
60: <hr>
61: Please refer to the following files on the two CDROM's for extensive
62: details on how to install OpenBSD 2.5 on your machine:
63: <p>
64: <dl>
65: <li> CD1:2.5/i386/INSTALL.i386
66: <li> CD1:2.5/sparc/INSTALL.sparc
67: <li> CD1:2.5/powerpc/INSTALL.powerpc
68: <p>
69: <li> CD2:2.5/alpha/INSTALL.alpha
70: <li> CD2:2.5/amiga/INSTALL.amiga
71: <li> CD2:2.5/mac68k/INSTALL.mac68k
72: <li> CD2:2.5/hp300/INSTALL.hp300
73: <p>
74: <li>A pmax release is available on the ftp sites, but not on the CDs.
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
85: CD; try using CD1. If not, write CD1:2.5/i386/floppy25.fs to a
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.5/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>SPARC:</font></h3>
96: <p>
97: To boot off CD1, type "boot cdrom 2.5/sparc/bsd.rd", or
98: "b sd(0,6,0)2.5/sparc/bsd.rd" depending on your ROM version.
99: Alternatively, write CD1:2.5/sparc/floppy25.fs to a floppy and boot it
100: using "boot fd()" or "boot floppy" depending on your ROM version.
101: Finally, a third alternative is to write CD1:2.5/sparc/kc.fs and
102: CD1:2.5/sparc/inst.fs to two separate floppies. Then insert "kc.fs",
103: and boot as described above. As soon as the floppy drive ejects a
104: floppy, insert "inst.fs". Answer a bunch of questions. Reboot from
105: the "kc.fs" floppy. This time, when the floppy is ejected simply
106: re-insert "kc.fs" again and answer a different set of questions.
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.5/amiga/utils/loadbsd CD0:2.5/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.5/alpha/bsd.rd dkaX" (use "show device" to find your
123: CDROM drive identifier). Otherwise, write CD2:2.5/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.5/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.5/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>NOTES ABOUT THE SOURCE CODE:</font></h3>
138: <p>
139: src.tar.gz contains a source archive starting at /usr/src. This file
140: contains everything you need except for the kernel sources, which are
141: in a separate archive. To extract:
142: <p>
143: <pre>
144: # mkdir -p /usr/src
145: # cd /usr/src
146: # tar xvfz /tmp/src.tar.gz
147: </pre>
148: <p>
149: srcsys.tar.gz contains a source archive starting at /usr/src/sys.
150: This file contains all the kernel sources you need to rebuild kernels.
151: To extract:
152: <p>
153: <pre>
154: # mkdir -p /usr/src/sys
155: # cd /usr/src
156: # tar xvfz /tmp/srcsys.tar.gz
157: </pre>
158: <p>
159: Both of these trees are a regular CVS checkout. Using these trees it
160: is possible to get a head-start on using the anoncvs servers as
161: described at <a href=anoncvs.html>http://www.OpenBSD.org/anoncvs.html</a>.
162: Using these files
163: results in a much faster initial CVS update than you could expect from
164: a fresh checkout of the full OpenBSD source tree.
165: <p>
166: <hr>
167: <p>
168: <h3><font color=#e00000>PORTS TREE</font></h3>
169: <p>
170: A ports tree archive is also provided. To extract:
171: <p>
172: <pre>
173: # cd /usr
174: # tar xvfz /tmp/ports.tar.gz
175: # cd ports
176: # ls
177: ...
178: </pre>
179: <p>
180: The ports/ subdirectory is a checkout of the OpenBSD ports tree. Go
181: read <a href=ports.html>http://www.OpenBSD.org/ports.html</a>
182: if you know nothing about ports
183: at this point. This text is not a manual of how to use ports.
184: Rather, it is a set of notes meant to kickstart the user on the
185: OpenBSD ports system.
186: <p>
187: Certainly, the OpenBSD ports system is not complete. This is because
188: the full integration of ports into the OpenBSD environment is still a
189: young project as of this release. We believe the ports that are
190: provided here are stable, but it is most important to realize that
191: ports will continue to grow a great deal in functionality in the
192: future.
193: <p>
194: As we said, ports will be growing a lot in the future. The ports/
195: directory represents a CVS (see the manpage for cvs(1) if you aren't
196: familiar with CVS) checkout of our ports. As with our complete source
197: tree, our ports tree is available via anoncvs. So, in
198: order to keep current with it, you must make the ports/ tree
199: available on a read-write medium and update the tree with a command
200: like:
201: <p>
202: <pre>
203: # cd [portsdir]/; cvs -d anoncvsserver.openbsd.org:/cvs update -PAd
204: </pre>
205: <p>
206: [Of course, you must replace the local directory and server name here
207: with the location of your ports collection and a nearby anoncvs
208: server.]
209: <p>
210: Again, it is important to see the webpage for specific instructions as
211: this is a new service which hasn't yet been ironed out
212: completely.
213: <p>
214: Finally, despite ports' youth, help is never far. If you're
215: interested in seeing a port added, would like to help out, or just
216: would like to know more, the mailing list ports@openbsd.org is a good
217: place to know.
![[BACK]](/icons/back.gif){kind=icon}
Return to 25.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www