OpenBSD/aviion notes draft.

8 files changed, 192 insertions, 3 deletions

diff --git a/distrib/notes/Makefile b/distrib/notes/Makefile
index ae20d5695b5..5956689a729 100644
--- a/distrib/notes/Makefile
+++ b/distrib/notes/Makefile
@@ -1,4 +1,4 @@
-#	$OpenBSD: Makefile,v 1.28 2007/02/28 22:30:02 miod Exp $
+#	$OpenBSD: Makefile,v 1.29 2007/03/15 20:18:19 miod Exp $
 
 NOPROG=
 NOMAN=
@@ -18,8 +18,9 @@ all:	$(TARG)
 
 allarchs:
 	@cd $(.CURDIR); \
-	for arch in alpha amd64 armish cats hp300 hppa i386 landisk luna88k \
-	    mac68k macppc mvme68k mvme88k sgi sparc sparc64 vax zaurus; \
+	for arch in alpha amd64 armish aviion cats hp300 hppa i386 landisk \
+	    luna88k mac68k macppc mvme68k mvme88k sgi sparc sparc64 vax \
+	    zaurus; \
 	do ${MAKE} M=$$arch; done
 
 $(TARG): $(DEP)
diff --git a/distrib/notes/aviion/contents b/distrib/notes/aviion/contents
new file mode 100644
index 00000000000..19fb8e07823
--- /dev/null
+++ b/distrib/notes/aviion/contents
@@ -0,0 +1,41 @@
+dnl	$OpenBSD: contents,v 1.1 2007/03/15 20:18:23 miod Exp $
+TopPart
+
+OpenBSDdistsets
+
+dnl not with the default text yes
+dnl OpenBSDbsd
+	bsd		A stock GENERIC MACHINE kernel.
+
+dnl not yet
+dnl OpenBSDrd
+dnl
+dnl	installboot	The OpenBSD/MACHINE boot loader installation
+dnl			program.
+dnl	bootxx		The OpenBSD/MACHINE boot block.
+dnl	bootsd		The OpenBSD/MACHINE disk boot loader.
+dnl	bootst		The OpenBSD/MACHINE tape boot loader.
+	netboot		The OpenBSD/MACHINE Sun-compatible network boot
+			loader.
+dnl	stboot		A VID tape block.
+dnl	tftpboot	The OpenBSD/MACHINE tftp-compatible network boot
+dnl			loader.
+
+dnl These files can be used to make a bootable tape suitable for installation.
+dnl They can also be used to configure an NFS server to support installation
+dnl over the network. See the section "Getting the OpenBSD system onto Useful
+dnl Media" for more information.
+
+DistributionDescription(six)
+
+OpenBSDbase(82256499,203198142)
+
+OpenBSDcomp(39873329,141571234)
+
+OpenBSDetc(1152254,3995885)
+
+OpenBSDgame(7097975,15193395)
+
+OpenBSDman(6838594,24373480)
+
+OpenBSDmisc(2276390,7482328)
diff --git a/distrib/notes/aviion/hardware b/distrib/notes/aviion/hardware
new file mode 100644
index 00000000000..75c83777ccb
--- /dev/null
+++ b/distrib/notes/aviion/hardware
@@ -0,0 +1,23 @@
+dnl	$OpenBSD: hardware,v 1.1 2007/03/15 20:18:23 miod Exp $
+OpenBSD/MACHINE OSREV runs on the following Data General AViiON systems:
+
+	- AV100/200/300/400, AV3000/4000 and AV4300 series
+dnl	- AV4600 and AV530 series
+dnl	- AV5000 and AV6000 series
+dnl	- AV6280 and AV8000-8 series
+
+The minimal configuration requires 16MB of RAM.
+dnl The minimal configuration requires 16MB of RAM and ~250MB of disk space.
+dnl To install the entire system requires much more disk space, and to
+dnl compile the system, more RAM is recommended.
+
+Supported devices:
+
+On-board devices:
+	- serial ports (dart)
+	- 2KB NVRAM (/dev/nvram0)
+	- Ethernet interface (le)
+
+Additional VMEbus devices:
+
+	Interphase Hawk 3207 Ethernet interface (le)
diff --git a/distrib/notes/aviion/install b/distrib/notes/aviion/install
new file mode 100644
index 00000000000..a0bff8c9991
--- /dev/null
+++ b/distrib/notes/aviion/install
@@ -0,0 +1,101 @@
+dnl	$OpenBSD: install,v 1.1 2007/03/15 20:18:23 miod Exp $
+OpenBSDInstallPrelude
+
+There is currently no support for disk controllers in OpenBSD/MACHINE.
+Because of this, the only way to use OpenBSD/MACHINE is to run as a
+diskless system, with the whole system installed on an NFS filesystem.
+
+Booting from Network:
+
+OpenBSD/MACHINE can boot off any network interface supported by the machine
+PROM (SCM), even if the device itself is not supported by OpenBSD.
+The OpenSBD network boot loader, netboot, expects a Sun-compatible diskless
+setup (bootparams and NFS root). Thus it will be necessary to set up a
+complete diskless client configuration 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).
+
+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 in hexadecimal. For example, a machine which has
+been assigned IP address 130.115.144.11, will make a TFTP request for
+`8273900B'.
+
+Normally, this file is a symbolic link to the OpenBSD network boot loader,
+which should be located in a place where the TFTP daemon can find it
+(remember, many TFTP daemons run in a chroot'ed environment).
+
+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 the 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.
+
+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.
+
+A few configuration files need to be edited:
+
+	<root>/etc/hosts
+		Add the IP addresses of both server and client.
+
+	<root>/etc/myname
+		This files contains the client's hostname; use the same
+		name as in <root>/etc/hosts.
+
+	<root>/etc/mygate
+		This files contains the client's default gateway. It should
+		be either an IP address or a name found in the `hosts' file.
+
+	<root>/etc/fstab
+		Enter the entries for the remotely mounted filesystems.
+		For example:
+			server:/export/root/client       /     nfs  rw 0 0
+			server:/export/exec/MACHINE.OpenBSD /usr  nfs  rw 0 0
+
+OpenBSDInstNFS
+
+You can now boot the machine from the network by specifying the Ethernet
+interface as the boot device, as in
+
+    SCM> b inen()
+
+to boot from the onboard interface, or
+
+    SCM> b hken()
+
+to boot from the Hawk Ethernet card.
+
diff --git a/distrib/notes/aviion/prep b/distrib/notes/aviion/prep
new file mode 100644
index 00000000000..b57945f11ad
--- /dev/null
+++ b/distrib/notes/aviion/prep
@@ -0,0 +1,6 @@
+dnl	$OpenBSD: prep,v 1.1 2007/03/15 20:18:23 miod Exp $
+Data General AViiON systems do not require any specific preparation
+steps to be able to run OpenBSD.
+
+dnl XXX write an SCM primer
+You might want to become familiar with the PROM boot commands, though.
diff --git a/distrib/notes/aviion/upgrade b/distrib/notes/aviion/upgrade
new file mode 100644
index 00000000000..0454a317a48
--- /dev/null
+++ b/distrib/notes/aviion/upgrade
@@ -0,0 +1,9 @@
+dnl	$OpenBSD: upgrade,v 1.1 2007/03/15 20:18:23 miod Exp $
+dnl OpenBSDUpgrade({:-an installation tape, or the miniroot over the network-:})
+To upgrade your OpenBSD installation, simply extract the new sets on
+the diskless server.
+
+It is strongly advised that you unpack the etc{:--:}OSrev.tgz set in
+a temporary directory and merge changes by hand, since all components of
+your system may not function correctly until your files in `/etc' are
+updated.
diff --git a/distrib/notes/aviion/whatis b/distrib/notes/aviion/whatis
new file mode 100644
index 00000000000..6f55434b889
--- /dev/null
+++ b/distrib/notes/aviion/whatis
@@ -0,0 +1,5 @@
+dnl	$OpenBSD: whatis,v 1.1 2007/03/15 20:18:23 miod Exp $
+
+OpenBSD/MACHINE runs on a few Motorola 88100 processor-based Data General
+AViiON workstations. Although hardware support is currently very limited,
+work is in progress to cover more models and devices.
diff --git a/distrib/notes/aviion/xfer b/distrib/notes/aviion/xfer
new file mode 100644
index 00000000000..f74b5b23f10
--- /dev/null
+++ b/distrib/notes/aviion/xfer
@@ -0,0 +1,3 @@
+dnl	$OpenBSD: xfer,v 1.1 2007/03/15 20:18:23 miod Exp $
+As long as OpenBSD/MACHINE only runs diskless, there is no real installation
+media to prepare.