=================================================================== RCS file: /cvsrepo/anoncvs/cvs/www/37.html,v retrieving revision 1.85 retrieving revision 1.86 diff -u -r1.85 -r1.86 --- www/37.html 2019/04/24 15:54:53 1.85 +++ www/37.html 2019/05/27 22:55:18 1.86 @@ -1,30 +1,42 @@ - - -
+ + + +
-
- + + |
Released May 19, 2005 Copyright 1997-2005, Theo de Raadt. -ISBN 0-9731791-5-5 +ISBN 0-9731791-5-5 3.7 Song: "The Wizard of OS" @@ -32,7 +44,7 @@
|
-
This is a partial list of new features and systems included in OpenBSD 3.7. For a comprehensive list, see the changelog leading to 3.7. @@ -73,28 +86,28 @@
@@ -103,44 +116,44 @@
-
-
-
-
-
-
-
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 @@ -351,14 +366,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 @@ -380,32 +397,30 @@
To make a boot floppy under MS-DOS, use the "rawrite" utility located at CD1:3.7/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), +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 -+
+# 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 are planning to dual boot OpenBSD with another OS, you will need to read INSTALL.amd64. -
-
Alternatively, at the Open Firmware prompt, enter boot cd:,ofwboot /3.7/macppc/bsd.rd -
-
-ok boot cdrom 3.7/sparc/bsd.rd ++ok boot cdrom 3.7/sparc/bsd.rd or -> b sd(0,6,0)3.7/sparc/bsd.rd -+> b sd(0,6,0)3.7/sparc/bsd.rd +
If your SPARC system does not have a CD drive, you can alternatively boot from floppy. @@ -454,11 +467,11 @@ To boot from the floppy use one of the two commands listed below, depending on the version of your ROM. -
-ok boot floppy ++ok boot floppy or -> boot fd() -+> boot fd() +
Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install @@ -468,11 +481,10 @@ If your SPARC system 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. - +
-
@@ -488,12 +500,11 @@
If nothing works, you can boot over the network as described in INSTALL.sparc64 -
-
Write FTP:3.7/alpha/floppy37.fs or +Write FTP:3.7/alpha/floppy37.fs or FTP:3.7/alpha/floppyB37.fs (depending on your machine) to a diskette and enter boot dva0. Refer to INSTALL.alpha for more details. @@ -501,141 +512,128 @@ Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install will most likely fail. -
-
After updating the firmware to at least ABLE 1.95 if necessary, boot FTP:3.7/cats/bsd.rd from an ABLE-supported device (such as a CD-ROM or an existing FFS or EXT2FS partition). -
-
Boot over the network by following the instructions in INSTALL.hp300. -
-
Boot over the network by following the instructions in INSTALL.hppa or the hppa platform page. -
-
Copy bsd.rd to a Mach or UniOS partition, and boot it from the PROM. Alternatively, you can create a bootable tape and boot from it. Refer to the instructions in INSTALL.luna88k for more details. -
-
Boot MacOS as normal and extract the Macside "BSD/Mac68k Booter" utility from FTP:3.7/mac68k/utils onto your hard disk. Configure the "BSD/Mac68k Booter" with the location of your bsd.rd kernel and boot into the installer. Refer to the instructions in INSTALL.mac68k for more details. -
-
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.
-
-
You can create a bootable installation tape or boot over the network.
The network boot requires a MVME88K BUG version that supports the NIOT
and NBO debugger commands. Follow the instructions in INSTALL.mvme88k
for more details.
-
-
Setup a DHCP/tftp network server, and boot using "bootp()/bsd.rd". Refer to the instructions in INSTALL.sgi for more details. -
-
Using the Linux built-in graphical ipkg installer, install the openbsd37_arm.ipk package. Reboot, then run it. Read INSTALL.zaurus for a few important details. -
-
++# 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 --
sys.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/sys.tar.gz +
-
-# mkdir -p /usr/src/sys -# cd /usr/src -# tar xvfz /tmp/sys.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 here. 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. -
-
If you already have an OpenBSD 3.6 system, and do not want to reinstall, upgrade instructions and advice can be found in the Upgrade Guide. +
-
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 the ports page @@ -645,7 +643,7 @@ OpenBSD ports system.
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 @@ -653,9 +651,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_7 -+
+# cd [portsdir]/; cvs -d anoncvs@server.openbsd.org:/cvs update -Pd -rOPENBSD_3_7 +
[Of course, you must replace the local directory and server name here with the location of your ports collection and a nearby anoncvs @@ -667,7 +665,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. -
- - - +