A long-needed notes update for mvme88k...

7 files changed, 229 insertions, 337 deletions

diff --git a/distrib/notes/mvme88k/contents b/distrib/notes/mvme88k/contents
index f33b771161d..5e1353fe050 100644
--- a/distrib/notes/mvme88k/contents
+++ b/distrib/notes/mvme88k/contents
@@ -1,3 +1,4 @@
+dnl	$OpenBSD: contents,v 1.5 2003/08/10 21:04:06 miod Exp $
 TopPart
 
 OpenBSDdistsets
@@ -6,23 +7,36 @@ OpenBSDbsd
 
 OpenBSDrd
 
-DistributionDescription(nine)
+		installboot	The OpenBSD/MACHINE boot loader
+				installation program.
+		bootxx		The OpenBSD/MACHINE boot block.
+		bootsd		The OpenBSD/MACHINE disk boot loader.
+		bootst		The OpenBSD/MACHINE tape boot loader.
+		netboot		The OpenBSD/MACHINE network boot loader.
+		stboot		A VID tape block.
 
-OpenBSDbase(41.4M,125.8M)
+These files can be used to make a bootable tape suitable for installation.
+They can also be used to configure an NFS server to support installation
+over the network. See the section "Getting the OpenBSD system onto Useful
+Media" for more information.
 
-OpenBSDcomp(9.5M,34.9M)
+DistributionDescription(six)
 
-OpenBSDetc(140.9K,660.0K)
+OpenBSDbase(69.0M,174.9M)
 
-OpenBSDgame(6.5M,17.9M)
+OpenBSDcomp(12.7M,39.3M)
 
-OpenBSDman(3.4M,13.0M)
+OpenBSDetc(1.5M,5.5M)
 
-OpenBSDmisc(1.6M,5.4M)
+OpenBSDgame(6.7M,14.8M)
 
-OpenBSDxbase
-
-OpenBSDxshare
-
-OpenBSDxfont
+OpenBSDman(6.0M,21.3M)
 
+OpenBSDmisc(1.9M,6.4M)
+dnl Not there yet...
+dnl
+dnl OpenBSDxbase
+dnl
+dnl OpenBSDxshare
+dnl
+dnl OpenBSDxfont
diff --git a/distrib/notes/mvme88k/hardware b/distrib/notes/mvme88k/hardware
index 968c18c55e9..e7b56323fc4 100644
--- a/distrib/notes/mvme88k/hardware
+++ b/distrib/notes/mvme88k/hardware
@@ -1,28 +1,30 @@
+dnl	$OpenBSD: hardware,v 1.3 2003/08/10 21:04:06 miod Exp $
 OpenBSD/MACHINE OSREV runs on the following classes of machines:
-	- MVME187 - Motorola with 88100
+	- MVME187 - Single board computer with 88100 processor
+	- Motorola 8120 - non expandable MVME187
 
-The minimal configuration requires 4M of RAM and ~80M of disk space.
+The minimal configuration requires 8M of RAM and ~250M of disk space.
 To install the entire system requires much more disk space, and to
-compile the system, more RAM is recommended.  (OpenBSD with 4M of
-RAM feels like Solaris with 4M of RAM.) Note that until you have
-around 16M of RAM, getting more RAM is more important than getting a
-faster CPU.)
+compile the system, more RAM is recommended.
 
 Supported devices {:-include-:}:
 
-MVME187
-	serial:
+MVME187, Motorola 8120:
+	serial ports:
 		on-board tty00 - tty03 - Cirrus Logic CD2401
 	ethernet:
 		on-board Intel 82596CA ethernet ("ie0")
 	SCSI:
 		on-board SCSI controller NCR53c710
+	SRAM:
+		supported
+	VMEbus:
+		supported (on MVME187 only, the 8120 does not have VME)
 
-	Parallel:
-		Not supported
+Additional VMEbus devices supported by the OpenBSD/MACHINE port {:-include-:}:
 
-	VME:
-		drivers for short I/O access
+	MVME328 SCSI controller (vs)
 
-	SRAM:
-		supported
+	MVME332 Serial controller (vx)
+
+	MVME376 Ethernet controller (ve)
diff --git a/distrib/notes/mvme88k/install b/distrib/notes/mvme88k/install
index 8799e6a75bc..017298ab8b5 100644
--- a/distrib/notes/mvme88k/install
+++ b/distrib/notes/mvme88k/install
@@ -1,80 +1,170 @@
-dnl	$OpenBSD: install,v 1.8 2003/01/04 00:18:08 miod Exp $
-Installing OpenBSD is a relatively complex process, but if you have
-this document in hand it shouldn't be too much trouble.
-
-There are several ways to install OpenBSD onto a disk. The easiest way
-in terms of preliminary setup is to use the OpenBSD ramdisk kernel that can
-be booted from tape. Alternatively, if your mvme88k is hooked up in a
-network you can find a server and arrange for a diskless setup which is a
-convenient way to install on a machine whose disk does not currently hold
-a usable operating system (see the section `Installing using a diskless
-setup' below).
-
-
-Installing using the OpenBSD ramdisk kernel.
-
-The ramdisk kernel is a kernel that containes an OpenBSD filesystem holding
-all utilities necessary to install OpenBSD on a local disk. It is distributed
-as a binary file with the name bsd.rd.
-
-After the initial probe messages you'll asked to start the install
-or upgrade procedure. Proceed to the section `Running the installation
-scripts' below.
-
-
-Installing using a diskless setup.
-
-First, you must setup a diskless client configuration on a server. If
-you are using a OpenBSD system as the boot-server, have a look at the
-diskless(8) manual page for guidelines on how to proceed with this.
-If the server runs another operating system, you'll have to consult
-documentation that came with it (on SunOS systems, add_client(8) is a
-good start).
-
-Second, you must configure the netboot parameters in the mvme88k Bug
-using the NIOT command.  The Load Address should be 0xAF0000.  The
-Execution Address should be 0xAF0008.
-
-Your mvme88k expects to be able to download a second stage bootstrap
-program via TFTP after having acquired its IP address through RevARP when
-instructed to boot "over the net". It will look for a filename composed of
-the machine's IP address followed by the machine's architecture, separated
-by a period. For example, a sun4c machine which has been assigned IP
-address 130.115.144.11, will make an TFTP request for a file that has
-been named in the nvram.  Normally, this file is a second-stage
-boot program, which should be located in a place where the TFTP daemon
-can find it (remember, many TFTP daemons run in a chroot'ed environment).
-You can find the boot program in `/usr/mdec/netboot' in the OpenBSD/mvme88k
+dnl	$OpenBSD: install,v 1.9 2003/08/10 21:04:06 miod Exp $
+OpenBSDInstallPrelude
+
+There are several ways to install OpenBSD onto a disk. The easiest way in
+terms of preliminary setup is to use the OpenBSD ramdisk kernel that can be
+booted from tape.
+
+Alternatively, if your MACHINE is hooked up in a network, it is possible to
+setup another machine as a server for diskless setup, which is a convenient
+way to install on a machine whose disk does not currently hold a usable
+operating system.
+This is difficult to get set up correctly the first time, but easy to use
+afterwards (see the section `Installing using a diskless setup' below).
+
+
+Booting from the Installation Media:
+
+Prior to attempting an installation, everything of value on the target
+system should be backed up.  While installing OpenBSD does not necessarily
+wipe out all the partitions on the hard disk, errors during the install
+process can have unforeseen consequences and will probably leave the system
+unbootable if the installation process is not completed. Availability of the
+installation media for the prior installation, such as a Motorola
+SystemV/MACHINE tape is always a good insurance, should it be necessary to
+"go back" for some reason.
+
+After taking care of all that, the system should be brought down gracefully
+using the shutdown(8) and/or halt(8) commands, which will eventually go bakc
+to the ``BUG>'' prompt (it may be necessary to send a break if the system is
+completely halted).
+
+
+Booting from SCSI tape:
+
+dnl XXX 188 does not have built-in devices - will need quite a whack once
+dnl 188 support is back.
+Bootable tapes can be booted with the following command at the prompt:
+
+	187-Bug> bo xx yy
+
+Where `xx' is the SCSI controller number (00 for the built-in SCSI
+controller), and `yy' is ten times the tape drive ID.
+
+For example, booting from a tape drive using SCSI id 4 on the built-in
+controller:
+	187-Bug> bo 00 40
+
+
+Installing using a diskless setup:
+
+First, a diskless client configuration should be setup on a server. If the
+boot server is an OpenBSD system, the diskless(8) manual page will provide
+detailed information on the process.
+
+If the server runs another operating system, the setup instructions will
+likely be available as part of the documentation that came with it (on SunOS
+systems, add_client(8) and the Sun System/Networks administrators guide
+constitute a good start; on Solaris systems, share(1M) is a good starting
+point as well).
+
+Second, the MACHINE workstation should then be setup using the NIOT command
+at the BUG prompt. The ``Load Address'' value should be 0xAF0000, and the
+``Execution Address'' value should be 0xAF0000 as well.
+
+Then, it should be possible to boot the machine from the server by entering
+the NBO command at the BUG prompt:
+	
+	187-Bug> nbo 00 00 bsd.rd
+
+
+
+Installing using the tape or netboot procedure:
+
+OpenBSDInstallPart2
+
+	Boot your machine from the installation media as described above.
+
+	It will take a while to load the kernel especially from a slow
+	network connection, most likely more than a minute.  If some action
+	doesn't eventually happen, or the spinning cursor has stopped and
+	nothing further has happened, either your boot media is bad, your
+	diskless setup isn't correct, or you may have a hardware or
+	configuration problem.
+
+OpenBSDBootMsgs
+
+	You will next be asked for your terminal type.  You should choose
+	the terminal type from amongst those listed.
+	(If your terminal type is xterm, just use vt100).
+
+OpenBSDInstallPart3
+
+OpenBSDInstallPart4
+
+OpenBSDInstallPart5(sd0)
+
+OpenBSDInstallNet({:-CD-ROM, NFS, -:})
+
+OpenBSDFTPInstall
+
+OpenBSDHTTPInstall
+
+OpenBSDTAPEInstall(4)
+
+OpenBSDCDROMInstall
+		
+OpenBSDNFSInstall
+
+OpenBSDDISKInstall(,{:-only -:})
+
+OpenBSDCommonFS(NFS)
+		
+OpenBSDCommonURL
+
+OpenBSDCongratulations
+
+
+
+Net Boot or Diskless Setup Information:
+
+The set up is similar to SunOS diskless setup, but not identical, because
+the Sun setup assumes that the bootblocks load a kernel image, which then
+uses NFS to access the exported root partition, while the OpenBSD bootblocks
+use internal NFS routines to load the kernel image directly from the
+exported root partition.
+
+Please understand that no one gets this right the first try, since there is
+a lot of setup and all the host daemons must be running and configured
+correctly.  If you have problems, extract the diskless(8) manpage, find
+someone who's been through it before and use the host syslog and tcpdump(8)
+to get visibility of what's happening (or not).
+
+Your MACHINE expects to be able to download a second stage bootstrap program
+via TFTP after having acquired its IP address through RevARP when instructed
+to boot "over the net". It will look for a filename composed of the
+machine's IP address, followed by the machine's architecture, separated by a
+period. For example, a MACHINE board which has been assigned IP address
+130.115.144.11, will make an TFTP request for `8273900B.MACHINE'. Normally,
+this file is a symbolic link to an appropriate second-stage boot program,
+which should be located in a place where the TFTP daemon can find it
+(remember, many TFTP daemons run in a chroot'ed environment).
+
+You can find the boot program in `/usr/mdec/netboot' in the OpenBSD/MACHINE
 distribution.
 
-After the boot program has been loaded into memory and given control by
-the PROM, it starts locating the machine's remote root directory through
-the BOOTPARAM protocol. First a BOOTPARAM WHOAMI request is broadcast
-on the local net. The answer to this request (if it comes in) contains
-the client's name. This name is used in next step, a BOOTPARAM GETFILE
-request -- sent to the server that responded to the WHOAMI request --
-requesting the name and address of the machine that will serve the client's
-root directory, as well as the path of the client's root on that server.
+After the boot program has been loaded into memory and given control by the
+BUG, it starts locating the machine's remote root directory through the
+BOOTPARAM protocol. First a BOOTPARAM WHOAMI request is broadcast on the
+local net. The answer to this request (if it comes in) contains the client's
+name. This name is used in next step, a BOOTPARAM GETFILE request -- sent to
+the server that responded to the WHOAMI request -- requesting the name and
+address of the machine that will serve the client's root directory, as well
+as the path of the client's root on that server.
 
 Finally, this information (if it comes in) is used to issue a REMOTE MOUNT
 request to the client's root filesystem server, asking for an NFS file
-handle corresponding to the root filesystem. If successful, the boot
-program starts reading from the remote root filesystem in search of the
-kernel which is then read into memory.
-
+handle corresponding to the root filesystem. If successful, the boot program
+starts reading from the remote root filesystem in search of the kernel which
+is then read into memory.
 
-As noted above in the section `Preparing your System for OpenBSD Installation',
-you have several options when choosing a location to store the installation
-filesets. However, the easiest way is to put the *.tgz files you want
-to install into the root directory for your client on the server.
-
-Next, unpack `base{:--:}OSrev.tgz' and `etc{:--:}OSrev.tgz' on the server in the root
-directory for your machine. If you elect to use a separately NFS-mounted
+Unpack `base{:--:}OSrev.tgz' and `etc{:--:}OSrev.tgz' on the server in the root directory
+for your target machine. If you elect to use a separately NFS-mounted
 filesystem for `/usr' with your diskless setup, make sure the "./usr" base
 files in base{:--:}OSrev.tgz end up in the correct location. One way to do this is
 to temporarily use a loopback mount on the server, re-routing <root>/usr to
-your server's exported OpenBSD "/usr" directory. Also put the kernel and the
-install/upgrade scripts into the root directory.
+your server's exported OpenBSD "/usr" directory. Also put the kernel and
+the install/upgrade scripts into the root directory.
 
 A few configuration files need to be edited:
 
@@ -89,7 +179,7 @@ A few configuration files need to be edited:
 		Enter the entries for the remotely mounted filesystems.
 		For example:
 			server:/export/root/client       /     nfs  rw 0 0
-			server:/export/exec/sun4.OpenBSD /usr  nfs  rw 0 0
+			server:/export/exec/MACHINE.OpenBSD /usr  nfs  rw 0 0
 
 Now you must populate the `/dev' directory for your client. If the server
 runs SunOS 4.x, you can simply change your working directory to `<root>/dev'
@@ -101,132 +191,3 @@ messages about unknown user and groups. These errors are inconsequential
 for the purpose of installing OpenBSD. However, you may want to correct them
 if you plan to the diskless setup regularly. In that case, you may re-run
 MAKEDEV on your OpenBSD machine once it has booted.
-
-Boot your workstation from the server by entering the appropriate `boot'
-command at the monitor prompt. Depending on the PROM version in your machine,
-this command takes one of the following forms:
-
-	187-bug> nbo 00 00 bsd -s
-
-This will boot the OpenBSD kernel in single-user mode.
-
-If you use a diskless setup with a separately NFS-mounted /usr filesystem,
-mount /usr by hand now:
-
-OpenBSD# mount /usr
-
-At this point, it's worth checking the disk label and partition sizes on
-the disk you want to install OpenBSD onto. OpenBSD understands SunOS-style
-disklabels, so if your disk was previously used by SunOS there will be
-a usable label on it. Use `disklabel -e <disk>' (where <disk> is the
-device name assigned by the OpenBSD kernel, e.g. `sd0') to view and
-modify the partition sizes. See the section `Preparing your System for
-OpenBSD Installation' above for suggestions about disk partition sizes.
-Make sure all your partitions start and end on cylinder boundaries.
-
-NOTE: if you are installing on a SCSI disk that does *not* have a SunOS
-or OpenBSD label on it, you may still be able to use disklabel(8) but you'll
-have to create all partitions from scratch. If your disk is listed in
-`/etc/disktab', you may use the entry (which in most cases only defines
-a `c' partition to describe the whole disk) to put an initial label on
-the disk.  DO NOT USE `disklabel -r ...' TO INITIALIZE YOUR DISK LABEL;
-THIS WILL LEAD TO UNPREDICTABLE RESULTS. This deficiency will be fixed
-in a next release.
-
-Here follows an example of what you'll see while in the disklabel editor.
-Do not touch any of the parameters except for the `label: ' entry and
-the actual partition size information at the bottom (the lines starting
-with `a:', `b:', ...).
-
-The size and offset fields are given in sector units. Be sure to make
-these numbers multiples of the of the number of sectors per cylinder:
-the kernel might be picky about these things, but aside from this you'll
-have the least chance of wasting disk space.
-Partitions on which you intend to have a mountable filesystem, should
-be given fstype `4.2BSD'. Remember, the `c' partition should describe
-the whole disk.
-The `(Cyl. x - y)' info that appears after the hash (`#') character is
-treated as a comment and need not be filled in when altering partitions.
-
-Special note: the line containing `8 partitions:' is best left alone,
-even if you {:-define-:} less then eight partitions. If this line displays
-a different number and the program complains about it (after you leave
-the editor), then try setting it to `8 partitions:'.
-
-
-<BEGIN SAMPLE DISKLABEL SCREEN>
-OpenBSD# disklabel sd2
- # /dev/rsd2c:
-type: SCSI
-disk: SCSI disk
-label: Hold Your Breath
-flags:
-bytes/sector: 512
-sectors/track: 64
-tracks/cylinder: 7
-sectors/cylinder: 448
-cylinders: 1429
-rpm: 3600
-interleave: 1
-trackskew: 0
-cylinderskew: 0
-headswitch: 0           # milliseconds
-track-to-track seek: 0  # milliseconds
-drivedata: 0
-
-8 partitions:
-#        size   offset    fstype   [fsize bsize   cpg]
-  a:    50176        0    4.2BSD        0     0     0   # (Cyl.    0 - 111)
-  b:    64512    50176      swap                        # (Cyl.  112 - 255)
-  c:   640192        0   unknown                        # (Cyl.    0 - 1428)
-  d:   525504   114688    4.2BSD        0     0     0   # (Cyl.  256 - 1428)
-<END SAMPLE DISKLABEL SCREEN>
-
-
-If you are upgrading a OpenBSD installation, start the upgrade script:
-
-OpenBSD# sh upgrade.sh
-
-else, start the installation script:
-
-OpenBSD# sh install.sh
-
-
-These scripts will do most of the work of transferring the system from the
-tar files onto your disk. You will frequently be asked for confirmation
-before the script proceeds with each phase of the installation process.
-Occasionally, you'll have to provide a piece of information such as the
-name of the disk you want to install on or IP addresses and domain names
-you want to assign. If your system has more than one disk, you may want
-to look at the output of the dmesg(8) command to see how your disks
-have been identified by the kernel.
-
-The installation script goes through the following phases:
-
-	- determination of the disk to install OpenBSD on
-	- checking of the partition information on the disk
-	- creating and mounting the OpenBSD filesystems
-	- setup of IP configuration
-	- extraction of the distribution tar files
-	- installation of boot programs
-
-
-Now try a reboot.  (If needed, swap your scsi id's first).  Initially
-I'd suggest you "bo bsd -bs", then try multiuser after that.
-if you boot single-user the OpenBSD incantation to make the root
-filesystem writable is
-
-    OpenBSD# mount -u /dev/sd0a /
-
-Congratulations, you have successfully installed OpenBSD OSREV.  When you
-reboot into OpenBSD, you should log in as "root" at the login prompt.
-You should create yourself an account and protect it and the "root" account
-with good passwords.
-
-Some of the files in the OpenBSD OSREV distribution might need to be
-tailored for your site.  In particular, the /etc/mail/sendmail.cf file
-will almost definitely need to be adjusted, and other files in /etc will
-probably need to be modified.  If you are unfamiliar with UN*X-like
-system administration, it's recommended that you buy a book that
-discusses it.
-
diff --git a/distrib/notes/mvme88k/prep b/distrib/notes/mvme88k/prep
index 064bf6cd7ff..c91c2e7aff8 100644
--- a/distrib/notes/mvme88k/prep
+++ b/distrib/notes/mvme88k/prep
@@ -1,17 +1,18 @@
-;
-; This section should talk about setting up the NVRAM environment
-; on the various models.
-;
-MVME187:
+dnl	$OpenBSD: prep,v 1.2 2003/08/10 21:04:06 miod Exp $
+Before installing OpenBSD on your machine, you will want to check your
+machine's NVRAM settings.
 
-	Be sure to use the SET command to set the date before trying
-	to use the ethernet support in the 187-Bug.
+The defaults settings are usually suitable for OpenBSD; make sure the
+environment is configured in BUG mode. You can check and change this with
+the ENV command.
+
+Be sure to use the SET command to set the date before trying to use the
+ethernet support in the 187-Bug.
+
+If you plan to boot from the network, make sure your ENV settings match
+the following setup:
 
-187-Bug> env
-Local SCSI Bus Reset on Debugger Startup [Y/N] = N? y
 Network Auto Boot Enable [Y/N]   = N? y
 Network Auto Boot at power-up only [Y/N] = Y? n
 Network Auto Boot Abort Delay    = 5? 2
 Network Auto Boot Configuration Parameters Pointer (NVRAM) = 00000000? fffc0080
-Update Non-Volatile RAM (Y/N)? y
-Reset Local System (CPU) (Y/N)? y
diff --git a/distrib/notes/mvme88k/upgrade b/distrib/notes/mvme88k/upgrade
index 0842326c507..1c6898d2252 100644
--- a/distrib/notes/mvme88k/upgrade
+++ b/distrib/notes/mvme88k/upgrade
@@ -1,6 +1,2 @@
-To upgrade to OpenBSD OSREV from a previous version follow the instructions
-in the section "Installing OpenBSD", but run the script `upgrade.sh'
-in stead of `install.sh'.
-
-The upgrade script will use the existing disk partitions to install the
-new system in, and also preserves the files in `/etc'.
+dnl	$OpenBSD: upgrade,v 1.2 2003/08/10 21:04:06 miod Exp $
+OpenBSDUpgrade({:-an installation tape, or the miniroot over the network-:})
diff --git a/distrib/notes/mvme88k/whatis b/distrib/notes/mvme88k/whatis
index d849cbb6ba5..c8f4b8760f1 100644
--- a/distrib/notes/mvme88k/whatis
+++ b/distrib/notes/mvme88k/whatis
@@ -1,6 +1,3 @@
-OpenBSD/mvme88k 2.3 was written because the MVME187 existed in a computer
-company basement.  Nivas Madhur started the port.  Steve Murphree, Jr.
-finished the port in December 1998.  Code by Dale Rahn, Theo de Raadt,
-and Chuck Cranor was used as a starting point. Currently this port runs
-on MVME187 and perhaps other models also.
-
+dnl	$OpenBSD: whatis,v 1.3 2003/08/10 21:04:06 miod Exp $
+OpenBSD/MACHINE is an experimental port of OpenBSD to the Motorola 881x0
+processor-based VME boards.
diff --git a/distrib/notes/mvme88k/xfer b/distrib/notes/mvme88k/xfer
index 9e0a0ea5316..558597f73e0 100644
--- a/distrib/notes/mvme88k/xfer
+++ b/distrib/notes/mvme88k/xfer
@@ -1,97 +1,18 @@
-dnl	$OpenBSD: xfer,v 1.3 2003/01/04 00:18:08 miod Exp $
+dnl	$OpenBSD: xfer,v 1.4 2003/08/10 21:04:06 miod Exp $
 Installation is supported from several media types, including:
-	NFS partitions
-	FTP
-	Tape
-
-The steps necessary to prepare the distribution sets
-for installation depend on which method of installation
-you choose.  The various methods are explained below.
-
-To prepare for installing via an NFS partition:
-
-	Place the OpenBSD software you wish to install into
-	a directory on an NFS server, and make that directory
-	mountable by the machine which you will be installing
-	OpenBSD on.  This will probably require modifying the
-	/etc/exports file of the NFS server and resetting
-	mountd, acts which will require superuser privileges.
-	Note the numeric IP address of the NFS server and of
-	the router closest to the new OpenBSD machine,
-	if the NFS server is not on a network which is
-	directly attached to the OpenBSD machine.
-
-	If you are using a diskless setup to install OpenBSD on
-	your machine, you can take advantage of the fact that
-	the above has already been done on your machine's server.
-	So, you can conveniently put the OpenBSD filesets in your
-	machine's root filesystem on the server where the install
-	program can find them.
-
-	Once you have done this, you can proceed to the next
-	step in the installation process, preparing your
-	system for OpenBSD installation.
 
-To prepare for installing via FTP:
-
-	NOTE: this method of installation is recommended
-	      only for those already familiar with using
-	      the BSD network-manipulation commands and
-	      interfaces.  If you aren't, this documentation
-	      should help, but is not intended to be
-	      all-encompassing.
-
-	The preparations for this method of installation
-	are easy: all you have to do is make sure that
-	there's some FTP site from which you can retrieve
-	the OpenBSD installation when it's time to do
-	the install.  You should know the numeric IP
-	address of that site, the numeric IP address of
-	your nearest router if one is necessary
-
-	Once you have done this, you can proceed to the next
-	step in the installation process, preparing your
-	system for OpenBSD installation.
-
-To prepare for installing via a tape:
+	CD-ROM
+	FFS partitions
+	Tape
+	Remote NFS partitions
+	FTP
+	HTTP
 
-	To install OpenBSD from a tape, you need to somehow
-	make a boot tape on the appropriate kind of tape.
-	The files needed for this are:
-	
-	stboot 	  - The Motorola VID block
-	bootst 	  - The bootstrap program
-	bsd.rd.gz - The ramdisk installation kernel
-	
-	If you're making the tape on a UN*X system, the easiest
-	way to do so is:
-	
-	dd obs=512 if=stboot of=<no-rewind tape_device>
-	dd obs=512 if=bootst of=<no-rewind tape_device>
-	dd conv=sync obs=512 if=bsd.rd.gz of=<no-rewind tape_device>
-	
-	where "<no-rewind tape_device>" is the name of the tape device
-	that describes the tape drive you're using (possibly
-	something like /dev/nrst0, but we make no guarantees 8-).
-		
-	Now you need to get the OpenBSD filesets you wish to
-	install on your system on to the appropriate kind of tape,
-	in tar format.
+OpenBSDXferPrelude
 
-	If you're making the tape on a UN*X system, the easiest
-	way to do so is:
 
-		tar cvf <tape_device> <files>
+OpenBSDXferBootTape(,stboot obs=512,bootst obs=512,bsd.rd obs=8k conv=sync)
 
-	where "<tape_device>" is the name of the tape device
-	that describes the tape drive you're using (possibly
-	something like /dev/nrst0, but again, we make no guarantees 8-).
-	Under SunOS 5.x, this would be something like /dev/rmt/0mbn.
-	Again, your mileage may vary.  If you can't figure it out,
-	ask your system administrator.  "<files>" are the names
-	of the "set_name.nnn" files which you want to be placed
-	on the tape.
+OpenBSDXferNFS
 
-	Once you have done this, you can proceed to the next
-	step in the installation process, preparing your
-	system for OpenBSD installation.
+OpenBSDXferFFS