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