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