pub/OpenBSD/2.3/ directory on
--- 30,35 ----
***************
*** 56,62 ****
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 --- 47,52 ---- *************** *** 71,89 **** details on how to install OpenBSD 2.3 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.3/i386/floppy23.fs to a --- 93,99 ---- use of the new "disklabel -E" command. If you are at all confused when installing OpenBSD, read the relevant INSTALL.* file as listed above!
!
Play with your BIOS options, and see if you can enable booting off a CD; try using CD1. If not, write CD1:2.3/i386/floppy23.fs to a *************** *** 106,119 **** be "floppy" or "rfd0c" or "rfd0a"). Use properly formatted perfect floppies with NO BAD BLOCKS or you will lose.
!
Using CD1, tell the BOOT ROM to load the file CD1:\2.3\arc\bsd.rd. If that does not work, create a MS-DOS filesystem using your vendor's arc setup program, copy CD1:2.3/arc/bsd.rd to there and attempt to boot it.
!
To boot off CD1, type "boot cdrom 2.3/sparc/bsd.rd", or "b sd(0,6,0)2.3/sparc/bsd.rd" depending on your ROM version. --- 106,119 ---- be "floppy" or "rfd0c" or "rfd0a"). Use properly formatted perfect floppies with NO BAD BLOCKS or you will lose.
!
Using CD1, tell the BOOT ROM to load the file CD1:\2.3\arc\bsd.rd. If that does not work, create a MS-DOS filesystem using your vendor's arc setup program, copy CD1:2.3/arc/bsd.rd to there and attempt to boot it.
!
To boot off CD1, type "boot cdrom 2.3/sparc/bsd.rd", or "b sd(0,6,0)2.3/sparc/bsd.rd" depending on your ROM version. *************** *** 126,150 **** the "kc.fs" floppy. This time, when the floppy is ejected simply re-insert "kc.fs" again and answer a different set of questions.
!
Write the simpleroot23.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.
!
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.3/amiga/utils/loadbsd CD0:2.3/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.3/alpha/bsd.rd dkaX" (use "show device" to find your --- 126,150 ---- the "kc.fs" floppy. This time, when the floppy is ejected simply re-insert "kc.fs" again and answer a different set of questions.
!
Write the simpleroot23.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.
!
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.3/amiga/utils/loadbsd CD0:2.3/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.3/alpha/bsd.rd dkaX" (use "show device" to find your *************** *** 152,158 **** 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 --- 152,158 ---- 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 *************** *** 162,204 **** partitions. Finally, you will be ready to configure the BSD/Mac68k Booter with the location of your kernel and boot the system.
!
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! -
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 !
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 !
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. 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. --- 162,203 ---- partitions. Finally, you will be ready to configure the BSD/Mac68k Booter with the location of your kernel and boot the system.
!
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!
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 !
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 !
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 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. *************** *** 207,223 ****
A ports tree archive is also provided. To extract:
!
! # 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 --- 206,222 ----
A ports tree archive is also provided. To extract:
!
! # 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 *************** *** 241,249 **** 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 !
[Of course, you must replace the local directory and server name here with the location of your ports collection and a nearby anoncvs --- 240,248 ---- 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 !
[Of course, you must replace the local directory and server name here with the location of your ports collection and a nearby anoncvs *************** *** 255,260 ****
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.
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.