=================================================================== RCS file: /cvsrepo/anoncvs/cvs/www/34.html,v retrieving revision 1.64 retrieving revision 1.65 diff -u -r1.64 -r1.65 --- www/34.html 2019/04/24 15:54:53 1.64 +++ www/34.html 2019/05/27 22:55:18 1.65 @@ -1,31 +1,43 @@ - - -
+ + + +
-
- + + |
Released Nov 1, 2003 Copyright 1997-2003, Theo de Raadt. -ISBN 0-9731791-2-0 +ISBN 0-9731791-2-0 3.4 Song: "The Legend of Puffy Hood" @@ -33,7 +45,7 @@
|
-
This is a partial list of new features and systems included in OpenBSD 3.4. For a comprehensive list, see the changelog leading to 3.4. @@ -59,7 +72,7 @@
@@ -69,7 +82,7 @@ effort limit on code execution.
-
@@ -142,13 +155,13 @@
@@ -157,55 +170,55 @@
@@ -220,7 +233,7 @@
@@ -310,12 +323,14 @@
-
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 @@ -345,14 +360,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 @@ -369,52 +386,49 @@
To make a boot floppy under MS-DOS, use the "rawrite" utility located at CD:/3.4/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. - +
-
Alternatively, at the Open Firmware prompt, enter boot cd:,ofwboot /3.4/macppc/bsd.rd -
-
-
-> boot cdrom 3.4/sparc/bsd.rd ++> boot cdrom 3.4/sparc/bsd.rd or -> b sd(0,6,0)3.4/sparc/bsd.rd -+> b sd(0,6,0)3.4/sparc/bsd.rd +
If your sparc does not have a CD drive, you can alternatively boot from floppy. @@ -423,11 +437,11 @@ the floppy use one of the two commands listed below, depending on the version of your ROM. -
-> boot floppy ++> boot floppy or -> boot fd() -+> boot fd() +
Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install @@ -437,11 +451,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. - +
-
@@ -457,12 +470,11 @@
If nothing works, you can boot over the network as described in INSTALL.sparc64 -
-
Write FTP:3.4/alpha/floppy34.fs or +Write FTP:3.4/alpha/floppy34.fs or FTP:3.4/alpha/floppyB34.fs (depending on your machine) to a diskette and enter boot dva0. Refer to INSTALL.alpha for more details. @@ -470,27 +482,20 @@ Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install will most likely fail. -
-
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. -
-
Boot MacOS as normal and partition your disk with the appropriate A/UX configurations. Then, extract the Macside utilities from FTP:3.4/mac68k/utils onto your hard disk. Run Mkfs to create your @@ -498,61 +503,65 @@ "BSD/Mac68k Installer" to copy all the sets in FTP:3.4/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.
-
-
++# 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. -
-
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 @@ -562,7 +571,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 @@ -570,9 +579,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_4 -+
+# cd [portsdir]/; cvs -d anoncvs@server.openbsd.org:/cvs update -Pd -rOPENBSD_3_4 +
[Of course, you must replace the local directory and server name here with the location of your ports collection and a nearby anoncvs @@ -584,7 +593,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. -
- - - +