www/29.html - diff

Return to 29.html CVS log

Up to [local] / www

Diff for /www/29.html between version 1.6 and 1.7

version 1.6, 2001/04/25 19:41:39

version 1.7, 2001/04/25 20:53:18

Line 176

Please refer to the following files on the two CDROM's for extensive

details on how to install OpenBSD 2.9 on your machine:

<p>

<dl>

<ul>

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

<li> CD1:2.9/powerpc/INSTALL.powerpc

<li> CD1:2.9/vax/INSTALL.vax

Line 188

<li> CD2:2.9/hp300/INSTALL.hp300

<li> CD2:2.9/sun3/INSTALL.sun3

<p>

<li>The alpha release is available on the ftp sites, but not

<li>The alpha release is available on the ftp sites, but not on the CDs.

on the CDs.

</ul>

</dl>

<hr>

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

<p>

<h3><font color=#e00000>OpenBSD/i386:</font></h3>

<ul>

<p>

Play with your BIOS options, and see if you can enable booting off a

CD; try using CD1. If not, write CD1:2.9/i386/floppy29.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.9/tools/rawrite.exe. Under

Unix, use "dd if=<file> of=/dev/<device> 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><font color=#e00000>sparc:</font></h3>

</ul>

<p>

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

<ul>

<p>

To boot off CD2, type "boot cdrom 2.9/sparc/bsd.rd", or

"b sd(0,6,0)2.9/sparc/bsd.rd" depending on your ROM version.

Alternatively, write CD2:2.9/sparc/floppy29.fs to a floppy and boot it

using "boot floppy" or "boot fd()" depending on your ROM version.

</ul>

<p>

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

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

<ul>

<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.9/amiga/utils/loadbsd CD0:2.9/amiga/bsd.rd".

</ul>

<p>

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

<ul>

<p>

You can boot over the network by following the instructions in

INSTALL.hp300.

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

Line 236

Line 252

BSD/Mac68k Installer to copy all the sets in CD2:2.9/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>

<p>

<h3><font color=#e00000>OpenBSD/sun3:</font></h3>

<ul>

<p>

Get the release via ftp. Then, you can either setup a diskless boot or

create an installation tape, as described in INSTALL.sun3.

</ul>

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

<p>

<pre>

# mkdir -p /usr/src

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

# cd /usr/src

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

# tar xvfz /tmp/src.tar.gz

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

</pre>

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

<p>

<pre>

# mkdir -p /usr/src/sys

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

# cd /usr/src

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

# tar xvfz /tmp/srcsys.tar.gz

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

</pre>

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

Line 271

Line 293

results in a much faster initial CVS update than you could expect from

a fresh checkout of the full OpenBSD source tree.

<p>

</ul>

<hr>

<p>

Line 279

Line 301

<p>

A ports tree archive is also provided. To extract:

<p>

<pre>

# cd /usr

# <strong>cd /usr</strong>

# tar xvfz /tmp/ports.tar.gz

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

# cd ports

# <strong>cd ports</strong>

# ls

</pre></ul>

...

</pre>

<p>

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

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

read <a href=ports.html>http://www.OpenBSD.org/ports.html</a>

if you know nothing about ports

at this point. This text is not a manual of how to use ports.

Line 301

Line 321

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/

As we said, ports will be growing a lot in the future. The <i>ports/</i>

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

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>

<pre>

# cd [portsdir]/; cvs -d anoncvsserver.openbsd.org:/cvs update -PAd

# <strong>cd [portsdir]/; cvs -d anoncvsserver.openbsd.org:/cvs update -PAd</strong>

</pre>

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