The OpenBSD 4.0 Release:
Released Nov 1, 2006
Copyright 1997-2006, Theo de Raadt.
What's New
How to install
How to upgrade
How to use the ports tree
Ordering a CD set
To get the files for this release:
- Order a CDROM from our ordering system.
- See the information on The FTP page for
a list of mirror machines.
- Go to the pub/OpenBSD/4.0/ directory on
one of the mirror sites.
- Briefly read the rest of this document.
- Have a look at The 4.0 Errata page for a list
of bugs and workarounds.
- See a detailed log of changes between the
3.9 and 4.0 releases.
Note: All applicable copyrights and credits can be found
in the applicable file sources found in the files src.tar.gz, sys.tar.gz,
XF4.tar.gz, or in the files fetched via ports.tar.gz. The distribution
files used to build packages from the ports.tar.gz file are not included on
the CDROM because of lack of space.
What's New
This is a partial list of new features and systems included in OpenBSD 4.0.
For a comprehensive list, see the changelog leading
to 4.0.
- New platforms:
- OpenBSD/armish.
Various ARM-based appliances, using the Redboot boot loader, currently only supporting the Thecus N2100 and IOData HDL-G.
- Improved hardware support, including:
- New msk(4) driver for Marvell/SysKonnect Yukon-2 Gigabit Ethernet.
- New bnx(4) driver for Broadcom NetXtreme II Gigabit Ethernet.
- New xge(4) driver for Neterion Xframe/Xframe II 10Gb Ethernet.
- New rum(4) driver for Ralink Technology 2nd gen USB IEEE 802.11a/b/g wireless.
- New acx(4) driver for Texas Instruments ACX100/ACX111 IEEE 802.11a/b/g wireless.
- New pgt(4) driver for Connexant/Intersil Prism GT Full-MAC IEEE 802.11a/b/g wireless.
- New uath(4) driver for Atheros USB IEEE 802.11a/b/g wireless.
- New binary blob free wpi(4) driver for Intel PRO/Wireless 3945ABG IEEE 802.11a/b/g wireless.
- New arc(4) driver for Areca Technology Corporation SATA RAID.
- New mfi(4) driver for LSI Logic & Dell MegaRAID SAS RAID.
- New azalia(4) driver for generic High Definition Audio.
- New SD/MMC/SDIO drivers (sdhc(4), sdmmc(4)), currently supporting SD memory cards as fake SCSI sd(4) drives.
- New udcf(4) driver for Gude ADS Expert mouseCLOCK DCF77/HBG time signal station receivers.
- New uslcom(4) driver for Silicon Laboratories CP2101/CP2102 based USB serial adapters.
- New ucycom(4) driver for Cypress microcontroller based USB serial adapters.
- New uark(4) driver for Arkmicro Technologies ARK3116 based USB serial adapters.
- New umsm(4) driver for Qualcomm MSM EVDO based modems.
- New Dallas/Maxim 1-Wire bus support, including:
- New gpioow(4) driver for 1-Wire bus bit-banging through GPIO pin
- New onewire(4) 1-Wire bus driver
- New owid(4) 1-Wire ID family driver
- New owtemp(4) 1-Wire temperature family driver
- New isagpio(4) driver for ISA I/O mapped as GPIO.
- New nmea(4)
line discipline for NMEA 0183 (GPS) devices. The new
nmeaattach(8)
utility can be used to receive NMEA 0183 data and provide the time
received as a timedelta sensor to be used by, for example,
ntpd(8).
- New VAX framebuffer drivers:
- New lcg(4) driver for VAXstation 4000/60 and VLC color frame buffers
- New lcspx(4) driver for Low-Cost SPX color frame buffers
- New gpx(4) driver for GPX color frame buffers
- smg(4) driver for Small Monochrome Graphics frame buffers heavily updated to be a modern wscons(4) driver
- New vxtbus(4) support for VAX VXT2000 bus.
- New led(4) VAX LED driver
- The bge(4) driver supporting newer chipsets, such as the Broadcom BCM5754, BCM5755, BCM5786, and BCM5787.
- The em(4) driver supporting newer chipsets, such as the Intel ESB2 and ICH8.
- The nfe(4) driver supporting newer chipsets, such as the NVIDIA MCP61 and MCP65.
- The re(4) driver supporting newer chipsets, such as the Realtek RT8101E, RT8168, and RT8169SC.
- The dc(4) driver supporting newer chipsets, such as the ADMtek ADM9511 and ADM9513.
- The pciide(4) driver supporting newer chipsets, such as:
- ATI IXP300 SATA, IXP600 IDE
- Intel 6321ESB IDE/SATA, 82801G SATA, and 82801H SATA
- IT Express IT8211F IDE
- NVIDIA MCP61 SATA, MCP65 SATA
- Promise PDC205xx SATA
- ServerWorks SATA
- VIA VT8237A SATA
- The mpt(4) driver has been replaced with mpi(4), a more stable driver that supports more hardware.
- Working interrupt routing on Sun Netra t1 105, Ultra 60 and possibly other sparc64 systems.
- Work around broken VIA and NVIDIA MPBIOSes, fixes interrupt routing with GENERIC.MP on several systems.
- Initial bio(4) support for Compaq/HP ciss(4) Smart ARRAY 5/6 SAS/SCSI RAID controllers.
- UltraSPARC III based sparc64 machines are now supported!
- Support for the Zaurus SL-C3200 in OpenBSD/zaurus.
- New tools:
- GNU RCS has been replaced with OpenRCS.
- New functionality:
- ipsecctl(8) has been greatly extended and completely supersedes ipsecadm(8).
- ftp(1) now supports HTTPS.
- cdio(1) can now perform track-at-once burning and rewritable blanking.
- spppcontrol(8) and wicontrol(8) functionality has been merged into
ifconfig(8).
- gcc(1) provides a new warning, -Wstack-larger-than-N, to report functions
which are too greedy in stack variables, see
gcc-local(1) for details.
- An in-kernel getcwd(3) implementation.
- A new system call adjfreq(2)
to allow ntpd(8)
to adjust the tick rate of the system clock automatically.
- Support for X11 on VAX has been added
- Virtual Allocation Table (VAT) support for UDF.
- C99 functions
round(3),
roundf(3),
trunc(3), and
truncf(3)
have been added to libm, the math library.
- pf(4)
now supports Unicast Reverse Path Forwarding (uRPF) checks for simplified
ingress filtering.
- bpf(4)
can now ignore packets based on their direction (inbound/outbound) using the
BIOCSDIRFILT ioctl.
- pdisk(8)
can now set up slices on HFS(DPME) partitioned disks on mac68k.
- sasyncd(8)
communicates with its
isakmpd(8),
telling it to run active or passive. This makes IPsec failover setups much more robust.
- Assorted improvements and code cleanup:
- Much better time keeping for multiprocessor OpenBSD/i386
systems.
- Much improved implementation of telldir(3)
and friends.
- Replacement of all
malloc(3)
calls that follow a pattern prone to integer overflow with safer constructs.
- Improved failover handling in
carp(4):
- Extend the carp protocol with the demotion counter to act smarter on multiple failures.
- Group failovers now work without carp running preempt mode.
- Demotion can now be controlled via interface groups.
- OpenSSH 4.4:
- Conditional configuration in sshd_config(5) using the Match directive. This allows some
configuration options to be selectively overridden if specific criteria
(based on user, group, hostname and/or address) are met.
- Add support for Diffie-Hellman group exchange key agreement with a
final hash of SHA256.
- Added a ForceCommand directive to sshd_config(5), similar to the command="..." option in
~/.ssh/authorized_keys.
- Added a PermitOpen directive to sshd_config(5), similar to the permitopen="..." option in
authorized_keys, to allow control over the port-forwardings that a
user is allowed to establish.
- Added an ExitOnForwardFailure option to cause ssh(1) to exit (with
a non-zero exit code) when requested port forwardings could not be
established.
- Added optional logging of transactions to sftp-server(8).
- ssh(1) will now record port numbers for hosts stored in
~/.ssh/authorized_keys when a non-standard port has been requested.
- Extended the sshd_config(5) "SubSystem" directive to allow the
specification of commandline arguments.
- Many manpage fixes and improvements
- OpenBGPD 4.0:
- new nexthop selection logic ignoring bgpd routes, helps in complex setups
with ospfd
- add a "detailed" show rib view to bgpctl, including communities
- allow requesting a route refresh from a peer that supports it
- have bgpd always report back the result of an operation to bgpctl, so
the operator can spot errors quicker
- allow bgpd to manipulate carp demotion counters based on session states,
gives even greater failover support
- support restarting sessions that reached max-prefix after a given time
- bgpctl can now show all routes received from a neighbor before filters
were applied, and routes sent to neighbors
- assorted fixes and improvements, as usual
- OpenOSPFD 4.0:
- Track uptime of the daemon itself.
- Track uptime of all ospf enabled interfaces.
- Adjust logging behaviour to prevent unwanted logging.
- Delay LSA updates when removing and adding - prevent flapping.
- Fix plaintext authentication.
- Improve the output of 'ospfctl show interfaces'.
- Support rtlabels when redistributing routes.
- OpenNTPD 4.0:
- support timedelta sensors, such as DCF77 receivers supported by
udcf(4)
and GPS receivers supported by
nmea(4).
- Adjust the kernel tick frequency, using
adjfreq(3),
improving accuracy on many machines.
- allow for weight to be added to sensors or servers, so that one can
weight timedelta sensors higher than ntp peers
- Over 3700 ports, 3400 pre-built packages, improved package tools.
- As usual, steady improvements in manual pages and other documentation.
- The system includes the following major components from outside suppliers:
- X.Org 6.9.0 (+ patches, and i386 contains XFree86 3.3.6 servers
(+ patches) for legacy chipsets not supported by X.Org)
- Gcc 2.95.3
(+ patches)
and 3.3.5
(+ patches)
- Perl 5.8.8 (+ patches)
- Apache 1.3.29, mod_ssl 2.8.16, DSO support (+ patches)
- OpenSSL 0.9.7j (+ patches)
- Groff 1.15
- Sendmail 8.13.8, with libmilter
- Bind 9.3.2-P1 (+ patches)
- Lynx 2.8.5rel.4 with HTTPS and IPv6 support (+ patches)
- Sudo 1.6.8p9
- Ncurses 5.2
- Latest KAME IPv6
- Heimdal 0.7.2 (+ patches)
- Arla 0.35.7
- Binutils 2.15 (+ patches)
- Gdb 6.3
How to install
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.
Please refer to the following files on the three CDROMs or FTP mirror for
extensive details on how to install OpenBSD 4.0 on your machine:
- CD1:4.0/i386/INSTALL.i386
- CD2:4.0/amd64/INSTALL.amd64
- CD2:4.0/macppc/INSTALL.macppc
- CD3:4.0/sparc/INSTALL.sparc
- CD3:4.0/sparc64/INSTALL.sparc64
- FTP:.../OpenBSD/4.0/alpha/INSTALL.alpha
- FTP:.../OpenBSD/4.0/armish/INSTALL.armish
- FTP:.../OpenBSD/4.0/cats/INSTALL.cats
- FTP:.../OpenBSD/4.0/hp300/INSTALL.hp300
- FTP:.../OpenBSD/4.0/hppa/INSTALL.hppa
- FTP:.../OpenBSD/4.0/luna88k/INSTALL.luna88k
- FTP:.../OpenBSD/4.0/mac68k/INSTALL.mac68k
- FTP:.../OpenBSD/4.0/mvme68k/INSTALL.mvme68k
- FTP:.../OpenBSD/4.0/mvme88k/INSTALL.mvme88k
- FTP:.../OpenBSD/4.0/sgi/INSTALL.sgi
- FTP:.../OpenBSD/4.0/vax/INSTALL.vax
- FTP:.../OpenBSD/4.0/zaurus/INSTALL.zaurus
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!
OpenBSD/i386:
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:4.0/i386/floppy40.fs to a floppy and boot via the floppy drive.
Use CD1:4.0/i386/floppyB40.fs instead for greater SCSI controller
support, or CD1:4.0/i386/floppyC40.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:4.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
FAQ 4.3.1.
OpenBSD/amd64:
The 4.0 release of OpenBSD/amd64 is located on CD2.
Boot from the CD to begin the install - you may need to adjust
your BIOS options first.
If you can't boot from the CD, you can create a boot floppy to install from.
To do this, write CD2:4.0/amd64/floppy40.fs to a floppy, then
boot from the floppy drive.
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.
OpenBSD/macppc:
Put 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
/4.0/macppc/bsd.rd
OpenBSD/sparc:
The 4.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.
ok boot cdrom 4.0/sparc/bsd.rd
or
> b sd(0,6,0)4.0/sparc/bsd.rd
If your SPARC system does not have a CD drive, you can alternatively boot from floppy.
To do so you need to write CD3:4.0/sparc/floppy40.fs to a floppy.
For more information see FAQ 4.3.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 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.
OpenBSD/sparc64:
Put CD3 in your CDROM drive and type boot cdrom.
If this doesn't work, or if you don't have a CDROM drive, you can write
CD3:4.0/sparc64/floppy40.fs or CD3:4.0/sparc64/floppyB40.fs
(depending on your machine) to a floppy and boot it with boot
floppy. Refer to INSTALL.sparc64 for details.
Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install
will most likely fail.
You can also write CD3:4.0/sparc64/miniroot40.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.
OpenBSD/alpha:
Write FTP:4.0/alpha/floppy40.fs or
FTP:4.0/alpha/floppyB40.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.
OpenBSD/armish:
OpenBSD/cats:
After updating the firmware to at least ABLE 1.95 if necessary, boot
FTP:4.0/cats/bsd.rd from an ABLE-supported device (such as a CD-ROM
or an existing FFS or EXT2FS partition).
OpenBSD/hp300:
OpenBSD/hppa:
OpenBSD/luna88k:
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.
OpenBSD/mac68k:
Boot MacOS as normal and extract the Macside "BSD/Mac68k Booter" utility from
FTP:4.0/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.
OpenBSD/mvme68k:
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.
OpenBSD/mvme88k:
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.
OpenBSD/sgi:
Burn cd40.iso on a CD-R, put it in the CD drive of your machine and
select Install System Software from the System Maintenance menu.
If your machine doesn't have a CD drive, you can
setup a DHCP/tftp network server, and boot using "bootp()/bsd.rd".
Refer to the instructions in INSTALL.sgi for more details.
OpenBSD/vax:
Boot over the network via mopbooting as described in INSTALL.vax.
OpenBSD/zaurus:
Using the Linux built-in graphical ipkg installer, install the
openbsd40_arm.ipk package. Reboot, then run it. Read INSTALL.zaurus
for a few important details.
Notes about the source code:
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
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.
How to upgrade
If you already have an OpenBSD 3.9 system, and do not want to reinstall,
upgrade instructions and advice can be found in the
Upgrade Guide.
Ports 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 anoncvs@server.openbsd.org:/cvs update -Pd -rOPENBSD_4_0
[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 4.0 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
$OpenBSD: 40.html,v 1.50 2006/09/17 16:58:57 henning Exp $