version 1.1, 2004/08/26 02:32:24 |
version 1.2, 2004/08/26 09:39:56 |
|
|
<font color="#e00000">ISBN 0-9731791-4-7</font> |
<font color="#e00000">ISBN 0-9731791-4-7</font> |
<p> |
<p> |
|
|
<br> |
<a href="#new">What's New</a><br> |
<br> |
<a href="#install">How to install</a><br> |
<br> |
<a href="#ports">How to use the ports tree</a><br> |
<br> |
<a href="orders.html">Ordering a CD set</a><br> |
<br> |
|
<br> |
<p> |
<br> |
<h3><font color="#0000e0"> |
<br> |
To get the files for this release: |
<br> |
<ul> |
<br> |
<li>Order a CDROM from our <a href="orders.html">ordering system</a>. |
<br> |
<li>See the information on <a href="ftp.html">The FTP page</a> for |
<br> |
a list of mirror machines. |
<br> |
<li>Go to the <font color="#e00000">pub/OpenBSD/3.6/</font> directory on |
<br> |
one of the mirror sites. |
<br> |
<li>Briefly read the rest of this document. |
<br> |
<!-- |
<br> |
<li>Have a look at <a href="errata.html">The 3.6 Errata page</a> for a list |
<br> |
of bugs and workarounds. |
<br> |
--> |
<br> |
<li>See a <a href="plus.html">detailed log of changes</a> between the |
<br> |
3.5 and 3.6 releases. |
<br> |
</ul> |
<br> |
</font></h3> |
<br> |
<br clear=all> |
<br> |
|
<br> |
<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, |
|
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. |
|
<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 3.6. |
|
For a comprehensive list, see the <a href="plus.html">changelog</a> leading |
|
to 3.6. |
|
<p> |
|
|
|
<ul> |
|
|
|
<li> New platform: |
|
<ul> |
|
<li><a href="luna88k.html">OpenBSD/luna88k</a><br> |
|
Expanding the mvme88k porting effort by supporting Omron's line of |
|
88100-based workstations. |
|
</ul> |
|
<p> |
|
|
|
<li> SMP support on <a href="i386.html">OpenBSD/i386</a> and <a |
|
href="amd64.html">OpenBSD/amd64</a> platforms. |
|
<p> |
|
|
|
<li> New functionality: |
|
<ul> |
|
<li>A new dhcp |
|
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=dhcpd&sektion=8">server</a> |
|
and |
|
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=dhclient&sektion=8">client</a> |
|
implementation, featuring privilege separation and safe defaults. |
|
<li>A clean |
|
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ntpd&sektion=8">ntp |
|
daemon</a> which ought to fit the needs of most ntp users. |
|
<li><a href="http://www.openbsd.org/cgi-bin/man.cgi?query=pfctl&sektion=8">pfctl</a> |
|
now provides a <i>rules optimizer</i>, to help improving filtering speed. |
|
</ul> |
|
<p> |
|
|
|
<li>Improved hardware support, including: |
|
<ul> |
|
<li>Sangoma T1 and E1 cards |
|
(<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=san&sektion=4">san</a>) |
|
<li>Jumbo frames are now working reliably on |
|
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=em&sektion=4">em</a>, |
|
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=sk&sektion=4">sk</a> |
|
and |
|
<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ti&sektion=4">ti</a> |
|
adapters. |
|
<li>USB 2.0 |
|
(<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ehci&sektion=4">ehci</a>) |
|
controllers. |
|
<li>AIC79xx-based Ultra320 SCSI adapters, such as the Adaptec 29320 and |
|
39320 |
|
(<a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ahd&sektion=4">ahd</a>) |
|
</ul> |
|
<p> |
|
|
|
<li> Improved NFS performance and reliability. |
|
|
|
<li> Shared libraries on the <a href="hppa.html">OpenBSD/hppa</a> port. |
|
|
|
<li> Over 2700 ports, 2500 pre-built packages. |
|
<p> |
|
|
|
<li>Many improvements for security and reliability (look for the red |
|
print in the <a href="plus.html">complete changelog</a>). |
|
<p> |
|
|
|
<li>As ususal, 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="amd64.html">OpenBSD/cats</a>, |
|
<a href="cats.html">OpenBSD/hppa</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.9: |
|
<ul> |
|
<li>sshd now re-executes itself on accepting a new connection. This security |
|
measure ensures that all execute-time randomisations are reapplied for each |
|
connection rather than once, for the master process' lifetime. This includes |
|
mmap and malloc mappings, shared library addressing, shared library mapping |
|
order, ProPolice and StackGhost cookies on architectures that support |
|
such things. |
|
<li>Selected environment variables can now be passed between the |
|
client and the server. |
|
<li>Session multiplexing: a single ssh connection can now carry |
|
multiple login/command/file transfer sessions. |
|
</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 |
|
(+ <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=gcc-local&sektion=1">patches</a>) |
|
and 3.3.2 |
|
(+ <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=gcc-local&sektion=1">patches</a>) |
|
<li>Perl 5.8.5 (+ patches) |
|
<li>Apache 1.3.29, mod_ssl 2.8.16, DSO support (+ patches) |
|
<li>OpenSSL 0.9.7d (+ patches) |
|
<li>Groff 1.15 |
|
<li>Sendmail 8.13.0, with libmilter |
|
<li>Bind 9.2.3 (+ patches) |
|
<li>Lynx 2.8.5rel.2 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 0.35.7 |
|
<li>Gdb 6.1 |
|
</ul> |
|
<p> |
|
|
|
</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 3.6 on your machine: |
|
<p> |
|
<ul> |
|
<li>CD1:3.6/i386/INSTALL.i386 |
|
<li>CD1:3.6/vax/INSTALL.vax |
|
<p> |
|
<li>CD2:3.6/amd64/INSTALL.amd64 |
|
<li>CD2:3.6/macppc/INSTALL.macppc |
|
<p> |
|
<li>CD3:3.6/sparc/INSTALL.sparc |
|
<li>CD3:3.6/sparc64/INSTALL.sparc64 |
|
<p> |
|
<li>FTP:.../OpenBSD/3.6/alpha/INSTALL.alpha |
|
<li>FTP:.../OpenBSD/3.6/cats/INSTALL.cats |
|
<li>FTP:.../OpenBSD/3.6/hp300/INSTALL.hp300 |
|
<li>FTP:.../OpenBSD/3.6/hppa/INSTALL.hppa |
|
<li>FTP:.../OpenBSD/3.6/luna88k/INSTALL.luna88k |
|
<li>FTP:.../OpenBSD/3.6/mac68k/INSTALL.mac68k |
|
<li>FTP:.../OpenBSD/3.6/mvme68k/INSTALL.mvme68k |
|
<li>FTP:.../OpenBSD/3.6/mvme88k/INSTALL.mvme88k |
|
</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:3.6/i386/floppy36.fs</i> to a floppy and boot via the floppy drive. |
|
|
|
<p> |
|
Use <i>CD1:3.6/i386/floppyB36.fs</i> instead for greater scsi controller |
|
support, or <i>CD1:3.6/i386/floppyC36.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 "rawrite" utility located |
|
at <i>CD1:3.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&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&sektion=1">dd(1) |
|
</a>, where the device could be "floppy", "rfd0c", or |
|
"rfd0a". |
|
|
|
<ul><pre> |
|
# <strong>dd if=<file> of=/dev/<device> 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">FAQ4.1</a>. |
|
</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/amd64:</font></h3> |
|
<ul> |
|
The 3.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:3.6/amd64/floppy36.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 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.6/macppc/bsd.rd</i> |
|
</ul> |
|
|
|
<p> |
|
<h3><font color="#e00000">OpenBSD/sparc:</font></h3> |
|
<ul> |
|
The 3.6 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. |
|
|
|
<ul><pre> |
|
ok <strong>boot cdrom 3.6/sparc/bsd.rd</strong> |
|
or |
|
> <strong>b sd(0,6,0)3.6/sparc/bsd.rd</strong> |
|
</pre></ul> |
|
|
|
<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.6/sparc/floppy36.fs</i> to a floppy. |
|
For more information see <a href="faq/faq4.html#MkFlop">FAQ4.1</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 |
|
> <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 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/sparc64:</font></h3> |
|
<ul> |
|
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.6/sparc64/floppy36.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.6/sparc64/miniroot36.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:3.6/alpha/floppy36.fs</i> or |
|
<i>FTP:3.6/alpha/floppyB36.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/cats:</font></h3> |
|
<ul> |
|
<p> |
|
After updating the firmware to at least ABLE 1.95 if necessary, boot |
|
<i>FTP:3.6/cats/bsd.rd</i> from an ABLE-supported device (such as a CD-ROM |
|
or an existing FFS or EXT2FS partition). |
|
</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#netboot">hppa platform page</a>. |
|
</ul> |
|
|
|
<p> |
|
<h3><font color="#e00000">OpenBSD/luna88k:</font></h3> |
|
<ul> |
|
<p> |
|
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. |
|
</ul> |
|
|
|
<p> |
|
<h3><font color="#e00000">OpenBSD/mac68k:</font></h3> |
|
<ul> |
|
<p> |
|
Boot MacOS as normal and partition your disk with the appropriate A/UX |
|
configurations. Then, extract the Macside utilities from |
|
<i>FTP:3.6/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>FTP:3.6/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. |
|
</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">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="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="ports.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&apropos=0&sektion=1&manpath=OpenBSD+Current&arch=i386&format=html"> |
|
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 anoncvsserver.openbsd.org:/cvs update -Pd -rOPENBSD_3_6</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 3.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 ports@openbsd.org is a good |
|
place to know. |
|
<p> |
|
|
<hr> |
<hr> |
<a href="index.html"><img height="24" width="24" src="back.gif" border="0" |
<a href="index.html"><img height="24" width="24" src="back.gif" border="0" |