-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+What's New
+How to install
+How to use the ports tree
+Ordering a CD set
+
+
+
+This is a partial list of new features and systems included in OpenBSD 3.6. +For a comprehensive list, see the changelog leading +to 3.6. +
+ +
+ +
+ +
+ +
+ +
+ +
+ +
+ +
+
+ +
+ +
+
+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 +of) install are very similar; the CDROM instructions are left intact +so that you can see how much easier it would have been if you had +purchased a CDROM instead. +
+ +
+
+
+
+
+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! +
+ +
+Use CD1:3.6/i386/floppyB36.fs instead for greater scsi controller +support, or CD1:3.6/i386/floppyC36.fs for better laptop support. + +
+If you can't boot from a CD or a floppy disk, +you can install across the network using PXE as described in +the included INSTALL.i386 document. + +
+If you are planning on dual booting OpenBSD with another OS, you will need to +read INSTALL.i386. + +
+To make a boot floppy under MS-DOS, use the "rawrite" utility located +at CD1:3.6/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 +FAQ4.1. + + +
+
+
+If you can't boot from a CD or a floppy disk, +you can install across the network using PXE as described in the included +INSTALL.amd64 document. + +
+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.6/macppc/bsd.rd +
+
+ok boot cdrom 3.6/sparc/bsd.rd +or +> b sd(0,6,0)3.6/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.6/sparc/floppy36.fs to a floppy. +For more information see FAQ4.1. To boot from +the floppy use one of the two commands listed below, depending on the version of +your ROM. + +
+ok boot floppy +or +> b fd() ++ +
+Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install +will most likely fail. + +
+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. + + +
+
+If this doesn't work, or if you don't have a CDROM drive, you can write
+CD3:3.6/sparc64/floppy36.fs to a floppy and boot it with boot
+floppy.
+Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install
+will most likely fail.
+
+
+You can also write CD3:3.6/sparc64/miniroot36.fs to the swap partition on +the disk and boot with boot disk:b. + +
+If nothing works, you can boot over the network as described in INSTALL.sparc64 +
+
Write FTP:3.6/alpha/floppy36.fs or +FTP:3.6/alpha/floppyB36.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. + +
+
+After updating the firmware to at least ABLE 1.95 if necessary, boot +FTP:3.6/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 partition your disk with the appropriate A/UX +configurations. Then, extract the Macside utilities from +FTP:3.6/mac68k/utils onto your hard disk. Run Mkfs to create your +filesystems on the A/UX partitions you just made. Then, use the +"BSD/Mac68k Installer" to copy all the sets in FTP:3.6/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.
+
+
+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.
+
+
+
+# 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 ++
+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 ++
+The ports/ subdirectory is a checkout of the OpenBSD ports tree. Go +read the ports page +if you know nothing about ports +at this point. This text is not a manual of how to use ports. +Rather, it is a set of notes meant to kickstart the user on the +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 +order to keep current with it, you must make the ports/ tree +available on a read-write medium and update the tree with a command +like: +
+
+# cd [portsdir]/; cvs -d anoncvsserver.openbsd.org:/cvs update -Pd -rOPENBSD_3_6 ++
+[Of course, you must replace the local directory and server name here +with the location of your ports collection and a nearby anoncvs +server.] +
+Note that most ports are available as packages through ftp. Updated +packages for the 3.6 release will be made available if problems arise. +
+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. +
+ +
www@openbsd.org