24.html

<!doctype html>
<html lang=en id=release>
<meta charset=utf-8>

<title>OpenBSD 2.4</title>
<meta name="description" content="OpenBSD 2.4">
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="stylesheet" type="text/css" href="openbsd.css">
<link rel="canonical" href="https://www.openbsd.org/24.html">
<style>
#OpenBSD + table td {
	vertical-align: middle !important;
}
</style>

<h2 id=OpenBSD>
<a href="index.html">
<i>Open</i><b>BSD</b></a>
2.4
</h2>

<table>
<tr>
<td>
<a href=images/openbsd24_cover.gif>
<img src=images/cd24-s.gif alt="CD 2.4"></a>
<td>
Released December 1, 1998.<br>
Copyright 1997-1998, Theo de Raadt.<br>
<cite class=isbn>ISBN - 0-9683637-2-5</cite>.

<ul>
<li>See the information on <a href="ftp.html">the FTP page</a> for
    a list of mirror machines.
<li>Go to the <code class=reldir>pub/OpenBSD/2.4/</code> directory on
    one of the mirror sites.
<li>Have a look at <a href="errata24.html">The 2.4 Errata page</a> for a list
    of bugs and workarounds.
</ul>
<p>
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 <code>ports.tar.gz</code>.
</table>

<hr>

<section id=install>
<h3>How to install</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.

<hr>
Please refer to the following files on the two CDROMs for extensive
details on how to install OpenBSD 2.4 on your machine:

<ul>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/2.4/i386/INSTALL.i386">
	.../OpenBSD/2.4/i386/INSTALL.i386 (on CD1)</a>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/2.4/sparc/INSTALL.sparc">
	.../OpenBSD/2.4/sparc/INSTALL.sparc (on CD1)</a>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/2.4/powerpc/INSTALL.powerpc">
	.../OpenBSD/2.4/powerpc/INSTALL.powerpc (on CD1)</a>
<p>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/2.4/alpha/INSTALL.alpha">
	.../OpenBSD/2.4/alpha/INSTALL.alpha (on CD2)</a>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/2.4/amiga/INSTALL.amiga">
	.../OpenBSD/2.4/amiga/INSTALL.amiga (on CD2)</a>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/2.4/mac68k/INSTALL.mac68k">
	.../OpenBSD/2.4/mac68k/INSTALL.mac68k (on CD2)</a>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/2.4/hp300/INSTALL.hp300">
	.../OpenBSD/2.4/hp300/INSTALL.hp300 (on CD2)</a>
<p>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/2.4/pmax/INSTALL.pmax">
	.../OpenBSD/2.4/pmax/INSTALL.pmax</a>
</ul>
</section>

<hr>

<section id=quickinstall>
<p>
Quick installer information for people familiar with OpenBSD, and the
use of the new "disklabel -E" command.  If you are at all confused when
installing OpenBSD, read the relevant INSTALL.* file as listed above!

<h3>OpenBSD/i386:</h3>
<p>
Play with your BIOS options, and see if you can enable booting off a
CD; try using CD1.  If not, write CD1:2.4/i386/floppy24.fs to a
floppy, then boot that.  If you are mixing OpenBSD with another
operating system, you will surely need to read the INSTALL.i386
document.
<p>
To make a floppy under MS-DOS, use /2.4/tools/rawrite.exe.  Under
Unix, use "dd if=&lt;file&gt; of=/dev/&lt;device&gt; bs=32k" (where device could
be "floppy" or "rfd0c" or "rfd0a").  Use properly formatted perfect
floppies with NO BAD BLOCKS or you will lose.

<h3>OpenBSD/sparc:</h3>
<p>
To boot off CD1, type "boot cdrom 2.4/sparc/bsd.rd", or
"b sd(0,6,0)2.4/sparc/bsd.rd" depending on your ROM version.
Alternatively, write CD1:2.4/sparc/floppy24.fs to a floppy and boot it
using "boot fd()" or "boot floppy" depending on your ROM version.
Finally, a third alternative is to write CD1:2.4/sparc/kc.fs and
CD1:2.4/sparc/inst.fs to two separate floppies.  Then insert "kc.fs",
and boot as described above.  As soon as the floppy drive ejects a
floppy, insert "inst.fs".  Answer a bunch of questions.  Reboot from
the "kc.fs" floppy.  This time, when the floppy is ejected simply
re-insert "kc.fs" again and answer a different set of questions.

<h3>OpenBSD/amiga:</h3>
<p>
Create BSD partitions according to INSTALL.amiga's preparation section.
Mount the CD2 under AmigaOS as device CD0: Next, execute the following
CLI command: "CD0:2.4/amiga/utils/loadbsd CD0:2.4/amiga/bsd.rd".

<h3>OpenBSD/hp300:</h3>
<p>
You can boot over the network by following the instructions in
INSTALL.hp300.

<h3>OpenBSD/alpha:</h3>
<p>
Your alpha must use SRM firmware (not ARC).  If you have a CDROM, you
can try "boot -fi 2.4/alpha/bsd.rd dkaX" (use "show device" to find your
CDROM drive identifier). Otherwise, write CD2:2.4/alpha/floppy.fs to a
floppy and boot that by typing "boot dva0".  If this fails, you can place
bsd.rd on some other device and boot it, or use the provided simpleroot.

<h3>OpenBSD/mac68k:</h3>
<p>
Boot MacOS as normal and partition your disk with the appropriate A/UX
configurations.  Then, extract the Macside utilities from
CD1:2.4/mac68k/utils 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 CD1:2.4/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.
</section>

<hr>

<section id=sourcecode>
<h3>Notes about the source code</h3>
<p>
<code>src.tar.gz</code> contains a source archive starting at <code>/usr/src</code>.
This file contains everything you need except for the kernel sources, which are
in a separate archive.  To extract:
<blockquote><pre>
# <kbd>mkdir -p /usr/src</kbd>
# <kbd>cd /usr/src</kbd>
# <kbd>tar xvfz /tmp/src.tar.gz</kbd>
</pre></blockquote>
<p>
<code>sys.tar.gz</code> contains a source archive starting at <code>/usr/src/sys</code>.
This file contains all the kernel sources you need to rebuild kernels.
To extract:
<blockquote><pre>
# <kbd>mkdir -p /usr/src/sys</kbd>
# <kbd>cd /usr/src</kbd>
# <kbd>tar xvfz /tmp/srcsys.tar.gz</kbd>
</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
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.
</section>

<hr>

<section id=ports>
<h3>Ports Tree</h3>
<p>
A ports tree archive is also provided.  To extract:
<blockquote><pre>
# <kbd>cd /usr</kbd>
# <kbd>tar xvfz /tmp/ports.tar.gz</kbd>
</pre></blockquote>
<p>
The ports/ subdirectory is a checkout of the OpenBSD ports tree.  Go
read <a href="faq/faq15.html">https://www.OpenBSD.org/faq/faq15.html</a>
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>
Certainly, the OpenBSD ports system is not complete.  This is because
the full integration of ports into the OpenBSD environment is still a
young project as of this release.  We believe the ports that are
provided here are stable, but it is most important to realize that
ports will continue to grow a great deal in functionality in the
future.
<p>
As we said, ports will be growing a lot in the future.  The ports/
directory represents a CVS (see the manpage for cvs(1) 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 ports/ tree
available on a read-write medium and update the tree with a command
like:
<blockquote><pre>
# <kbd>cd [portsdir]/; cvs -d anoncvs@server.openbsd.org:/cvs update -Pd</kbd>
</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
server.]
<p>
Again, it is important to see the webpage for specific instructions as
this is a new service which hasn't yet been ironed out
completely.
<p>
Finally, despite ports' youth, help is never far.  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.
</section>