35.html

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

<title>OpenBSD 3.5</title>
<meta name="description" content="OpenBSD 3.5">
<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/35.html">

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

<table>
<tr>
<td>
<a href="images/Carp.gif">
<img width="255" height="343" src="images/Carp.gif" alt="Carp"></a>
<td>
Released May 1, 2004<br>
Copyright 1997-2004, Theo de Raadt.<br>
<cite class=isbn>ISBN 0-9731791-3-9</cite>
<br>
3.5 Song: <a href="lyrics.html#35">"CARP License" and "Redundancy must be free"</a>
<br>
<br>
<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/3.5/</code> directory on
    one of the mirror sites.
<li>Have a look at <a href="errata35.html">The 3.5 Errata page</a> for a list
    of bugs and workarounds.
<li>See a <a href="plus35.html">detailed log of changes</a> between the
    3.4 and 3.5 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 3.5.
For a comprehensive list, see the <a href="plus35.html">changelog</a> leading
to 3.5.
<p>

<ul>

<li> New platforms:
<ul>
<li><a href="amd64.html">OpenBSD/amd64</a><br>
Supporting the AMD64 architecture natively,
with full 64-bit support, 8 extra registers in the architecture
to significantly increase performance, and a memory management
Non-Executable bit that permits full W^X support.<br>
(Note: The upcoming Intel "ia32e" AMD64-compatible CPUs have also
been tested, and work, even though they lack the NX bit).
<li><a href="cats.html">OpenBSD/cats</a><br>
Our first entry in the ARM-CPU landscape.  We intend to use this as a
development platform for something else we plan for the future...
<li><a href="mvme88k.html">OpenBSD/mvme88k</a><br>
Supporting an older, but very cool CPU architecture, perhaps the
most pure RISC CPU ever.
</ul>
<p>

<li>Replacement of the GNU
<a href="https://man.openbsd.org/bc">bc(1)</a>,
<a href="https://man.openbsd.org/dc">dc(1)</a>,
<a href="https://man.openbsd.org/nm">nm(1)</a> and
<a href="https://man.openbsd.org/size">size(1)</a>
commands with BSD licensed equivalents.
<p>

<li>A large number of bug fixes, changes, and optimizations to our packet filter
    <a href="https://man.openbsd.org/pf">pf(4)</a>
    including:
<ul>
<li>Atomic commits of ruleset changes (reduce the chance of ending up in an
    inconsistent state).
<li>A 30% reduction in the size of state table entries.
<li>Source-tracking (limit number of clients and states per client).
<li>Sticky-address (the flexibility of round-robin with the benefits of
    source-hash).
<li>Invert the socket match order when redirecting to
    localhost (prevents the potential security problem of remote connections
    being identified as local).
<li>Significant improvements to interface handling.
</ul>
<p>

<li>New tools for filtering gateway failover:
<ul>
<li>CARP (the Common Address Redundancy Protocol)
    <a href="https://man.openbsd.org/carp">carp(4)</a>
    allows multiple machines to share responsibility for a given IP address or
    addresses. If the owner of the address fails, another member of the group
    will take over for it. A discussion of the history of CARP can be found
    <a href="lyrics.html">here</a>.
<li>Additions to the
    <a href="https://man.openbsd.org/pfsync">pfsync(4)</a>
    interface allow it to synchronise state table entries between two or more
    firewalls which are operating in parallel, allowing stateful connections
    to cross any of the firewalls regardless of where the state was initially
    created.
</ul>
<p>

<li> New functionality:
<ul>
<li><a href="https://man.openbsd.org/pty.4">pty(4)</a> devices are now allocated on demand, up to a configurable limit.
<li>New ptm device (see <a href="https://man.openbsd.org/pty.4">pty(4)</a>)
that allows non-privileged processes to allocate a properly-permissioned pty.<br>
As a result any process can now open a pty easily, meaning
<a href="https://man.openbsd.org/xterm.1">xterm(1)</a>
and
<a href="https://man.openbsd.org/xconsole.1">xconsole(1)</a>
are no longer setuid root.  (In 3.4 they were setuid root, but privilege revoking).
<li>The <a href="https://man.openbsd.org/closefrom.2">closefrom(2)</a>
system call has been added.
<li>TCP MD5 signatures (used by <a href="https://man.openbsd.org/nc.1">nc(1)</a>
and <a href="https://man.openbsd.org/bgpd.8">bgpd(8)</a>).
<li>Network boot support for i386 and amd64, using
    <a href="https://man.openbsd.org/i386/pxeboot.8">pxeboot(8)</a>.
<li>The i386 8GB boot loader limitation has been removed.
<li><a href="https://man.openbsd.org/spamd.8">spamd(8)</a>
gains <a href="http://projects.puremagic.com/greylisting/">greylisting</a> support. This allows greylisting (a very powerful spam reduction technique) to be
done on a firewall for many mail hosts, no matter what MTA is being used.
<li>Interface 'cloning', accessed by
<a href="https://man.openbsd.org/ifconfig.8">ifconfig(8)</a>
commands <em>create</em> and <em>destroy</em>. E.g. 'ifconfig vlan100 create'.
<li>
<a href="https://man.openbsd.org/ifconfig.8">ifconfig(8)</a>
can now be used with a generic <em>interface</em> name, for listing all such configured interfaces. E.g. 'ifconfig carp'.
<li>The MAKEDEV(8) manual pages are now generated, and hence, accurate.
<li>Complete rewrite of <a href="https://man.openbsd.org/pkg_add.1">package</a> tools in perl.
<li><a href="https://man.openbsd.org/syslogd.8">syslogd(8)</a>
now supports logging to memory buffers, to be read using
<a href="https://man.openbsd.org/syslogc.8">syslogc(8)</a>.
This is useful for diskless or flash-based computers.
<li><a href="https://man.openbsd.org/ipsec.4">IPsec</a> ESP in UDP encapsulation.
<li><a href="https://man.openbsd.org/malloc.3">
malloc(3)</a> chunk randomization and guard pages. This helps to detect out-of-bounds
reads and writes.
<li><a href="https://man.openbsd.org/authpf.8">
authpf(8)</a> now tags traffic in
<a href="https://man.openbsd.org/pflog.4">
pflog(4)</A> so that users may be associated with traffic through a NAT setup.
<li>hw.setperf sysctl allows controlling the speed of many new i386
<a href="https://man.openbsd.org/cpu&arch=i386">CPUs</a>,
great for prolonged battery life.
<li>XFS has been added to the GENERIC kernels so that
<a href="https://man.openbsd.org/afsd.8">afsd(8)
</a> may be started easily, eliminating the need to recompile the kernel
to use AFS.<br>
AFS can now be used anonymously by enabling it in
<a href="https://man.openbsd.org/rc.conf.8">rc.conf(8)</a>
with no further configuration.
<li>The <a href="https://man.openbsd.org/ps.1">ps</a>, <a href="https://man.openbsd.org/top.1">top</a> and <a href="https://man.openbsd.org/w.1">w</a> utilities no longer break when changes are made in kernel structures.
<li>A <a href="https://man.openbsd.org/poll.2">poll</a> interface has been added to the <a href="https://man.openbsd.org/rpc.3">rpc</a> routines in the standard C library. Use of <a href="https://man.openbsd.org/poll.2">poll</a> over <a href="https://man.openbsd.org/select.2">select</a> can result in better performance for programs with a large number of open file descriptors.
<li><a href="https://man.openbsd.org/dhclient.8"
>dhclient(8)</a> now detects when the interface it configured is modified and
gracefully exits.
e.g. repeatedly running it against the same interface leaves only the
last instance active.
</ul>
<p>

<li> Privilege separation added to allow complex operations to occur in an untrusted, unprivileged process, resulting in much greater security for the following processes:
<ul>
<li><a href="https://man.openbsd.org/isakmpd.8">isakmpd(8)</a>
<li><a href="https://man.openbsd.org/named.8">named(8)</a>
(Previously privilege revoking, but this had a small breakage).
<li><a href="https://man.openbsd.org/pflogd.8">pflogd(8)</a>
<li><a href="https://man.openbsd.org/tcpdump.8">tcpdump(8)</a>
</ul>
<p>

<li> New tools:
<ul>
<li><a href="https://man.openbsd.org/sensorsd.8">sensorsd(8)</a>, monitoring hardware sensors.
<li><a href="https://man.openbsd.org/procmap.1">procmap(1)</a>, to examine a process' memory map.
<li><a href="https://man.openbsd.org/bgpd.8">bgpd(8)</a>, implementing the <a href="https://www.rfc-editor.org/rfc/rfc1771.txt">BGP-4</a> routing protocol.
<li><a href="https://man.openbsd.org/pkill.1">pkill(1)</a> and
<a href="https://man.openbsd.org/pgrep.1">pgrep(1)</a>, finding or signalling processes by name.
</ul>
<p>

<li> Performance improvements:
<ul>
<li>Improved connection/socket lookup - about 100 times faster at 10000 sockets than 3.4.
<li>TCP SYN cache. Greatly reduces the memory cost of half-open TCP connections.
<li>Implemented TCP adjustments recommended by
    <a href="https://www.rfc-editor.org/rfc/rfc3390.txt">RFC3390</a>,
    controllable via
    <a href="https://man.openbsd.org/sysctl.8">sysctl</a>.
<li>OpenSSL speedup on i386, up to 100% improvement for md5, sha1, blowfish,
    des, 3des, rsa, dsa and bn.
<li>OpenSSL now directly uses the new AES instructions some VIA C3 processors
    provide, increasing AES to 780MBytes/second (so you get to see a fan-less
    CPU performing AES more than 10x faster than the fastest CPU currently sold).
<li>Directory hashing makes lookups in large directories much faster.
<li>Zeroing pages with SSE. Faster operation, and avoids clobbering the cache.
</ul>
<p>

<li><a href="https://man.openbsd.org/scsi.4">SCSI(4)</a> improvements:
<ul>
<li>Bus probe made faster by skipping non-existent LUNs.
<li>Bus probe made saner by elimination of spurious commands.
<li>Bus probe made safer by having INQUIRY commands ask only for available data.
<li>Eliminated a race that, e.g., caused problems burning CDs at high speeds.
<li>SCSIDEBUG output can now be restricted to specified buses.
<li>ASC/ASCQ diagnostic messages updated to SCSI-3 standards.
<li>Better error handling.
</ul>
<p>

<li>Improved hardware support, including:
<ul>
<li>The <a href="hppa.html">hppa</a> architecture gets support for many
    <a href="https://man.openbsd.org/pci">PCI</a>
    based machines w/ addition of <a href="https://man.openbsd.org/hppa/dino.4">dino(4)</a> GSC-PCI bridge.
<li>New <a href="https://man.openbsd.org/oosiop.4">oosiop(4)</a> driver for NCR 53C700 SCSI host adapters.
<li>Major improvements to <a href="https://man.openbsd.org/ahc.4">ahc(4)</a>, bringing support for many new models.
<li>New <a href="https://man.openbsd.org/bce.4">bce(4)</a> driver, supporting the Broadcom BCM4401 FastEthernet chipset.
<li>New <a href="https://man.openbsd.org/mpt.4">mpt(4)</a> driver for  LSI Fusion-MPT SCSI and FibreChannel host adapters.
<li>New <a href="https://man.openbsd.org/macppc/snapper.4">snapper(4)</a> audio driver for recent iBook (since May 02) and PowerBook (since Apr 02) models.
<li>Improved stability of the <a href="https://man.openbsd.org/wi.4">wi(4)</a> driver as well as support for USB-based adapters and software WEP.
<li><a href="https://man.openbsd.org/wi.4">wi(4)</a> in HostAP mode now supports SSID hiding and newer prism firmware revisions.
<li>Fixed several firmware incompatibility issues in <a href="https://man.openbsd.org/an.4">an(4)</a>.
<li>Improved ATA and SATA support.
<li>Support for i835 AGP GART in <a href="https://man.openbsd.org/vga.4">vga(4)</a>.
<li>Improved Gigabit Ethernet support for <a href="https://man.openbsd.org/em.4">em(4)</a>,  <a href="https://man.openbsd.org/sk.4">sk(4)</a> &  <a href="https://man.openbsd.org/bge.4">bge(4)</a>.
<li>Several fixes for <a href="https://man.openbsd.org/apm.4">apm(4)</a>.
<li>Support for Intel 852/855/865 AGP chipsets.
<li>Many more USB Flash and other
<a href="https://man.openbsd.org/umass.4">umass(4)</a> devices work as a result of SCSI improvements.
</ul>
<p>

<li> This release ships with Firefox for all major architectures.
<p>

<li> Major improvements in <a href="https://man.openbsd.org/pthreads.3">pthreads(3)</a>.
<p>

<li> Over 2500 ports, 2300 pre-built packages.
<p>

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

<li>Many improvements in manual pages and other documentation.
<p>

<li>Gcc 3.3.2, including local additions like ProPolice support, for the
<a href="amd64.html">OpenBSD/amd64</a>,
<a href="cats.html">OpenBSD/cats</a> and
<a href="sparc64.html">OpenBSD/sparc64</a>
platforms.
Other architectures still use gcc 2.95.3 with the same local additions.
<p>
<li>OpenSSH 3.8.1:
<ul>
<li>
<a href="https://man.openbsd.org/sshd.8">sshd(8)</a>
now supports forced changes of expired passwords via
<a href="https://man.openbsd.org/passwd.1">passwd(1)</a>.
<li>
<a href="https://man.openbsd.org/ssh.1">ssh(1)</a>
now uses untrusted cookies for X11-Forwarding.
Some X11 applications might need full access to the X11 server,
see ForwardX11Trusted in
<a href="https://man.openbsd.org/ssh_config.5">ssh_config(5)</a>
and
<a href="https://man.openbsd.org/xauth.1">xauth(1)</a>.
<li>
<a href="https://man.openbsd.org/ssh.1">ssh(1)</a>
now supports sending application layer
keep-alive messages to the server.  See ServerAliveInterval in
<a href="https://man.openbsd.org/ssh_config.5">ssh_config(5)</a>.
<li> Improved
<a href="https://man.openbsd.org/sftp.1">sftp(1)</a>
batch file support.
<li> New KerberosGetAFSToken option for
<a href="https://man.openbsd.org/sshd.8">sshd(8)</a>.
<li> Updated /etc/moduli file and improved performance for
protocol version 2.
<li> Support for host keys in DNS.
<li> The experimental "gssapi" support has been replaced with
the "gssapi-with-mic" to fix possible MITM attacks.
The two versions are not compatible.
</ul>
<p>

<li>The system includes the following major components from outside suppliers:
<ul>
<li>XFree86 4.4.0 unencumbered (+ patches, and i386 contains 3.3.X servers also, thus
    providing support for all chipsets)
<li>Gcc 2.95.3 (+ patches) and 3.3.2 (+ patches)
<li>Perl 5.8.2 (+ patches)
<li>Apache 1.3.29, mod_ssl 2.8.16, DSO support (+ patches)
<li>OpenSSL 0.9.7c (+ patches)
<li>Groff 1.15
<li>Sendmail 8.12.11
<li>Bind 9.2.3 (+ patches)
<li>Lynx 2.8.4rel.1 with HTTPS and IPv6 support (+ patches)
<li>Sudo 1.6.7p5
<li>Ncurses 5.2
<li>Latest KAME IPv6
<li>Heimdal 0.6rc1 (+ patches)
<li>Arla-current
</ul>
<p>

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

<hr>
Please refer to the following files on the three CDROMs or ftp mirror for
extensive details on how to install OpenBSD 3.5 on your machine:
<p>
<ul>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/3.5/i386/INSTALL.i386">
	.../OpenBSD/3.5/i386/INSTALL.i386 (on CD1)</a>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/3.5/vax/INSTALL.vax">
	.../OpenBSD/3.5/vax/INSTALL.vax (on CD1)</a>
<p>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/3.5/amd64/INSTALL.amd64">
	.../OpenBSD/3.5/amd64/INSTALL.amd64 (on CD2)</a>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/3.5/macppc/INSTALL.macppc">
	.../OpenBSD/3.5/macppc/INSTALL.macppc (on CD2)</a>
<p>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/3.5/sparc/INSTALL.sparc">
	.../OpenBSD/3.5/sparc/INSTALL.sparc (on CD3)</a>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/3.5/sparc64/INSTALL.sparc64">
	.../OpenBSD/3.5/sparc64/INSTALL.sparc64 (on CD3)</a>
<p>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/3.5/alpha/INSTALL.alpha">
	.../OpenBSD/3.5/alpha/INSTALL.alpha</a>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/3.5/cats/INSTALL.cats">
	.../OpenBSD/3.5/cats/INSTALL.cats</a>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/3.5/hp300/INSTALL.hp300">
	.../OpenBSD/3.5/hp300/INSTALL.hp300</a>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/3.5/hppa/INSTALL.hppa">
	.../OpenBSD/3.5/hppa/INSTALL.hppa</a>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/3.5/mac68k/INSTALL.mac68k">
	.../OpenBSD/3.5/mac68k/INSTALL.mac68k</a>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/3.5/mvme68k/INSTALL.mvme68k">
	.../OpenBSD/3.5/mvme68k/INSTALL.mvme68k</a>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/3.5/mvme88k/INSTALL.mvme88k">
	.../OpenBSD/3.5/mvme88k/INSTALL.mvme88k</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:3.5/i386/floppy35.fs</i> to a floppy and boot via the floppy drive.

<p>
Use <i>CD1:3.5/i386/floppyB35.fs</i> instead for greater scsi controller
support, or <i>CD1:3.5/i386/floppyC35.fs</i> for better laptop support.

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

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

<p>
To make a boot floppy under MS-DOS, use the &quot;rawrite&quot; utility located
at <i>CD1:3.5/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#MkFlop">this page</a>.

<h3>OpenBSD/vax:</h3>

<p>
Boot over the network via mopbooting as described in INSTALL.vax.

<h3>OpenBSD/amd64:</h3>

<p>
The 3.5 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 <i>CD2:3.5/amd64/floppy35.fs</i> to a floppy, then
boot from the floppy drive.

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

<p>
If you are planning to dual boot OpenBSD with another OS, you will need to
read INSTALL.amd64.

<h3>OpenBSD/macppc:</h3>

<p>
Put the CD2 in your CDROM drive and poweron your machine while holding down the
<i>C</i> key until the display turns on and shows <i>OpenBSD/macppc boot</i>.

<p>
Alternatively, at the Open Firmware prompt, enter <i>boot cd:,ofwboot
/3.5/macppc/bsd.rd</i>

<h3>OpenBSD/sparc:</h3>

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

<blockquote><pre>
ok <kbd>boot cdrom 3.5/sparc/bsd.rd</kbd>
or
> <kbd>b sd(0,6,0)3.5/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 <i>CD3:3.5/sparc/floppy35.fs</i> to a floppy.
For more information see <a href="faq/faq4.html#MkFlop">this page</a>. To boot from
the floppy use one of the two commands listed below, depending on the version of
your ROM.

<blockquote><pre>
ok <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/sparc64:</h3>

<p>
Put the CD3 in your CDROM drive and type <i>boot cdrom</i>.

<p>
If this doesn't work, or if you don't have a CDROM drive, you can write
<i>CD3:3.5/sparc64/floppy35.fs</i> to a floppy and boot it with <i>boot
floppy</i>.<br>
Make sure you use a properly formatted floppy with NO BAD BLOCKS or your install
will most likely fail.

<p>
You can also write <i>CD3:3.5/sparc64/miniroot35.fs</i> to the swap partition on
the disk and boot with <i>boot disk:b</i>.

<p>
If nothing works, you can boot over the network as described in INSTALL.sparc64

<h3>OpenBSD/alpha:</h3>

<p>
Write <i>3.5/alpha/floppy35.fs</i> or
<i>3.5/alpha/floppyB35.fs</i> (depending on your machine) to a diskette and
enter <i>boot dva0</i>. Refer to INSTALL.alpha for more details.

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

<h3>OpenBSD/cats:</h3>

<p>
After updating the firmware to at least ABLE 1.95 if necessary, boot
<i>3.5/cats/bsd.rd</i> from an ABLE-supported device (such as a CD-ROM
or an existing FFS or EXT2FS partition).

<h3>OpenBSD/hp300:</h3>

<p>
Boot over the network by following the instructions in INSTALL.hp300.

<h3>OpenBSD/hppa:</h3>

<p>
Boot over the network by following the instructions in INSTALL.hppa or the
<a href="hppa.html#netboot">hppa platform page</a>.

<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
<i>3.5/mac68k/utils</i> 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 <i>3.5/mac68k/</i> 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/mvme68k:</h3>

<p>
You can create a bootable installation tape or boot over the network.<br>
The network boot requires a MVME68K BUG version that supports the <i>NIOT</i>
and <i>NBO</i> debugger commands. Follow the instructions in INSTALL.mvme68k
for more details.

<h3>OpenBSD/mvme88k:</h3>

<p>
You can create a bootable installation tape or boot over the network.<br>
The network boot requires a MVME88K BUG version that supports the <i>NIOT</i>
and <i>NBO</i> debugger commands. Follow the instructions in INSTALL.mvme88k
for more details.
</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/sys.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 the <a href="faq/faq15.html">ports</a> 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.
<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_3_5</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 3.5 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>