[BACK]Return to 51.html CVS log [TXT][DIR] Up to [local] / www
File: [local] / www / 51.html (download) (as text)

Revision 1.13, Thu Mar 15 12:19:59 2012 UTC (12 years, 2 months ago) by sperreault
Branch: MAIN
Changes since 1.12: +2 -2 lines 

As pointed out by phessler@, rdomain support for IPv6 is not complete.
New wording suggested by sthen@. ok phessler@

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>OpenBSD 5.1 Release</title>
<link rev=made href="mailto:www@openbsd.org">
<meta name="resource-type" content="document">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="description" content="OpenBSD 5.1">
<meta name="keywords" content="openbsd,main">
<meta name="distribution" content="global">
<meta name="copyright" content="This document copyright 2011 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>
<hr>

<p>
<a href="images/Bugbusters.jpg">
<img align="left" width="227" height="343" hspace="24" vspace="30"
src="images/Bugbusters.jpg" alt="OpenBSD 5.1 logo"></a>
<h2><font color="#0000e0">The OpenBSD 5.1 Release:</font></h2>
<p>
To be released May 1, 2012<br>
Copyright 1997-2012, Theo de Raadt.<br>
<font color="#e00000">ISBN 978-0-9784475-9-5</font>
<br>
<a href="lyrics.html#51">5.1 Song: "Bug Busters"</a>
<p>

<a href="#new">What's New</a><br>
<a href="#install">How to install</a><br>
<a href="#upgrade">How to upgrade</a><br>
<a href="#ports">How to use the ports tree</a><br>
<a href="orders.html">Ordering a CD set</a><br>

<p>
<h3><font color="#0000e0">
To get the files for this release:
<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.1/</font> directory on
    one of the mirror sites.
<li>Briefly read the rest of this document.
<li>Have a look at <a href="errata51.html">The 5.1 Errata page</a> for a list
    of bugs and workarounds.
<li>See a <a href="plus51.html">detailed log of changes</a> between the
    5.0 and 5.1 releases.
</ul>
</font></h3>
<br clear=all>

<strong>Note:</strong> 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.1.
For a comprehensive list, see the <a href="plus51.html">changelog</a> leading
to 5.1.
<p>

<ul>
<li>Improved hardware support, including:
    <ul>
    <li><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=umsm&amp;sektion=4">umsm(4)</a> supports additional mobile broadband devices.
    <li>Non-GigE <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ale&amp;sektion=4">ale(4)</a> devices can now establish link to a GigE link partner.
    <li>Support for Intel 82580 has been added to <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=em&amp;sektion=4">em(4)</a>.
    <li>Support for MegaRAID 9240 has been added to <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=mfi&amp;sektion=4">mfi(4)</a>.
    <li>Support for Nuvoton NCT6776F has been added to <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=lm&amp;sektion=4">lm(4)</a>.
    <li>Support for Centrino Advanced-N 6205 has been added to <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=iwn&amp;sektion=4">iwn(4)</a>.
    <li>Support for SiS 1182/1183 SATA has been added to <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pciide&amp;sektion=4">pciide(4)</a>.
    </ul>
<p>

<li>Generic network stack improvements:
    <ul>
    <li>NAT64 support in PF using the af-to keyword.
    <li>RFC4638 MTU negotiation for pppoe(4).
    <li>pflow(4) now supports Netflow v9/ipfix.
    <li>Improved IPv6 fragment checking in PF and the network stack.
    <li>Various enhancements with ICMP/ICMPv6 states in PF.
    <li>Many robustness improvements for IEEE 802.11 (particularly hostap).
    <li>pfsync(4) improvements including jumbo frames and automatically requesting a bulk update after a physical interface comes online.
    <li>One-shot rule support for PF, for use with proxies via anchors.
    <li>Improved vlan priority support, including mapping to interface queues.
    <li>Initial rdomains support for IPv6.
    </ul>
<p>
<li>Routing daemons and other userland network improvements:
    <ul>
    <li>fstat now displays routing table ID and socket-splicing information and ps can display routing table ID.
    <li>traceroute and traceroute6 can look up ASNs for each hop.
    <li>snmpd(8) adds a MIB to show statistics for carp(4) interfaces.
    <li>bgpctl parses and display MRT routing table dumps.
    <li>ntpd supports multiple rdomains.
    <li>When ospfd detects route socket overflow, it now delays before it reloads the fib.
    <li>Improved and more consistent ToS support in various network tools (tcpbench/nc/ping/traceroute).
    <li>[Not written yet]
    </ul>
<p>

<li><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pf&amp;sektion=4">pf(4)</a> improvements:
    <ul>
    <li>[Not written yet]
    </ul>
<p>
<li>SCSI improvements:
    <ul>
    <li>[Not written yet]
    </ul>
<p>
<li>Assorted improvements:
    <ul>
    <li>Improved locale support.
    <li>Support for MSG_NOSIGNAL
    <li>KERN_PROC_CWD sysctl() for fetching the path to a process's working directory.
    <li>Improved fnmatch(), glob(), and regcomp() implementations to resist DoS attacks.
    <li>Lots of HISTORY and AUTHORS information added to manpages.
    <li>Improved checking of file-offset wraparound.
    <li>pwrite/pwritev now correctly ignored O_APPEND.
    <li>Improved conformance of header files with standards.
    <li>Improved cancelation support in both user-threads (libpthread) and rthreads.
    <li>Improved correctness of execing, coredumping, signal delivery, alternate signal stacks, blocking socket accepts(), mutexes and condition variables, per-thread errno, symbol binding, and ktracing when rthreads are in use.
    <li>Architecture-independent kernel support for thread-control-block handling for rthreads.
    <li>Small improvements to Linux compat (only available on i386).
    </ul>
<p>
<li>Install/Upgrade process changes:
    <ul>
    <li>[Not written yet]
    </ul>
<p>

<li>Over 7,000 ports, major performance and stability improvements in 
the package build process
    <ul>
    <li>downloading of distfiles is simpler, can resume interrupted download,
    discover file moves, and expire old files. Distfiles mirror sites now use
    the new and improved method.
    <li>dependency handling during ports build and package creation is at least
    twice as fast, twenty times as fast in pathological cases. This also affects
    user scripts such as out-of-date
    <li>more checks are done during package builds, for increased user friendliness
    <li>the long term process of documenting the infrastructure is now 100% done.
    <li>The distributed ports builder (dpb) can now clean up old dependencies,
    thus helping package builds be more reproducible.
    This found tens of hidden build dependencies in the ports tree already.
    <li>the semantics of pkg_add -a have been nailed down and a few minor bugs
    have been fixed.
    <li>arch-dependent issues are better classified, leading to better builds on
    old architectures in some complicated cases. In particular, dpb explicitly
    purges from memory info about packages it cannot build and stuff that 
    depends on it, leading to better life on sparc and vax which have very
    small data-size limits.
    <li>dpb recognizes full builds and trims some duplicate package builds
    </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:       7229
      <li>sparc64:    6599
      <li>alpha:      5943
    </ul></td><td valign=top width="25%"><ul>
      <li>sh:         ?
      <li>amd64:      7181
      <li>powerpc:    6852
    </ul></td><td valign=top width="25%"><ul>
      <li>sparc:      4152
      <li>arm:        ?
      <li>hppa:       6159
    </ul></td><td valign=top width="25%"><ul>
      <li>vax:        2199
      <li>mips64:     ?
      <li>mips64el:   5807
  </ul></td></tr></table>
<p>

<li>Some highlights:
    <ul>
    <li>Gnome 2.32.2                    <li>KDE 3.5.10
    <li>Xfce 4.8.0                      <li>MySQL 5.1.54
    <li>PostgreSQL 9.0.5                <li>Postfix 2.8.4
    <li>OpenLDAP 2.3.43 and 2.4.25      <li>Mozilla Firefox 3.5.19, 3.6.18 and 5.0
    <li>Mozilla Thunderbird 5.0         <li>GHC 7.0.4
    <li>LibreOffice 3.4.1.3             <li>Emacs 21.4, 22.3 and 23.3
    <li>Vim 7.3.154                     <li>PHP 5.2.17 and 5.3.6
    <li>Python 2.4.6, 2.5.4 and 2.7.1   <li>Ruby 1.8.7.352 and 1.9.2.200
    <li>Tcl 8.5.9                       <li>Jdk 1.7
    <li>Mono 2.10.2                     <li>Chromium 12.0.742.122
    <li>Groff 1.21
    </ul>
<p>

<li>As usual, steady improvements in manual pages and other documentation.
    <li>Base system and Xenocara manuals are now installed as source code,
      making <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=grep&amp;sektion=1">grep(1)</a> more useful in /usr/share/man/ and /usr/X11R6/man/.
    <li>If both formatted and source versions of manuals are installed,
      <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=man&amp;sektion=1">man(1)</a> automatically displays the newer version of each page.

 - The system includes the following major components from outside suppliers:
    <li>Xenocara (based on X.Org 7.6 with xserver 1.11.4 + patches,
      freetype 2.4.8, fontconfig 2.8.0, Mesa 7.10.3, xterm 276,
      xkeyboard-config 2.5 and more)
    <li>Gcc 2.95.3 (+ patches), 3.3.5 (+ patches) and 4.2.1 (+patches)
    <li>Perl 5.12.2 (+ patches)
    <li>Our improved and secured version of Apache 1.3, with
      SSL/TLS and DSO support
    <li>OpenSSL 1.0.0a (+ patches)
    <li>Sendmail 8.14.5, with libmilter
    <li>Bind 9.4.2-P2 (+ patches)
    <li>Lynx 2.8.7rel.2 with HTTPS and IPv6 support (+ patches)
    <li>Sudo 1.7.2p8
    <li>Ncurses 5.7
    <li>Heimdal 0.7.2 (+ patches)
    <li>Arla 0.35.7
    <li>Binutils 2.15 (+ patches)
    <li>Gdb 6.3 (+ patches)
    </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.1 on your machine:
<p>
<ul>
<li>CD1:5.1/i386/INSTALL.i386
<p>
<li>CD2:5.1/amd64/INSTALL.amd64
<li>CD2:5.1/macppc/INSTALL.macppc
<p>
<li>CD3:5.1/sparc64/INSTALL.sparc64
<p>
<li>FTP:.../OpenBSD/5.1/alpha/INSTALL.alpha
<li>FTP:.../OpenBSD/5.1/armish/INSTALL.armish
<li>FTP:.../OpenBSD/5.1/hp300/INSTALL.hp300
<li>FTP:.../OpenBSD/5.1/hppa/INSTALL.hppa
<li>FTP:.../OpenBSD/5.1/landisk/INSTALL.landisk
<li>FTP:.../OpenBSD/5.1/loongson/INSTALL.loongson
<li>FTP:.../OpenBSD/5.1/mvme68k/INSTALL.mvme68k
<li>FTP:.../OpenBSD/5.1/mvme88k/INSTALL.mvme88k
<li>FTP:.../OpenBSD/5.1/sgi/INSTALL.sgi
<li>FTP:.../OpenBSD/5.1/socppc/INSTALL.socppc
<li>FTP:.../OpenBSD/5.1/sparc/INSTALL.sparc
<li>FTP:.../OpenBSD/5.1/vax/INSTALL.vax
<li>FTP:.../OpenBSD/5.1/zaurus/INSTALL.zaurus
</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.1/i386/floppy51.fs</i> to a floppy and boot via the floppy drive.

<p>
Use <i>CD1:5.1/i386/floppyB51.fs</i> instead for greater SCSI controller
support, or <i>CD1:5.1/i386/floppyC51.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.1/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.1 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.1/amd64/floppy51.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>
Put 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
/5.1/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.1/sparc64/floppy51.fs</i> or <i>CD3:5.1/sparc64/floppyB51.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.1/sparc64/miniroot51.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.1/alpha/floppy51.fs</i> or
<i>FTP:5.1/alpha/floppyB51.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>miniroot51.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>miniroot51.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/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/sgi:</font></h3>
<ul>
<p>
To install on an O2, burn cd51.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.

<p>
On other systems, or 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.1/sparc/bsd.rd</strong>
or
&gt; <strong>b sd(0,6,0)5.1/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>floppy51.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
openbsd51_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.0 system, and do not want to reinstall,
upgrade instructions and advice can be found in the
<a href="faq/upgrade51.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>
# <strong>cd ports</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;apropos=0&amp;sektion=1&amp;manpath=OpenBSD+Current&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 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:
<p>
<ul><pre>
# <strong>cd [portsdir]/; cvs -d anoncvs@server.openbsd.org:/cvs update -Pd -rOPENBSD_5_1</strong>
</pre></ul>
<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 through FTP. Updated
packages for the 5.1 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 ports@openbsd.org is a good
place to know.
<p>

<hr>
<a href="index.html"><img height="24" width="24" src="back.gif" border="0"
alt="OpenBSD"></a>
<a href="mailto:www@openbsd.org">www@openbsd.org</a>
<br><small>
$OpenBSD: 51.html,v 1.13 2012/03/15 12:19:59 sperreault Exp $
</small>

</body>
</html>