=================================================================== RCS file: /cvsrepo/anoncvs/cvs/www/30.html,v retrieving revision 1.42 retrieving revision 1.43 diff -u -r1.42 -r1.43 --- www/30.html 2019/04/24 15:54:53 1.42 +++ www/30.html 2019/05/27 22:55:18 1.43 @@ -1,29 +1,41 @@ - - -
+ + + +
-
- + + |
Released December 1, 2001 Copyright 1997-2001, Theo de Raadt. -ISBN 0-9683637-8-4 +ISBN 0-9683637-8-4 3.0 Song: "E-Railed (OpenBSD Mix)" @@ -31,7 +43,7 @@
|
-
This is a partial list of new features and systems included in OpenBSD 3.0. For a comprehensive list, see the changelog leading to 3.0. @@ -77,7 +90,7 @@
@@ -102,14 +115,15 @@
+
-
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 @@ -138,14 +152,15 @@
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 CD1:3.0/i386/floppy30.fs to a floppy and boot via the floppy drive. @@ -157,20 +172,18 @@ If you are planning on dual booting OpenBSD with another OS, you will need to read the included INSTALL.i386 document.
-To make a boot floppy under MS-DOS, use the "rawrite" utility located at CD:/3.0/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". +To make a boot floppy under MS-DOS, use the "rawrite" utility located at CD:/3.0/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. - +
-
At the SRM prompt, enter boot -fi 3.0/alpha/bsd.rd dka6 where dka6 is the short name for the CDROM drive (you can check with show dev). @@ -181,18 +194,16 @@
Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install will most likely fail. -
-
Put the CD2 in your CDROM drive and poweron your machine while holding down the C key until the display turns on and shows OpenBSD/macppc boot.
Alternatively, at the Open Firmware prompt, enter boot cd:,ofwboot /3.0/macppc/bsd.rd +
Due to an error in how the CD was produced for the 3.0 Release, the following modified command should be used: boot cd:,OFWBOOT @@ -201,33 +212,27 @@ iMac (Rev A - Rev C); on these machines it will be necessary to copy the ofwboot and /3.0/macppc/bsd.rd to the first HFS partition on the harddrive and boot using boot hd:,OFWBOOT /bsd.rd. -
-
Put the CD2 in your CDROM drive and press the spacebar during the poweron self-test. Enter the boot choice that corresponds to SYS_CDBOOT.
Alternatively, you can boot over the network by following the instructions in INSTALL.hp300. -
-
Create BSD partitions according to INSTALL.amiga's preparation section. Mount the CD2 under AmigaOS as device CD0: Next, execute the following CLI command: "CD0:3.0/amiga/utils/loadbsd CD0:3.0/amiga/bsd.rd". -
-
Boot MacOS as normal and partition your disk with the appropriate A/UX configurations. Then, extract the Macside utilities from CD2:3.0/mac68k/utils onto your hard disk. Run Mkfs to create your @@ -235,45 +240,39 @@ BSD/Mac68k Installer to copy all the sets in CD2:3.0/mac68k/ onto your partitions. Finally, you will be ready to configure the BSD/Mac68k Booter with the location of your kernel and boot the system. -
-
You can create a bootable installation tape or boot over the network.
The network boot requires a MVME68K BUG version that supports the NIOT
and NBO debugger commands. Follow the instructions in INSTALL.mvme68k
for more details.
-
-
Boot over the network via mopbooting as described in INSTALL.vax. -
-
The 3.0 release of OpenBSD/sparc is located on CD3. To boot off of this CD you can use one of the two commands listed below, depending on the version of your ROM. -
-> boot cdrom 3.0/sparc/bsd.rd ++> boot cdrom 3.0/sparc/bsd.rd or -> b sd(0,6,0)3.0/sparc/bsd.rd -+> b sd(0,6,0)3.0/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.0/sparc/floppy30.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. @@ -282,12 +281,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. - +
-
Put the CD3 in your CDROM drive and type boot cdrom.
@@ -302,52 +299,57 @@
If nothing works, you can boot over the network as described in INSTALL.sparc64 -
-
src.tar.gz contains a source archive starting at /usr/src. This file contains everything you need except for the kernel sources, which are in a separate archive. To extract: + +
++# 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 @@ -362,7 +364,7 @@ on most architectures (over 1200 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 @@ -370,9 +372,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_0 -+
[Of course, you must replace the local directory and server name here with the location of your ports collection and a nearby anoncvs @@ -384,7 +386,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. -
- - - +