[BACK]Return to 56.html CVS log [TXT][DIR] Up to [local] / www

File: [local] / www / 56.html (download) (as text)

Revision 1.4, Sun Aug 3 16:44:25 2014 UTC (9 years, 9 months ago) by deraadt
Branch: MAIN
Changes since 1.3: +4 -3 lines

Better showcasing of the signify keys

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>OpenBSD 5.6</title>
<meta name="resource-type" content="document">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="description" content="OpenBSD 5.6">
<meta name="keywords" content="openbsd,main">
<meta name="distribution" content="global">
<meta name="copyright" content="This document copyright 2014 by OpenBSD.">
</head>

<body bgcolor="#ffffff" text="#000000" link="#24248E">

<a href="index.html">
<img alt="[OpenBSD]" height="30" width="141" hspace="24" src="images/smalltitle.gif" border="0"></a>
<p>

<a href="images/XXX.jpg">
<img align="left" width="227" height="343" hspace="24" src="images/XXX.jpg"></a>
<h2><font color="#0000e0">OpenBSD 5.6</font></h2>
<p>
Released Nov 1, 2014<br>
Copyright 1997-2014, Theo de Raadt.<br>
<font color="#e00000">ISBN 978-0-9881561-4-2</font>
<br>
<a href="lyrics.html#56">5.6 Song: "XXX"</a>
<p>

<ul>
<li>Order a CDROM from our <a href="orders.html">ordering system</a>.
<li>See the information on <a href="ftp.html">the FTP page</a> for
    a list of mirror machines.
<li>Go to the <font color="#e00000">pub/OpenBSD/5.6/</font> directory on
    one of the mirror sites.
<li>Briefly read the rest of this document.
<li>Have a look at <a href="errata56.html">the 5.6 errata page</a> for a list
    of bugs and workarounds.
<li>See a <a href="plus56.html">detailed log of changes</a> between the
    5.5 and 5.6 releases.
<p>
<li>http://www.openbsd.org/cgi-bin/man.cgi?query=signify&amp;sektion=1">signify(1)</a> pubkeys for this release:
<li>5.6 base: RWR0EANmo9nqhpPbPUZDIBcRtrVcRwQxZ8UKGWY8Ui4RHi229KFL84wV
<li>5.6 fw:   RWT4e3jpYgSeLYs62aDsUkcvHR7+so5S/Fz/++B859j61rfNVcQTRxMw
<li>5.6 pkg:  RWSPEf7Vpp2j0PTDG+eLs5L700nlqBFzEcSmHuv3ypVUEOYwso+UucXb
</ul>
<br clear=all>
All applicable copyrights and credits can be found in the applicable
file sources found in the files src.tar.gz, sys.tar.gz,
xenocara.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.
<p>

<a name="new"></a>
<hr>
<p>
<h3><font color="#0000e0">What's New</font></h3>
<p>
This is a partial list of new features and systems included in OpenBSD 5.6.
For a comprehensive list, see the <a href="plus56.html">changelog</a> leading
to 5.6.
<p>

<ul>
<li>...
<p>


<li>Installer improvements:
    <ul>
    <li>...
    </ul>
<p>

<li>New/extended platforms:
    <ul>
    <li>...
    </ul>
<p>

<li>Improved hardware support, including:
    <ul>
    <li>...
    </ul>
<p>

<li>Generic network stack improvements:
    <ul>
    <li>...
    </ul>
<p>

<li>Routing daemons and other userland network improvements:
    <ul>
    <li>...
    </ul>
<p>

<li>OpenSMTPD 5.4.2 (includes changes to 5.4.1):
    <ul>
    <li>...
    </ul>
<p>

<li>Security improvements:
    <ul>
    <li>Changed the heuristics of the stack protector to also protect functions with local array definitions and references to local frame addresses.  This matches the -fstack-protector-strong option of upstream GCC.
    <li>Position-independent executables (PIE) are now used by default on powerpc.
    <li>Removed Kerberos.
    </ul>
<p>

<li>Assorted improvements:
    <ul>
    <li>locate databases for both base and xenocara, as
    <code>/usr/lib/locate/src.db</code> and
    <code>/usr/X11R6/lib/locate/xorg.db</code>.
    <li>Much faster package updates, due to package contents reordering that
    precludes re-downloading unchanged files.
    </ul>
<p>

<li>LibreSSL
    <ul>
    <li>...
    </ul>
<p>

<li>OpenSSH 6.7
    <ul>
    <li>Security:
      <ul>
      <li>...
      </ul>
    <li>New/changed features:
      <ul>
      <li>...
      </ul>
    <li>The following significant bugs have been fixed in this release:
      <ul>
      <li>...
      </ul>
    </ul>
<p>

<li>Ports and packages:
    <ul>
    <li>Over 8,800 ports.
    <li>...
    </ul>
<p>
<li>Many pre-built packages for each architecture:
    <table border=0 cellspacing=0 cellpadding=2 width="95%">
    <tr>
    <td valign="top" width="25%">
    <ul>
      <li>i386:       XXXX
      <li>sparc64:    XXXX
      <li>alpha:      XXXX
      <li>m68k:       XXXX
    </ul></td><td valign=top width="25%"><ul>
      <li>sh:         XXXX
      <li>amd64:      XXXX
      <li>powerpc:    XXXX
      <li>m88k:       XXXX
    </ul></td><td valign=top width="25%"><ul>
      <li>sparc:      XXXX
      <li>arm:        XXXX
      <li>hppa:       XXXX
    </ul></td><td valign=top width="25%"><ul>
      <li>vax:        XXXX
      <li>mips64:     XXXX
      <li>mips64el:   XXXX
  </ul></td></tr></table>
<p>

<li>Some highlights:
    <ul>
    <li>GNOME 3.12.2			<li>KDE 3.5.10
    <li>KDE 4.13.2
    <li>Xfce 4.10			<li>MySQL 5.1.73
    <li>PostgreSQL 9.3.4		<li>Postfix 2.11.1
    <li>OpenLDAP 2.3.43 and 2.4.39	<li>Mozilla Firefox 31.0
    <li>Mozilla Thunderbird 31.0	<li>GHC 7.6.3
    <li>LibreOffice 4.1.6.2		<li>Emacs 21.4 and 24.3
    <li>Vim 7.4.135			<li>PHP 5.3.28, 5.4.30 and 5.5.14
    <li>Python 2.7.8, 3.3.5 and 3.4.1	<li>Ruby 1.8.7.374, 1.9.3.545, 2.0.0.481 and 2.1.2
    <li>Tcl/Tk 8.5.15 and 8.6.1		<li>JDK 1.6.0.32 and 1.7.0.55
    <li>Mono 3.4.0			<li>Chromium 36.0.1985.125
    <li>Groff 1.22.2			<li>Go 1.3
    <li>GCC 4.6.4, 4.8.3 and 4.9.0	<li>LLVM/Clang 3.5 (20140228)
    <li>Node.js 0.10.28
    </ul>
<p>

<li>As usual, steady improvements in manual pages and other documentation.
<p>

<li>The system includes the following major components from outside suppliers:
    <ul>
    <li>Xenocara (based on X.Org 7.7 with xserver 1.15.2 + patches,
      freetype 2.5.3, fontconfig 2.11.1, Mesa 10.2.3, xterm 309,
      xkeyboard-config 2.11 and more)
    <li>Gcc 4.2.1 (+ patches) and 3.3.6 (+ patches)
    <li>Perl 5.18.3 (+ patches)
    <li>Nginx 1.6.0 (+ patches)
    <li>SQLite 3.8.4.3 (+ patches)
    <li>Sendmail 8.14.8, with libmilter
    <li>Bind 9.4.2-P2 (+ patches)
    <li>NSD 4.0.1
    <li>Unbound 1.4.22
    <li>Sudo 1.7.2p8
    <li>Ncurses 5.7
    <li>Binutils 2.15 (+ patches)
    <li>Gdb 6.3 (+ patches)
    <li>Less 444 (+ patches)
    <li>Awk Aug 10, 2011 version
    </ul>

</ul>

<a name="install"></a>
<hr>
<p>
<h3><font color="#0000e0">How to install</font></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 5.6 on your machine:
<p>
<ul>
<li><a href="http://ftp.openbsd.org/pub/OpenBSD/5.6/i386/INSTALL.i386">
	.../OpenBSD/5.6/i386/INSTALL.i386 (on CD1)</a>
<li><a href="http://ftp.openbsd.org/pub/OpenBSD/5.6/vax/INSTALL.vax">
	.../OpenBSD/vax/INSTALL.vax (on CD1)</a>
<p>
<li><a href="http://ftp.openbsd.org/pub/OpenBSD/5.6/amd64/INSTALL.amd64">
	.../OpenBSD/amd64/INSTALL.amd64 (on CD2)</a>
<li><a href="http://ftp.openbsd.org/pub/OpenBSD/5.6/hppa/INSTALL.hppa">
	.../OpenBSD/hppa/INSTALL.hppa (on CD2)</a>
<li><a href="http://ftp.openbsd.org/pub/OpenBSD/5.6/macppc/INSTALL.macppc">
	.../OpenBSD/macppc/INSTALL.macppc (on CD2)</a>
<p>
<li><a href="http://ftp.openbsd.org/pub/OpenBSD/5.6/sparc64/INSTALL.sparc64">
	.../OpenBSD/sparc64/INSTALL.sparc64 (on CD3)</a>
<li><a href="http://ftp.openbsd.org/pub/OpenBSD/5.6/sparc/INSTALL.sparc">
	.../OpenBSD/sparc/INSTALL.sparc (on CD3)</a>
<p>
<li><a href="http://ftp.openbsd.org/pub/OpenBSD/5.6/alpha/INSTALL.alpha">
	.../OpenBSD/5.6/alpha/INSTALL.alpha</a>
<li><a href="http://ftp.openbsd.org/pub/OpenBSD/5.6/armish/INSTALL.armish">
	.../OpenBSD/5.6/armish/INSTALL.armish</a>
<li><a href="http://ftp.openbsd.org/pub/OpenBSD/5.6/armv7/INSTALL.armv7">
	.../OpenBSD/5.6/armv7/INSTALL.armv7</a>
<li><a href="http://ftp.openbsd.org/pub/OpenBSD/5.6/aviion/INSTALL.aviion">
	.../OpenBSD/5.6/aviion/INSTALL.aviion</a>
<li><a href="http://ftp.openbsd.org/pub/OpenBSD/5.6/hp300/INSTALL.hp300">
	.../OpenBSD/5.6/hp300/INSTALL.hp300</a>
<li><a href="http://ftp.openbsd.org/pub/OpenBSD/5.6/hppa/INSTALL.hppa">
	.../OpenBSD/5.6/hppa/INSTALL.hppa</a>
<li><a href="http://ftp.openbsd.org/pub/OpenBSD/5.6/landisk/INSTALL.landisk">
	.../OpenBSD/5.6/landisk/INSTALL.landisk</a>
<li><a href="http://ftp.openbsd.org/pub/OpenBSD/5.6/loongson/INSTALL.loongson">
	.../OpenBSD/5.6/loongson/INSTALL.loongson</a>
<li><a href="http://ftp.openbsd.org/pub/OpenBSD/5.6/luna88k/INSTALL.luna88k">
	.../OpenBSD/5.6/luna88k/INSTALL.luna88k</a>
<li><a href="http://ftp.openbsd.org/pub/OpenBSD/5.6/macppc/INSTALL.macppc">
	.../OpenBSD/5.6/macppc/INSTALL.macppc</a>
<li><a href="http://ftp.openbsd.org/pub/OpenBSD/5.6/mvme68k/INSTALL.mvme68k">
	.../OpenBSD/5.6/mvme68k/INSTALL.mvme68k</a>
<li><a href="http://ftp.openbsd.org/pub/OpenBSD/5.6/mvme88k/INSTALL.mvme88k">
	.../OpenBSD/5.6/mvme88k/INSTALL.mvme88k</a>
<li><a href="http://ftp.openbsd.org/pub/OpenBSD/5.6/octeon/INSTALL.octeon">
	.../OpenBSD/5.6/octeon/INSTALL.octeon</a>
<li><a href="http://ftp.openbsd.org/pub/OpenBSD/5.6/sgi/INSTALL.sgi">
	.../OpenBSD/5.6/sgi/INSTALL.sgi</a>
<li><a href="http://ftp.openbsd.org/pub/OpenBSD/5.6/socppc/INSTALL.socppc">
	.../OpenBSD/5.6/socppc/INSTALL.socppc</a>
<li><a href="http://ftp.openbsd.org/pub/OpenBSD/5.6/sparc/INSTALL.sparc">
	.../OpenBSD/5.6/sparc/INSTALL.sparc</a>
<li><a href="http://ftp.openbsd.org/pub/OpenBSD/5.6/vax/INSTALL.vax">
	.../OpenBSD/5.6/vax/INSTALL.vax</a>
<li><a href="http://ftp.openbsd.org/pub/OpenBSD/5.6/zaurus/INSTALL.zaurus">
	.../OpenBSD/5.6/zaurus/INSTALL.zaurus</a>
</ul>
<hr>

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

<h3><font color="#e00000">OpenBSD/i386:</font></h3>
<ul>
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:5.6/i386/floppy56.fs</i> to a floppy and boot via the floppy drive.

<p>
Use <i>CD1:5.6/i386/floppyB56.fs</i> instead for greater SCSI controller
support, or <i>CD1:5.6/i386/floppyC56.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:5.6/tools/rawrite.exe</i>. To make the boot floppy under a Unix OS,
use the
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=dd&amp;sektion=1">dd(1)</a>
utility. The following is an example usage of
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=dd&amp;sektion=1">dd(1)</a>,
where the device could be &quot;floppy&quot;, &quot;rfd0c&quot;, or
&quot;rfd0a&quot;.

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

<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">FAQ 4.3.2</a>.
</ul>

<p>
<h3><font color="#e00000">OpenBSD/amd64:</font></h3>
<ul>
The 5.6 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:5.6/amd64/floppy56.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.
</ul>

<p>
<h3><font color="#e00000">OpenBSD/macppc:</font></h3>
<ul>
Burn the image from the FTP site to a CDROM, and power on 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
/5.6/macppc/bsd.rd</i>
</ul>

<p>
<h3><font color="#e00000">OpenBSD/sparc64:</font></h3>
<ul>
Put 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:5.6/sparc64/floppy56.fs</i> or <i>CD3:5.6/sparc64/floppyB56.fs</i>
(depending on your machine) to a floppy and boot it with <i>boot
floppy</i>. Refer to INSTALL.sparc64 for details.

<p>
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:5.6/sparc64/miniroot56.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.
</ul>

<p>
<h3><font color="#e00000">OpenBSD/alpha:</font></h3>
<ul>
<p>Write <i>FTP:5.6/alpha/floppy56.fs</i> or
<i>FTP:5.6/alpha/floppyB56.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.

</ul>

<p>
<h3><font color="#e00000">OpenBSD/armish:</font></h3>
<ul>
<p>
After connecting a serial port, Thecus can boot directly from the network
either tftp or http. Configure the network using fconfig, reset,
then load bsd.rd, see INSTALL.armish for specific details.
IOData HDL-G can only boot from an EXT-2 partition. Boot into linux
and copy 'boot' and bsd.rd into the first partition on wd0 (hda1)
then load and run bsd.rd, preserving the wd0i (hda1) ext2fs partition.
More details are available in INSTALL.armish.
</ul>

<p>
<h3><font color="#e00000">OpenBSD/hp300:</font></h3>
<ul>
<p>
Boot over the network by following the instructions in INSTALL.hp300.
</ul>

<p>
<h3><font color="#e00000">OpenBSD/hppa:</font></h3>
<ul>
<p>
Boot over the network by following the instructions in INSTALL.hppa or the
<a href="hppa.html#install">hppa platform page</a>.
</ul>

<p>
<h3><font color="#e00000">OpenBSD/landisk:</font></h3>
<ul>
<p>
Write <i>miniroot56.fs</i> to the start of the CF
or disk, and boot normally.
</ul>

<p>
<h3><font color="#e00000">OpenBSD/loongson:</font></h3>
<ul>
<p>
Write <i>miniroot56.fs</i> to a USB stick and boot bsd.rd from it
or boot bsd.rd via tftp.
Refer to the instructions in INSTALL.loongson for more details.
</ul>
<p>

<p>
<h3><font color="#e00000">OpenBSD/luna88k:</font></h3>
<ul>
<p>
Copy `boot' and `bsd.rd' to a Mach or UniOS partition, and boot the bootloader
from the PROM, and the bsd.rd from the bootloader.
Refer to the instructions in INSTALL.luna88k for more details.
</ul>

<p>
<h3><font color="#e00000">OpenBSD/mvme68k:</font></h3>
<ul>
<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.
</ul>

<p>
<h3><font color="#e00000">OpenBSD/mvme88k:</font></h3>
<ul>
<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.
</ul>

<p>
<h3><font color="#e00000">OpenBSD/octeon:</font></h3>
<ul>
<p>
After connecting a serial port, boot bsd.rd over the network via DHCP/tftp.
Refer to the instructions in INSTALL.octeon for more details.
</ul>

<p>
<h3><font color="#e00000">OpenBSD/sgi:</font></h3>
<ul>
<p>
To install, burn cd56.iso on a CD-R, put it in the CD drive of your
machine and select <i>Install System Software</i> from the System Maintenance
menu. Indigo/Indy/Indigo2 (R4000) systems will not boot automatically from
CD-ROM, and need a proper invocation from the PROM prompt.
Refer to the instructions in INSTALL.sgi for more details.

<p>
If your machine doesn't have a CD drive, you can setup a DHCP/tftp network
server, and boot using "bootp()/bsd.rd.IP##" using the kernel matching your
system type. Refer to the instructions in INSTALL.sgi for more details.
</ul>

<p>
<h3><font color="#e00000">OpenBSD/socppc:</font></h3>
<ul>
<p>
After connecting a serial port, boot over the network via DHCP/tftp.
Refer to the instructions in INSTALL.socppc for more details.
</ul>

<p>
<h3><font color="#e00000">OpenBSD/sparc:</font></h3>
<ul>
Boot from one of the provided install ISO images, using one of the two
commands listed below, depending on the version of your ROM.

<ul><pre>
ok <strong>boot cdrom 5.6/sparc/bsd.rd</strong>
or
&gt; <strong>b sd(0,6,0)5.6/sparc/bsd.rd</strong>
</pre></ul>

<p>
If your SPARC system does not have a CD drive, you can alternatively boot from floppy.
To do so you need to write <i>floppy56.fs</i> to a floppy.
For more information see <a href="faq/faq4.html#MkFlop">FAQ 4.3.2</a>.
To boot from the floppy use one of the two commands listed below,
depending on the version of your ROM.

<ul><pre>
ok <strong>boot floppy</strong>
or
&gt; <strong>b fd()</strong>
</pre></ul>

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

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

<p>
<h3><font color="#e00000">OpenBSD/vax:</font></h3>
<ul>
Boot over the network via mopbooting as described in INSTALL.vax.
</ul>

<p>
<h3><font color="#e00000">OpenBSD/zaurus:</font></h3>
<ul>
<p>
Using the Linux built-in graphical ipkg installer, install the
openbsd56_arm.ipk package.  Reboot, then run it.  Read INSTALL.zaurus
for a few important details.
</ul>

<p>
<h3><font color="#e00000">Notes about the source code:</font></h3>
<ul>
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:
<p>
<ul><pre>
# <strong>mkdir -p /usr/src</strong>
# <strong>cd /usr/src</strong>
# <strong>tar xvfz /tmp/src.tar.gz</strong>
</pre></ul>
<p>
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:
<p>
<ul><pre>
# <strong>mkdir -p /usr/src/sys</strong>
# <strong>cd /usr/src</strong>
# <strong>tar xvfz /tmp/sys.tar.gz</strong>
</pre></ul>
<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.
<p>
</ul>

<a name="upgrade"></a>
<hr>
<p>
<h3><font color="#0000e0">How to upgrade</font></h3>
<p>
If you already have an OpenBSD 5.4 system, and do not want to reinstall,
upgrade instructions and advice can be found in the
<a href="faq/upgrade56.html">Upgrade Guide</a>.

<a name="ports"></a>
<hr>
<p>
<h3><font color="#0000e0">Ports Tree</font></h3>
<p>
A ports tree archive is also provided.  To extract:
<p>
<ul><pre>
# <strong>cd /usr</strong>
# <strong>tar xvfz /tmp/ports.tar.gz</strong>
</pre></ul>
<p>
The <i>ports/</i> subdirectory is a checkout of the OpenBSD ports tree.  Go
read the <a href="faq/ports/index.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="http://www.openbsd.org/cgi-bin/man.cgi?query=cvs&amp;sektion=1&amp;arch=i386">
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
<a href="anoncvs.html">AnonCVS</a>.
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:
<p>
<ul><pre>
# <strong>cd /usr/ports</strong>
# <strong>cvs -d anoncvs@server.openbsd.org:/cvs update -Pd -rOPENBSD_5_5</strong>
</pre></ul>
<p>
[Of course, you must replace the server name here with a nearby anoncvs
server.]
<p>
Note that most ports are available as packages through FTP. Updated
packages for the 5.6 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.
<p>
</body>
</html>