www/31.html - diff

Return to 31.html CVS log

Up to [local] / www

Diff for /www/31.html between version 1.38 and 1.39

version 1.38, 2019/04/24 15:54:53

version 1.39, 2019/05/27 22:55:18

Line 1

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML Strict//EN">

<!doctype html>

<html>

<head>

<title>OpenBSD 3.1</title>

</head>

<style>

#sourcecode h3 {

color: var(--red);

}

#sourcecode p {

margin-left: 2.75em;

}

<h2>

#sourcecode blockquote {

margin-left: 4.5em;

}

</style>

3.1

</h2>

<table>

<tr>

<td>

<img align="left" width="255" height="323" hspace="24"

src="images/Systemagic.jpg"></a>

<td>

<p>

Released May 19, 2002<br>

<br>

3.1 Song: <a href="lyrics.html#31">"Systemagic"</a>

<br>

Line 32

Line 43

<ul>

<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/3.1/</font> directory on

<li>Go to the <code class=reldir>pub/OpenBSD/3.1/</code> directory on

one of the mirror sites.

<li>Have a look at <a href="errata31.html">The 3.1 Errata page</a> for a list

of bugs and workarounds.

Line 43

Line 54

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 ports.tar.gz.

</table>

<hr>

<p>

<p>

This is a partial list of new features and systems included in OpenBSD 3.1.

For a comprehensive list, see the <a href="plus31.html">changelog</a> leading

to 3.1.

Line 84

Line 96

<p>

<li>A lot of enhancements to our new packet filter, <a

href="https://man.openbsd.org/?query=pf&sektion=4">pf</a>,

href="https://man.openbsd.org/pf.4">pf</a>,

including performance improvements, as well as the ability to filter other

protocols than the usual tcp, udp and icmp, such as esp.

<p>

<li>An utility to achieve per-user pf rules changes, typically intended for

gateways, <a

href="https://man.openbsd.org/?query=authpf&sektion=8">authpf</a>.

href="https://man.openbsd.org/authpf.8">authpf</a>.

<p>

<li>The in-kernel software <a

href="https://man.openbsd.org/?query=raid&sektion=4">raid</a>

href="https://man.openbsd.org/raid.4">raid</a>

(RAIDframe) can now automatically detect and configure its raid devices at boot.

Taking advantage of this, the system can have its root partition directly

mounted from an auto-detected raid partition.

Line 125

Line 137

<li>Many improvements for security and reliability (look for the red

print in the <a href="plus31.html">complete changelog</a>).

<p>

</ul>

</section>

<hr>

<h3>How to install</h3>

<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

Line 148

Line 161

<ul>

<li> CD1:3.1/i386/INSTALL.i386</li>

<li> CD1:3.1/alpha/INSTALL.alpha</li>

<p>

</ul>

<ul>

<li> CD2:3.1/macppc/INSTALL.macppc</li>

<li> CD2:3.1/vax/INSTALL.vax</li>

<p>

</ul>

<ul>

<li> CD3:3.1/sparc/INSTALL.sparc</li>

<li> CD3:3.1/sparc64/INSTALL.sparc64</li>

<p>

</ul>

Only available via FTP:<br>

<ul>

<li> CD4:3.1/mvme68k/INSTALL.mvme68k</li>

<li> CD4:3.1/amiga/INSTALL.amiga</li>

<li> CD4:3.1/mac68k/INSTALL.mac68k</li>

Line 163

Line 179

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

<h3>OpenBSD/i386:</h3>

<ul>

<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.1/i386/floppy31.fs</i> to a floppy and boot via the floppy drive.

Line 182

Line 199

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 "rawrite" utility located at <i>CD:/3.1/tools/rawrite.exe</i>. To make the boot floppy under a Unix OS, use the <a href="https://man.openbsd.org/?query=dd&sektion=1">dd(1)</a> utility. The following is an example usage of <a href="https://man.openbsd.org/?query=dd&sektion=1">dd(1)</a>, where the device could be "floppy", "rfd0c", or "rfd0a".

To make a boot floppy under MS-DOS, use the "rawrite" utility located at <i>CD:/3.1/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 "floppy", "rfd0c", or "rfd0a".

# <strong>dd if=<file> of=/dev/<device> bs=32k</strong>

</pre></ul>

</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">this page</a>.

</ul>

<h3>OpenBSD/alpha:</h3>

<p>

<h3><font color="#e00000">OpenBSD/alpha:</font></h3>

<ul>

<p>

At the SRM prompt, enter <i>boot -fi 3.1/alpha/bsd.rd dka6</i> where <i>dka6</i>

is the short name for the CDROM drive (you can check with <i>show dev</i>).

Line 206

Line 221

<p>

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

</ul>

<h3>OpenBSD/macppc:</h3>

<p>

<h3><font color="#e00000">OpenBSD/macppc:</font></h3>

<ul>

<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.1/macppc/bsd.rd</i>

</ul>

<h3>OpenBSD/hp300:</h3>

<p>

<h3><font color="#e00000">OpenBSD/hp300:</font></h3>

<ul>

<p>

Put the CD4 in your CDROM drive and press the spacebar during the poweron

self-test. Enter the boot choice that corresponds to <i>SYS_CDBOOT</i>.

<p>

Alternatively, you can boot over the network by following the instructions in

INSTALL.hp300.

</ul>

<h3>OpenBSD/amiga:</h3>

<p>

<h3><font color="#e00000">OpenBSD/amiga:</font></h3>

<ul>

<p>

Create BSD partitions according to INSTALL.amiga's preparation section.

Mount the CD4 under AmigaOS as device CD0: Next, execute the following

CLI command: "CD0:3.1/amiga/utils/loadbsd CD0:3.1/amiga/bsd.rd".

</ul>

<h3>OpenBSD/mac68k:</h3>

<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

CD4:3.1/mac68k/utils onto your hard disk. Run Mkfs to create your

Line 252

Line 258

BSD/Mac68k Installer to copy all the sets in CD4:3.1/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.

</ul>

<h3>OpenBSD/mvme68k:</h3>

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

<h3>OpenBSD/vax:</h3>

<p>

<h3><font color="#e00000">OpenBSD/vax:</font></h3>

<ul>

<p>

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

</ul>

<h3>OpenBSD/sparc:</h3>

<p>

<h3><font color="#e00000">OpenBSD/sparc:</font></h3>

<ul>

<p>

The 3.1 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.

> <strong>boot cdrom 3.1/sparc/bsd.rd</strong>

> <kbd>boot cdrom 3.1/sparc/bsd.rd</kbd>

> <strong>b sd(0,6,0)3.1/sparc/bsd.rd</strong>

> <kbd>b sd(0,6,0)3.1/sparc/bsd.rd</kbd>

</pre></ul>

</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 "CD3:3.1/sparc/floppy31.fs" to a floppy. For more information see <a href="faq/faq4.html#4.1">this page</a>. To boot from the floppy use one of the two commands listed below, depending on the version of your ROM.

> <strong>boot floppy</strong>

> <kbd>boot floppy</kbd>

> <strong>boot fd()</strong>

</pre></ul>

</pre></blockquote>

<p>

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

Line 299

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>

<h3>OpenBSD/sparc64:</h3>

<p>

<h3><font color="#e00000">OpenBSD/sparc64:</font></h3>

<ul>

<p>

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

<p>

Line 319

Line 317

<p>

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

</ul>

</section>

<h3>Notes about the source code:</h3>

<p>

<h3><font color="#e00000">Notes about the source code:</font></h3>

<ul>

<p>

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:

# <kbd>mkdir -p /usr/src</kbd>

# <kbd>cd /usr/src</kbd>

# <kbd>tar xvfz /tmp/src.tar.gz</kbd>

</pre></blockquote>

<p>

# <strong>mkdir -p /usr/src</strong>

# <strong>cd /usr/src</strong>

# <strong>tar xvfz /tmp/src.tar.gz</strong>

</pre></ul>

<p>

srcsys.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:

# <kbd>mkdir -p /usr/src/sys</kbd>

# <kbd>cd /usr/src</kbd>

# <kbd>tar xvfz /tmp/srcsys.tar.gz</kbd>

</pre></blockquote>

<p>

# <strong>mkdir -p /usr/src/sys</strong>

# <strong>cd /usr/src</strong>

# <strong>tar xvfz /tmp/srcsys.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 at <a href=anoncvs.html>http://www.OpenBSD.org/anoncvs.html</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>

</section>

</section>

<hr>

<h3>Ports Tree</h3>

<p>

<h3><font color="#0000e0">Ports Tree</font></h3>

<p>

A ports tree archive is also provided. To extract:

<p>

# <strong>cd /usr</strong>

# <kbd>cd /usr</kbd>

# <strong>tar xvfz /tmp/ports.tar.gz</strong>

# <kbd>tar xvfz /tmp/ports.tar.gz</kbd>

# <strong>cd ports</strong>

# <kbd>cd ports</kbd>

</pre></ul>

</pre></blockquote>

<p>

The <i>ports/</i> subdirectory is a checkout of the OpenBSD ports tree. Go

read <a href="faq/faq15.html">http://www.OpenBSD.org/faq/faq15.html</a>

Line 379

Line 382

on most architectures (over 1500 packages build on i386, for instance).

<p>

The <i>ports/</i> directory represents a CVS (see the manpage for

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

Line 387

Line 390

available on a read-write medium and update the tree with a command

like:

<p>

# <strong>cd [portsdir]/; cvs -d anoncvs@server.openbsd.org:/cvs update -Pd -rOPENBSD_3_1</strong>

</pre></ul>

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

Line 401

Line 404

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>

</section>

</body>

</html>