Released December 1, 2001
Copyright 1997-2001, Theo de Raadt.
3.0 Song:"E-Railed (OpenBSD Mix)"
All applicable copyrights and credits are in the src.tar.gz,sys.tar.gz, xenocara.tar.gz, ports.tar.gz files, or in thefiles fetched via ports.tar.gz.
This is a partial list of new features and systems included in OpenBSD 3.0.For a comprehensive list, see thechangelog leadingto 3.0.
Following this are the instructions which you would have on a piece ofpaper if you had purchased a CDROM set instead of doing an alternateform of install. The instructions for doing an ftp (or other styleof) install are very similar; the CDROM instructions are left intactso that you can see how much easier it would have been if you hadpurchased a CDROM instead.
Quick installer information for people familiar with OpenBSD, and theuse of the "disklabel -E" command. If you are at all confused wheninstalling 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 writeCD1:3.0/i386/floppy30.fs to a floppy and boot via the floppy drive.
UseCD1:3.0/i386/floppyB30.fs instead for greater scsi controllersupport, orCD1:3.0/i386/floppyC30.fs for better laptop support.
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 atCD:/3.0/tools/rawrite.exe. To make the boot floppy under a Unix OS, use thedd(1) utility. The following is an example usage ofdd(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 tothis page.
At the SRM prompt, enterboot -fi 3.0/alpha/bsd.rd dka6 wheredka6is the short name for the CDROM drive (you can check withshow dev).
If you can't boot from CDROM, writeCD1:3.0/alpha/floppy30.fs orCD1:3.0/alpha/floppyB30.fs (depending on your machine) to a diskette andenterboot 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.
Put the CD2 in your CDROM drive and poweron your machine while holding down theC key until the display turns on and showsOpenBSD/macppc boot.
Alternatively, at the Open Firmware prompt, enterboot 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/3.0/macppc/bsd.rd.This command may not work on some older New World systems,iMac (Rev A - Rev C); on these machines it will be necessary tocopy the ofwboot and /3.0/macppc/bsd.rd to the first HFS partition onthe harddrive and boot usingboot hd:,OFWBOOT /bsd.rd.
Put the CD2 in your CDROM drive and press the spacebar during the poweronself-test. Enter the boot choice that corresponds toSYS_CDBOOT.
Alternatively, you can boot over the network by following the instructions inINSTALL.hp300.
Create BSD partitions according to INSTALL.amiga's preparation section.Mount the CD2 under AmigaOS as device CD0: Next, execute the followingCLI 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/UXconfigurations. Then, extract the Macside utilities fromCD2:3.0/mac68k/utils onto your hard disk. Run Mkfs to create yourfilesystems on the A/UX partitions you just made. Then, use theBSD/Mac68k Installer to copy all the sets in CD2:3.0/mac68k/ onto yourpartitions. Finally, you will be ready to configure the BSD/Mac68kBooter 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 theNIOTandNBO debugger commands. Follow the instructions in INSTALL.mvme68kfor 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.rdor>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 seethis page. To boot from the floppy use one of the two commands listed below, depending on the version of your ROM.
>boot floppyor>boot 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 eithersetup a bootable tape, or install via network, as told in theINSTALL.sparc file.
Put the CD3 in your CDROM drive and typeboot cdrom.
If this doesn't work, or if you don't have a CDROM drive, you can writeCD3:3.0/sparc64/floppy30.fs to a floppy and boot it withbootfloppy.
Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install will most likely fail.
You can also writeCD3:3.0/sparc64/miniroot30.fs to the swap partition onthe disk and boot withboot disk:b.
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 filecontains everything you need except for the kernel sources, which arein a separate archive. To extract:
#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
Both of these trees are a regular CVS checkout. Using these trees itis possible to get a head-start on using the anoncvs servers asdescribed athttp://www.OpenBSD.org/anoncvs.html.Using these filesresults in a much faster initial CVS update than you could expect froma 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
Theports/ subdirectory is a checkout of the OpenBSD ports tree. Goreadhttp://www.OpenBSD.org/faq/faq15.htmlif you know nothing about portsat 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 theOpenBSD ports system.
Certainly, the OpenBSD ports system is not complete. It is doubtful itwill ever be. However, it is growing very fast and getting more stable.Almost all ports provided with this release should build without problemson most architectures (over 1200 packages build on i386, for instance).
Theports/ directory represents a CVS (see the manpage forcvs(1) ifyou aren't familiar with CVS) checkout of our ports. As with our completesource tree, our ports tree is available via anoncvs. So, inorder to keep current with it, you must make theports/ treeavailable on a read-write medium and update the tree with a commandlike:
#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 herewith the location of your ports collection and a nearby anoncvsserver.]
Note that most ports are available as packages through ftp. Updatedpackages for the 3.0 release will be made available if problems arise.
If you're interested in seeing a port added, would like to help out, or justwould like to know more, the mailing list ports@openbsd.org is a goodplace to know.
