www/33.html - diff

Return to 33.html CVS log

Up to [local] / www

Diff for /www/33.html between version 1.53 and 1.54

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

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

Line 1

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<!doctype html>

<html>

<head>

<title>OpenBSD 3.3</title>

</head>

<style>

#sourcecode h3 {

color: var(--red);

}

#sourcecode p {

margin-left: 2.75em;

}

<h2>

#sourcecode blockquote {

margin-left: 4.5em;

}

</style>

3.3

</h2>

<table>

<tr>

<td>

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

<img width="255" height="343"

src="images/Barbarian.gif" alt="OpenBSD 3.3 logo"></a>

src="images/Barbarian.gif" alt="Barbarian"></a>

<p>

<td>

Released May 1, 2003<br>

<br>

3.3 Song: <a href="lyrics.html#33">"Puff the Barbarian"</a>

<br>

Line 33

Line 45

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

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

one of the mirror sites.

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

of bugs and workarounds.

Line 44

Line 56

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

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

to 3.3.

Line 113

Line 126

<li>An incredible amount of enhancements and stability improvements to

our packet filter, <a

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

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

including:

<ul>

<li>Queue, a bandwidth management system (uses altq underneath)

Line 125

Line 138

<li>Full CIDR support

<li>Early checksum verification return on invalid packets

<li>Performance boost: large rulesets load much faster now

<li><a href="https://man.openbsd.org/?query=spamd">spamd</a>,

<li><a href="https://man.openbsd.org/spamd">spamd</a>,

a spam deferral daemon, which SMTP connections can be redirected to.

This daemon handles connections based on black lists and white lists,

tar-pits the connections, and ensures that the spammer knows why their

Line 165

Line 178

<li> and much more.

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

Line 215

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

Line 222

Line 239

<p>

To make a boot floppy under MS-DOS, use the "rawrite" utility located

at <i>CD:/3.3/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".

at <i>CD:/3.3/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#MkFlop">this page</a>.

</ul>

<h3>OpenBSD/macppc:</h3>

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

</ul>

<h3>OpenBSD/vax:</h3>

<p>

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

<ul>

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>

The 3.3 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.3/sparc/bsd.rd</strong>

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

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

> <kbd>b sd(0,6,0)3.3/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.3/sparc/floppy33.fs" 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.

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

Line 291

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>

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

<p>

Line 296

Line 309

<p>

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

</ul>

<h3>OpenBSD/alpha:</h3>

<p>

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

Write <i>FTP:3.3/alpha/floppy33.fs</i> or

<ul>

<p>Write <i>FTP:3.3/alpha/floppy33.fs</i> or

<i>FTP:3.3/alpha/floppyB33.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>

<h3>OpenBSD/hp300:</h3>

<p>

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

<ul>

<p>

Boot over the network by following the instructions in INSTALL.hp300.

</ul>

<h3>OpenBSD/hppa:</h3>

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

<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

<i>FTP:3.3/mac68k/utils</i> onto your hard disk. Run Mkfs to create your

Line 336

Line 341

"BSD/Mac68k Installer" to copy all the sets in <i>FTP:3.3/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>

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

</section>

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

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

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

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>

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

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

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

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

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

</pre></ul>

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

Line 377

Line 384

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 the <a href="faq/faq15.html">ports</a> page

Line 405

Line 414

on most architectures (over 2000 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 413

Line 422

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

Line 436

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>