Skip to content

Commit

Permalink
one small annoying nit turned into a 8323 line unification diff.
Browse files Browse the repository at this point in the history
  • Loading branch information
deraadt committed Jun 12, 2019
1 parent 984bbbd commit ceae977
Show file tree
Hide file tree
Showing 46 changed files with 1,815 additions and 1,945 deletions.
110 changes: 54 additions & 56 deletions 21.html
Original file line number Diff line number Diff line change
Expand Up @@ -8,17 +8,9 @@
<link rel="stylesheet" type="text/css" href="openbsd.css">
<link rel="canonical" href="https://www.openbsd.org/21.html">
<style>
#sourcecode h3, #ports h3 {
color: var(--red);
}

#release #OpenBSD + table td {
vertical-align: middle;
}

#release #quickinstall p {
margin-left: 0;
}
</style>

<h2 id=OpenBSD>
Expand All @@ -37,7 +29,6 @@ <h2 id=OpenBSD>
Copyright 1997, Theo de Raadt.<br>
<p>
<ul>
<li><strong>Order a CDROM from our ordering system.</strong>
<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.1/</code> directory on
Expand All @@ -55,7 +46,6 @@ <h2 id=OpenBSD>

<section id=install>
<h3>How to install</h3>

<p>
Following this are the instructions if you had purchased a CDROM set
instead of attempting to do
Expand All @@ -68,18 +58,28 @@ <h3>How to install</h3>
Please refer to the following files on the two CDROMs for extensive
details on how to install OpenBSD 2.1 on your machine:
<ul>
<li> CD1:2.1/i386/INSTALL.i386
<li> CD1:2.1/arc/INSTALL.arc
<li> CD1:2.1/mac68k/INSTALL.mac68k
<li> CD1:2.1/pmax/INSTALL.pmax
<li> CD1:2.1/sparc/INSTALL.sparc
<li> CD1:2.1/mvme68k/INSTALL.mvme68k
</ul>
<ul>
<li> CD2:2.1/amiga/INSTALL.amiga
<li> CD2:2.1/hp300/INSTALL.hp300
<li> CD2:2.1/alpha/INSTALL.alpha
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/2.1/i386/INSTALL.i386">
.../OpenBSD/2.1/i386/INSTALL.i386 (on CD1)</a>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/2.1/arc/INSTALL.arc">
.../OpenBSD/2.1/arc/INSTALL.arc (on CD1)</a>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/2.1/mac68k/INSTALL.mac68k">
.../OpenBSD/2.1/mac68k/INSTALL.mac68k (on CD1)</a>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/2.1/pmax/INSTALL.pmax">
.../OpenBSD/2.1/pmax/INSTALL.pmax (on CD1)</a>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/2.1/sparc/INSTALL.sparc">
.../OpenBSD/2.1/sparc/INSTALL.sparc (on CD1)</a>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/2.1/mvme68k/INSTALL.mvme68k">
.../OpenBSD/2.1/mvme68k/INSTALL.mvme68k (on CD1)</a>
<p>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/2.1/amiga/INSTALL.amiga">
.../OpenBSD/2.1/amiga/INSTALL.amiga (on CD2)</a>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/2.1/hp300/INSTALL.hp300">
.../OpenBSD/2.1/hp300/INSTALL.hp300 (on CD2)</a>
<li><a href="https://ftp.openbsd.org/pub/OpenBSD/2.1/alpha/INSTALL.alpha">
.../OpenBSD/2.1/alpha/INSTALL.alpha (on CD2)</a>
</ul>
</section>

<hr>

<section id=quickinstall>
Expand All @@ -88,7 +88,7 @@ <h3>How to install</h3>
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>i386:</h3>
<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.1/i386/floppy21.fs to a
Expand All @@ -101,14 +101,14 @@ <h3>i386:</h3>
be "floppy" or "rfd0c" or "rfd0a"). Use properly formatted perfect
floppies with NO BAD BLOCKS or you will lose.
<p>
<h3>ARC:</h3>
<h3>OpenBSD/arc:</h3>
<p>
Using CD1, tell the BOOT ROM to load the file CD1:\2.1\arc\bsd.rd. If
that does not work, create a MS-DOS filesystem using your vendor's arc
setup program, copy CD1:2.1/arc/bsd.rd to there and attempt to boot
it.
<p>
<h3>SPARC:</h3>
<h3>OpenBSD/sparc:</h3>
<p>
To boot off CD1, type "boot cdrom 2.1/sparc/bsd.rd", or
"b sd(0,6,0)2.1/sparc/bsd.rd" depending on your ROM version.
Expand All @@ -121,33 +121,33 @@ <h3>SPARC:</h3>
the "kc.fs" floppy. This time, when the floppy is ejected simply
re-insert "kc.fs" again and answer a different set of questions.
<p>
<h3>PMAX:</h3>
<h3>OpenBSD/pmax:</h3>
<p>
Write the simpleroot21.fs onto the start of the disk using dd on another
machine. After moving the disk drive, use "boot -f rz(0,0,0)/bsd"
(2100/3100) or "boot 5/rz0a/bsd" (5000). Alternatively, install via
network as described in detail in INSTALL.pmax.
<p>
<h3>AMIGA:</h3>
<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.1/amiga/utils/loadbsd CD0:2.1/amiga/bsd.rd".
<p>
<h3>HP300:</h3>
<h3>OpenBSD/hp300:</h3>
<p>
You can boot over the network by following the instructions in
INSTALL.hp300.
<p>
<h3>ALPHA:</h3>
<h3>OpenBSD/alpha:</h3>
<p>
Your alpha must use SRM firmware (not ARC). If you have a CDROM, you
can try "boot -fi 2.1/alpha/bsd.rd dkaX" (use "show device" to find your
CDROM drive identifier). Otherwise, write CD2:2.1/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.
<p>
<h3>MAC68K:</h3>
<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
Expand All @@ -157,44 +157,42 @@ <h3>MAC68K:</h3>
partitions. Finally, you will be ready to configure the BSD/Mac68k
Booter with the location of your kernel and boot the system.
<p>
<h3>MVME68K:</h3>
<h3>OpenBSD/mvme68k:</h3>
<p>
Theo has no real idea. In the rush to get everything else done, the
install stuff for the mvme68k was never completed. Enough pieces are
included so that a really skilled person could find a way to install
it; perhaps using netbooting. Good luck!
</section>
</section>

<hr>

<section id=sourcecode>
<h3>NOTES ABOUT THE SOURCE CODE:</h3>

<h3>Notes about the source code</h3>
<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
# cd /usr/src
# tar xvfz /tmp/src.tar.gz
</pre>
<blockquote><pre>
# <kbd>mkdir -p /usr/src</kbd>
# <kbd>cd /usr/src</kbd>
# <kbd>tar xvfz /tmp/src.tar.gz</kbd>
</pre></blockquote>
<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
# cd /usr/src
# tar xvfz /tmp/srcsys.tar.gz
</pre>
<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 at <a href=anoncvs.html>http://www.OpenBSD.org/anoncvs.html</a>.
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.
Expand All @@ -203,17 +201,17 @@ <h3>NOTES ABOUT THE SOURCE CODE:</h3>
<hr>

<section id=ports>
<h3>PORTS TREE</h3>
<h3>Ports Tree</h3>
<p>
A ports tree archive is also provided. To extract:
<p>
<pre>
# cd /usr
# tar xvfz /tmp/ports.tar.gz
# cd ports
# ls
<blockquote><pre>
# <kbd>cd /usr</kbd>
# <kbd>tar xvfz /tmp/ports.tar.gz</kbd>
# <kbd>cd ports</kbd>
# <kbd>ls</kbd>
...
</pre>
</pre></blockquote>
<p>
The ports/ subdirectory is a checkout of the OpenBSD ports tree. Go
read <a href=faq/faq15.html>http://www.OpenBSD.org/faq/faq15.html</a>
Expand All @@ -237,9 +235,9 @@ <h3>PORTS TREE</h3>
available on a read-write medium and update the tree with a command
like:
<p>
<pre>
# cd [portsdir]/; cvs -d [email protected]:/cvs update -Pd
</pre>
<blockquote><pre>
# <kbd>cd [portsdir]/; cvs -d [email protected]:/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
Expand All @@ -251,6 +249,6 @@ <h3>PORTS TREE</h3>
<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 [email protected] is a good
place to know.
would like to know more, the mailing list
<a href="mail.html">[email protected]</a> is a good place to know.
</section>
Loading

0 comments on commit ceae977

Please sign in to comment.