29.html

<!doctype html>
<html lang=en id=release>
<meta charset=utf-8>

<title>OpenBSD 2.9</title>
<meta name="description" content="OpenBSD 2.9">
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="stylesheet" type="text/css" href="openbsd.css">
<link rel="canonical" href="https://www.openbsd.org/29.html">

<h2 id=OpenBSD>
<a href="index.html">
<i>Open</i><b>BSD</b></a>
2.9
</h2>

<table>
<tr>
<td>
<a href=images/Business.jpg>
<img src=images/Business.jpg alt="Business"></a>
<td>
Released June 1, 2001<br>
Copyright 1997-2001, Theo de Raadt.<br>
<cite class=isbn>ISBN 0-9683637-7-6</cite>

<ul>
<li>See the information on <a href="ftp.html">the FTP page</a> for
    a list of mirror machines.
<li>Go to the <code class=reldir>pub/OpenBSD/2.9/</code> directory on
    one of the mirror sites.
<li>Have a look at <a href="errata29.html">The 2.9 Errata page</a> for a list
    of bugs and workarounds.
<li>See a <a href=plus29.html>detailed log of changes</a> between the
    2.8 and 2.9 releases.
</ul>
<p>
All applicable copyrights and credits are in the src.tar.gz,
sys.tar.gz, xenocara.tar.gz, ports.tar.gz files, or in the
files fetched via <code>ports.tar.gz</code>.
</table>

<hr>

<section id=new>
<h3>What's New</h3>
<p>
This is a partial list of new features and systems included in OpenBSD 2.9.
For a comprehensive list, see the <a href=plus29.html>changelog</a> leading
to 2.9.

<ul>

<li>Filesystem performance has received an incredible boost from new softupdates and dirpref code. Some tests show a 60x improvement in filesystem speed. If there is one reason to upgrade to 2.9, this is it.
<p>

<li><a href="https://www.OpenSSH.com">OpenSSH</a> (supporting both the
SSH1 and SSH2 protocols) is now at version 2.9. Secure file transfers are
encouraged using the greatly enhanced SFTP subsystem which now comes both with
an SFTP server and client.
<p>

<li>Extensive changes to the documentation, notably the man pages and
the Web FAQ. The manual pages now include useful examples to
supplement the explanations.
<p>

<li>More complete collection and better tested set of "ports".
<p>

<li>Over 1000 pre-built and tested packages.
<p>

<li>OpenBSD 2.9 will run on the new Apple Titanium PowerBook G4.
<p>

<li>After a 2 release hiatus, the <a href="alpha.html">OpenBSD/alpha</a> port is back with more hardware support than ever!
<p>

<li>The system includes the following major components from outside suppliers:
<p>
<ul>
<li>XFree86 4.0.3 (and i386 contains 3.3.X servers also, thus providing support for all chipsets)
<li>gcc 2.95.3 (+ patches)
<li>perl 5.6.0 (+ patches)
<li>Apache 1.3.19, mod_ssl 2.8.2, OpenSSL 0.9.6 (+ patches), DSO support
<li>ipf 3.4.16 (+ patches)
<li>groff 1.15
<li>sendmail 8.11.3
<li>lynx 2.8.2 with HTTPS support added
<li>sudo 1.6.3p7
<li>ncurses 5.2
<li>Latest KAME IPv6
<li>KTH Kerberos 1.0.4
<li>OpenSSH 2.9

</ul>
<p>

<li>Much improved device driver support
<p>
<ul>
<li>3Com 3c990 3XP Typhoon/Sidewinder driver (Ethernet only).
<li>New hardware RAID drivers including:
	<ul>
	<li>Adaptec FSA
	<li>American Megatrends MegaRAID
	<li>Compaq Smart ARRAY controllers
	</ul>
<li>New SCSI drivers supporting:
	<ul>
	<li>Initio 940/950
	<li>Symbios Logic 53c1x10
	<li>AMD Am53c974-based PCI adapters
	</ul>
<li>Much added support for various laptop audio cards, including:
	<ul>
	<li>ESS Maestro 1/2/2E
	<li>Yamaha DS-1S
	<li>Cirrus Logic CS4281 audio devices
	</ul>
<li>USB hardware is now enabled by default and includes support for keyboards and mice.
</ul>
<p>

<li>Many improvements for security and reliability (look for the red
print in the <a href=plus29.html>complete changelog</a>).
<p>

<li>Many other new features, including:
<p>
<ul>
<li>Long username support.
<li>Vastly improved Linux <a href="https://man.openbsd.org/compat_linux.8">emulation</a> allowing many more applications to run.
<li>802.1d spanning tree support for <a href="https://man.openbsd.org/bridge.4">bridge(4)</a>.
<li><a href="https://man.openbsd.org/vlan.4">vlan(4)</a> bridging support allows for many more bridge possibilities (Now you can even use OpenBSD as an 802.1Q compatible switch)
<li><a href="https://man.openbsd.org/kqueue.2">kqueue(2)</a> kernel event notification mechanism.
<li>Addition of the <a href="https://man.openbsd.org/wscons.4">wscons(4)</a> machine-independent console driver.
<li>Major enhancements to softupdates, including speed and stability fixes.
<li>Bug-fixes and enhancements to the <a href="https://man.openbsd.org/atapiscsi.4">atapiscsi(4)</a> and <a href="https://man.openbsd.org/pciide.4">pciide(4)</a> drivers,
including UltraDMA/100 support for Intel, Promise, and Highpoint controllers.
</ul>

</ul>
</section>

<hr>

<section id=install>
<h3>How to install</h3>
<p>
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.

<hr>
Please refer to the following files on the two CDROMs for extensive
details on how to install OpenBSD 2.9 on your machine:

<ul>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/2.9/i386/INSTALL.i386">
	.../OpenBSD/2.9/i386/INSTALL.i386 (on CD1)</a>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/2.9/powerpc/INSTALL.powerpc">
	.../OpenBSD/2.9/powerpc/INSTALL.powerpc (on CD1)</a>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/2.9/vax/INSTALL.vax">
	.../OpenBSD/2.9/vax/INSTALL.vax (on CD1)</a>
<p>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/2.9/sparc/INSTALL.sparc">
	.../OpenBSD/2.9/sparc/INSTALL.sparc (on CD2)</a>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/2.9/mvme68k/INSTALL.mvme68k">
	.../OpenBSD/2.9/mvme68k/INSTALL.mvme68k (on CD2)</a>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/2.9/amiga/INSTALL.amiga">
	.../OpenBSD/2.9/amiga/INSTALL.amiga (on CD2)</a>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/2.9/mac68k/INSTALL.mac68k">
	.../OpenBSD/2.9/mac68k/INSTALL.mac68k (on CD2)</a>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/2.9/hp300/INSTALL.hp300">
	.../OpenBSD/2.9/hp300/INSTALL.hp300 (on CD2)</a>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/2.9/sun3/INSTALL.sun3">
	.../OpenBSD/2.9/sun3/INSTALL.sun3 (on CD2)</a>
<p>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/2.9/alpha/INSTALL.alpha">
	.../OpenBSD/2.9/alpha/INSTALL.alpha</a>
</ul>
</section>

<hr>

<section id=quickinstall>

<p>
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!

<h3>OpenBSD/i386:</h3>

<p>
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 <i>CD1:2.9/i386/floppy29.fs</i> to a floppy and boot via the floppy drive.

<p>
If you are planning on dual booting OpenBSD with another OS, you will need to read the included INSTALL.i386 document.

<p>
To make a boot floppy under MS-DOS, use the &quot;rawrite&quot; utility located at <i>CD:/2.9/tools/rawrite.exe</i>. To make the boot floppy under a Unix OS, use the <a href="https://man.openbsd.org/dd.1">dd(1)</a> utility. The following is an example usage of <a href="https://man.openbsd.org/dd.1">dd(1)</a>, where the device could be &quot;floppy&quot;, &quot;rfd0c&quot;, or &quot;rfd0a&quot;.

<blockquote><pre>
# <kbd>dd if=&lt;file&gt; of=/dev/&lt;device&gt; bs=32k</kbd>
</pre></blockquote>

<p>
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 <a href="faq/faq4.html#4.1">FAQ4.1</a>.

<h3>OpenBSD/sparc:</h3>

<p>
The 2.9 release of OpenBSD/sparc is located on CD2. To boot off of this CD you can use one of the two commands listed below, depending on the version of your ROM.

<blockquote><pre>
> <kbd>boot cdrom 2.9/sparc/bsd.rd</kbd>
or
> <kbd>b sd(0,6,0)2.9/sparc/bsd.rd</kbd>
</pre></blockquote>

<p>
If your sparc does not have a CD drive, you can alternatively boot from floppy. To do so you need to write &quot;CD2:2.9/sparc/floppy29.fs&quot; to a floppy. For more information see <a href="faq/faq4.html#4.1">FAQ4.1</a>. To boot from the floppy use one of the two commands listed below, depending on the version of your ROM.

<blockquote><pre>
> <kbd>boot floppy</kbd>
or
> <kbd>boot fd()</kbd>
</pre></blockquote>

<p>
Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install will most likely fail.

<p>
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.

<h3>OpenBSD/amiga:</h3>

<p>
Create BSD partitions according to INSTALL.amiga's preparation section.
Mount the CD2 under AmigaOS as device CD0: Next, execute the following
CLI command: "CD0:2.9/amiga/utils/loadbsd CD0:2.9/amiga/bsd.rd".

<h3>OpenBSD/hp300:</h3>

<p>
You can boot over the network by following the instructions in
INSTALL.hp300.

<h3>OpenBSD/mac68k:</h3>

<p>
Boot MacOS as normal and partition your disk with the appropriate A/UX
configurations.  Then, extract the Macside utilities from
CD2:2.9/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 CD2:2.9/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.

<h3>OpenBSD/sun3:</h3>

<p>
You can either setup a diskless boot or create an installation tape,
as described in INSTALL.sun3.

<h3>OpenBSD/alpha:</h3>

<p>
Get the release via ftp. Then, you can either setup a diskless boot or boot via floppy as described in INSTALL.alpha.
</section>

<hr>

<section id=sourcecode>
<h3>Notes about the source code</h3>
<p>
<code>src.tar.gz</code> contains a source archive starting at <code>/usr/src</code>.
This file contains everything you need except for the kernel sources, which are
in a separate archive.  To extract:
<blockquote><pre>
# <kbd>mkdir -p /usr/src</kbd>
# <kbd>cd /usr/src</kbd>
# <kbd>tar xvfz /tmp/src.tar.gz</kbd>
</pre></blockquote>
<p>
<code>sys.tar.gz</code> contains a source archive starting at <code>/usr/src/sys</code>.
This file contains all the kernel sources you need to rebuild kernels.
To extract:
<blockquote><pre>
# <kbd>mkdir -p /usr/src/sys</kbd>
# <kbd>cd /usr/src</kbd>
# <kbd>tar xvfz /tmp/srcsys.tar.gz</kbd>
</pre></blockquote>
<p>
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 <a href="anoncvs.html">here</a>.
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.
</section>

<hr>

<section id=ports>
<h3>Ports Tree</h3>
<p>
A ports tree archive is also provided.  To extract:
<blockquote><pre>
# <kbd>cd /usr</kbd>
# <kbd>tar xvfz /tmp/ports.tar.gz</kbd>
</pre></blockquote>
<p>
The <i>ports/</i> subdirectory is a checkout of the OpenBSD ports tree.  Go
read <a href="faq/faq15.html">https://www.OpenBSD.org/faq/faq15.html</a>
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.
<p>
Certainly, the OpenBSD ports system is not complete.  It is doubtful it
will ever be. However, it is growing very fast and getting more stable.
Almost all ports provided with this release should build without problems
on most architectures (over 1200 packages build on i386, for instance).
<p>
The <i>ports/</i> directory represents a CVS (see the manpage for
<a href="https://man.openbsd.org/cvs.1">cvs(1)</a> 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 <i>ports/</i> tree
available on a read-write medium and update the tree with a command
like:
<blockquote><pre>
# <kbd>cd [portsdir]/; cvs -d anoncvs@server.openbsd.org:/cvs update -Pd -rOPENBSD_2_9</kbd>
</pre></blockquote>
<p>
[Of course, you must replace the local directory and server name here
with the location of your ports collection and a nearby anoncvs
server.]
<p>
Note that most ports are available as packages on our mirrors. Updated
packages for the 2.9 release will be made available if problems arise.
<p>
If you're interested in seeing a port added, would like to help out, or just
would like to know more, the mailing list
<a href="mail.html">ports@openbsd.org</a> is a good place to know.
</section>