=================================================================== RCS file: /cvsrepo/anoncvs/cvs/www/32.html,v retrieving revision 1.47 retrieving revision 1.48 diff -u -r1.47 -r1.48 --- www/32.html 2019/04/24 15:54:53 1.47 +++ www/32.html 2019/05/27 22:55:18 1.48 @@ -1,30 +1,41 @@ - - -
+ + + +
-
- + + |
Released November 1, 2002 Copyright 1997-2002, Theo de Raadt. -ISBN 0-9731791-0-4 +ISBN 0-9731791-0-4 3.2 Song: "Goldflipper" @@ -32,7 +43,7 @@
|
-
This is a partial list of new features and systems included in OpenBSD 3.2. For a comprehensive list, see the changelog leading to 3.2. @@ -100,7 +112,7 @@
@@ -142,12 +154,14 @@ print in the complete changelog).
-
Following this are the instructions which you would have on a piece of paper if you had purchased a CDROM set instead of doing an alternate form of install. The instructions for doing an ftp (or other style @@ -172,14 +186,16 @@
Quick installer information for people familiar with OpenBSD, and the use of the "disklabel -E" command. If you are at all confused when installing OpenBSD, read the relevant INSTALL.* file as listed above! -
-
Play with your BIOS options to enable booting from a CD. The OpenBSD/i386 release is on CD1. If your BIOS does not support booting from CD, you will need to create a boot floppy to install from. To create a boot floppy write @@ -194,68 +210,64 @@
To make a boot floppy under MS-DOS, use the "rawrite" utility located -at CD:/3.2/tools/rawrite.exe. To make the boot floppy under a Unix OS, use the dd(1) utility. The following is an example usage of dd(1), where the device could be "floppy", "rfd0c", or "rfd0a". +at CD:/3.2/tools/rawrite.exe. To make the boot floppy under a Unix OS, use the dd(1) utility. The following is an example usage of dd(1), where the device could be "floppy", "rfd0c", or "rfd0a". -
+# dd if=<file> of=/dev/<device> bs=32k -+
Make sure you use properly formatted perfect floppies with NO BAD BLOCKS or your install will most likely fail. For more information on creating a boot floppy and installing OpenBSD/i386 please refer to this page. - +
-
If you can't boot from CDROM, write CD1:3.2/alpha/floppy32.fs or +
+If you can't boot from CDROM, write CD1:3.2/alpha/floppy32.fs or CD1:3.2/alpha/floppyB32.fs (depending on your machine) to a diskette and enter boot dva0. Refer to INSTALL.alpha for more details.
Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install will most likely fail. -
-
Alternatively, at the Open Firmware prompt, enter boot cd:,ofwboot /3.2/macppc/bsd.rd -
-
-
-> boot cdrom 3.2/sparc/bsd.rd ++> boot cdrom 3.2/sparc/bsd.rd or -> b sd(0,6,0)3.2/sparc/bsd.rd -+> b sd(0,6,0)3.2/sparc/bsd.rd +
If your sparc does not have a CD drive, you can alternatively boot from floppy. To do so you need to write "CD3:3.2/sparc/floppy32.fs" to a floppy. For more information see this page. To boot from the floppy use one of the two commands listed below, depending on the version of your ROM. -
-> boot floppy ++> boot floppy or > boot fd() -+
Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install will most likely fail. @@ -264,11 +276,10 @@ If your sparc doesn't have a floppy drive nor a CD drive, you can either setup a bootable tape, or install via network, as told in the INSTALL.sparc file. - +
-
@@ -283,51 +294,57 @@
If nothing works, you can boot over the network as described in INSTALL.sparc64 -
-
++# mkdir -p /usr/src +# cd /usr/src +# tar xvfz /tmp/src.tar.gz +
-
-# mkdir -p /usr/src -# cd /usr/src -# tar xvfz /tmp/src.tar.gz --
srcsys.tar.gz contains a source archive starting at /usr/src/sys. This file contains all the kernel sources you need to rebuild kernels. To extract: + +
++# mkdir -p /usr/src/sys +# cd /usr/src +# tar xvfz /tmp/srcsys.tar.gz +
-
-# mkdir -p /usr/src/sys -# cd /usr/src -# tar xvfz /tmp/srcsys.tar.gz --
Both of these trees are a regular CVS checkout. Using these trees it is possible to get a head-start on using the anoncvs servers as described at http://www.OpenBSD.org/anoncvs.html. Using these files results in a much faster initial CVS update than you could expect from a fresh checkout of the full OpenBSD source tree. -
-
A ports tree archive is also provided. To extract:
-
-# cd /usr -# tar xvfz /tmp/ports.tar.gz -# cd ports -+
+# cd /usr +# tar xvfz /tmp/ports.tar.gz +# cd ports +
The ports/ subdirectory is a checkout of the OpenBSD ports tree. Go read http://www.OpenBSD.org/faq/faq15.html @@ -342,7 +359,7 @@ on most architectures (over 2000 packages build on i386, for instance).
The ports/ directory represents a CVS (see the manpage for - + cvs(1) if you aren't familiar with CVS) checkout of our ports. As with our complete source tree, our ports tree is available via anoncvs. So, in @@ -350,9 +367,9 @@ available on a read-write medium and update the tree with a command like:
-
+# cd [portsdir]/; cvs -d anoncvs@server.openbsd.org:/cvs update -Pd -rOPENBSD_3_2 -+
[Of course, you must replace the local directory and server name here with the location of your ports collection and a nearby anoncvs @@ -364,7 +381,4 @@ If you're interested in seeing a port added, would like to help out, or just would like to know more, the mailing list ports@openbsd.org is a good place to know. -
- - - +