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