=================================================================== RCS file: /cvsrepo/anoncvs/cvs/www/24.html,v retrieving revision 1.30 retrieving revision 1.31 diff -u -r1.30 -r1.31 --- www/24.html 2019/05/27 22:55:18 1.30 +++ www/24.html 2019/06/12 20:57:16 1.31 @@ -8,17 +8,9 @@
pub/OpenBSD/2.4/
directory on
@@ -56,7 +47,6 @@
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 @@ -71,19 +61,26 @@ details on how to install OpenBSD 2.4 on your machine:
+
+
-
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 @@ -106,7 +103,7 @@ be "floppy" or "rfd0c" or "rfd0a"). Use properly formatted perfect floppies with NO BAD BLOCKS or you will lose.
-
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. @@ -119,18 +116,18 @@ the "kc.fs" floppy. This time, when the floppy is ejected simply re-insert "kc.fs" again and answer a different set of questions.
-
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".
-
You can boot over the network by following the instructions in INSTALL.hp300.
-
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 @@ -138,7 +135,7 @@ 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.
-
Boot MacOS as normal and partition your disk with the appropriate A/UX configurations. Then, extract the Macside utilities from @@ -149,52 +146,53 @@ Booter with the location of your kernel and boot the system. +
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:
-
-# mkdir -p /usr/src -# cd /usr/src -# tar xvfz /tmp/src.tar.gz -+
+# mkdir -p /usr/src +# cd /usr/src +# tar xvfz /tmp/src.tar.gz +
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:
-
-# mkdir -p /usr/src/sys -# cd /usr/src -# tar xvfz /tmp/srcsys.tar.gz -+
+# mkdir -p /usr/src/sys +# cd /usr/src +# tar xvfz /tmp/srcsys.tar.gz +
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 http://www.OpenBSD.org/anoncvs.html. +described here. 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.
A ports tree archive is also provided. To extract:
-
-# cd /usr -# tar xvfz /tmp/ports.tar.gz -# cd ports -# ls ++# cd /usr +# tar xvfz /tmp/ports.tar.gz +# cd ports +# ls ... -+
The ports/ subdirectory is a checkout of the OpenBSD ports tree. Go read http://www.OpenBSD.org/faq/faq15.html @@ -218,9 +216,9 @@ available on a read-write medium and update the tree with a command like:
-
-# cd [portsdir]/; cvs -d anoncvs@server.openbsd.org:/cvs update -Pd -+
+# cd [portsdir]/; cvs -d anoncvs@server.openbsd.org:/cvs update -Pd +
[Of course, you must replace the local directory and server name here with the location of your ports collection and a nearby anoncvs @@ -232,6 +230,6 @@
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 ports@openbsd.org is a good -place to know. +would like to know more, the mailing list +ports@openbsd.org is a good place to know.