[src/netbsd-1-4]: src/distrib/notes/vax Apply patch (requested by toddpw):

[he <he%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/79e4ba7cfc94
branches:  netbsd-1-4
changeset: 470433:79e4ba7cfc94
user:      he <he%NetBSD.org@localhost>
date:      Mon Feb 28 19:45:32 2000 +0000

description:
Apply patch (requested by toddpw):
  Update the VAX install notes to closer reflect reality.

diffstat:

 distrib/notes/vax/hardware |  17 ++++----
 distrib/notes/vax/install  |   4 +-
 distrib/notes/vax/prep     |  18 +++-----
 distrib/notes/vax/xfer     |  85 +++++++++++++++++++++++++++++----------------
 4 files changed, 72 insertions(+), 52 deletions(-)

diffs (234 lines):

diff -r 74dd020024fb -r 79e4ba7cfc94 distrib/notes/vax/hardware
--- a/distrib/notes/vax/hardware        Mon Feb 28 19:09:02 2000 +0000
+++ b/distrib/notes/vax/hardware        Mon Feb 28 19:45:32 2000 +0000
@@ -1,13 +1,14 @@
-.\" $NetBSD: hardware,v 1.3.2.1 1999/05/07 15:06:13 perry Exp $        
+.\" $NetBSD: hardware,v 1.3.2.2 2000/02/28 19:45:32 he Exp $   
 .
 Hardware supported by NetBSD/vax \*V includes (but may not be limited to): 
 .Bl -tag -width indent -offset indent
 .It Em CPU types:
 VAX 11/750, VAX 11/78{0,5}, VAX 8200/8250/8300/8350,
-VAX 8600/8650, MicroVAX II, MicroVAX III, 
-MicroVAX 3600/3800/3900, MicroVAX 3300/3400/3500,
+VAX 8600/8650, MicroVAX II/VAXstation II, MicroVAX III, 
+MicroVAX 3300/3400, MicroVAX 3500/3600, MicroVAX 3800/3900,
 MicroVAX 2000/VAXstation 2000, VAXstation 3100 model 30,38,40,48,76,
-MicroVAX 3100 (partly) and VAXstation 4000/60.
+VAXstation 3200/3500
+and VAXstation 4000/60.
 .It Em Networking:
 DEUNA/DELUA Unibus ethernet, DEQNA/DELQA Q22 bus ethernet,
 and LANCE chip where available.
@@ -29,15 +30,15 @@
 .El
 .Pp
 The minimal configuration requires 2M of RAM and ~40MB of disk space,
-but the installation requires at least 4MB RAM and you probably do
-not want to run with anything less than that.
+but the installation really requires 6MB RAM unless you plan on
+using Jedi powers.
 .Pp
 Here is a table of recommended HD partition sizes for a full install:
 .Pp
 .Bl -column -offset indent Partition Advised Needed
 .It Partition Ta Advised Ta Needed
-.It root\ (/)    Ta 20M          Ta 10M
-.It user\ (/usr) Ta 80M          Ta 45M
+.It root\ (/)    Ta 32M          Ta 16M
+.It user\ (/usr) Ta 110M         Ta 45M
 .It swap         Ta 2\ or\ 3\ *\ RAM
 .El
 Anything else is up to you!
diff -r 74dd020024fb -r 79e4ba7cfc94 distrib/notes/vax/install
--- a/distrib/notes/vax/install Mon Feb 28 19:09:02 2000 +0000
+++ b/distrib/notes/vax/install Mon Feb 28 19:45:32 2000 +0000
@@ -1,4 +1,4 @@
-.\"    $NetBSD: install,v 1.4.2.1 1999/05/07 15:05:10 perry Exp $      
+.\"    $NetBSD: install,v 1.4.2.2 2000/02/28 19:45:32 he Exp $ 
 .\"
 .\" Copyright (c) 1999 The NetBSD Foundation, Inc.
 .\" All rights reserved.
@@ -76,6 +76,6 @@
 Then just proceed with the program sysinst. The install descriptions
 for sysinst that follows can be easily adopted to vax.
 
-.\" Sad that the sysinst install instructions is so i386-specific.
+.\" Sad that the sysinst install instructions are so i386-specific.
 .so ../common/sysinst
 
diff -r 74dd020024fb -r 79e4ba7cfc94 distrib/notes/vax/prep
--- a/distrib/notes/vax/prep    Mon Feb 28 19:09:02 2000 +0000
+++ b/distrib/notes/vax/prep    Mon Feb 28 19:45:32 2000 +0000
@@ -1,17 +1,13 @@
-.\" $NetBSD: prep,v 1.3.2.1 1999/05/07 15:06:14 perry Exp $    
+.\" $NetBSD: prep,v 1.3.2.2 2000/02/28 19:45:32 he Exp $       
 .
 VAX machines usually need little or no preparation before installing
 NetBSD, other than the usual, well advised precaution of BACKING UP
 ALL DATA on any attached storage devices.
 .Pp
-You will need to know the CSR address of your disk controller(s) if
-they are on a Qbus/Unibus. The disk controllers must then be at
-either 772150 (DUA) or 760334 (DUB). These two addresses are the
-only recognized by the kernel and boot programs.
+If you are on a Qbus or Unibus system the disk controller(s) need
+be at the standard CSR addresses for DUA (772150) or DUB (760334)
+to be recognized by the kernel and boot programs.
 .Pp
-Also; if you are installing on a VAXstation, note that the only supported
-built-in console is the monochrome graphics on some VS3100's. If you
-have another graphic card or machine you
-.Em must
-have a serial console.
-
+If you are installing on a VAXstation you
+.Em may
+require a serial console.
diff -r 74dd020024fb -r 79e4ba7cfc94 distrib/notes/vax/xfer
--- a/distrib/notes/vax/xfer    Mon Feb 28 19:09:02 2000 +0000
+++ b/distrib/notes/vax/xfer    Mon Feb 28 19:45:32 2000 +0000
@@ -1,20 +1,21 @@
-.\" $NetBSD: xfer,v 1.3.2.1 1999/05/07 15:06:14 perry Exp $    
+.\" $NetBSD: xfer,v 1.3.2.2 2000/02/28 19:45:32 he Exp $       
 .
 Installation is supported from several media types, including:
 .Bl -bullet -compact -offset indent
 .It
+Floppy
+.It
+FTP
+.It
 Tape
 .It
 NFS
-.It
-Floppy
-.It
-FTP
 .El
 .(Note
 Installing on a "bare" machine requires some bootable
 device; either a tape or floppy drive or a NFS server together
-with a machine that can act as a MOP loader.
+with a machine that can act as a MOP loader, such as another
+machine running NetBSD.
 NetBSD/vax can use both BOOTP/DHCP and
 BOOTPARAMS for netboot installations.
 .Note)
@@ -22,28 +23,46 @@
 The procedure for transferring the distribution sets onto
 installation media depends on the type of media. most of it is up to
 you, depending what you want to install, but preferred are to do
-the installation over network as soon as the miniroot is installed.
+the installation over network as soon as the install kernel is booted.
 .
 .Ss2 Creating boot tapes
 .
-Fetch the bootable miniroot image from
-.Dl \&.../NetBSD-\*V/vax/miniroot/miniroot.gz Ns Ar {50,33}
-Gunzip the miniroot and write it on the beginning of the tape.
-Under Ultrix this is done like this:
-.D1 Ic "gunzip miniroot.gz
+Fetch the bootable bootfs image from
+.Dl \&.../NetBSD-\*V/vax/installation/bootfs/boot.fs.gz
+Gunzip boot.fs.gz and write it on the beginning of the tape.
+Under NetBSD this is done via:
+.D1 Ic "gunzip boot.fs.gz
+.D1 Ic "mt -f /dev/nrmt0 rewind
+.D1 Ic "dd if=boot.fs of=/dev/nrmt0
+.D1 Ic "mt -f /dev/nrmt0 rewoffl
+.Pp
+Under Ultrix the tape name is different:
+.D1 Ic "gunzip boot.fs.gz
 .D1 Ic "mt -f /dev/rmt0h rewind
-.D1 Ic "dd if=miniroot of=/dev/rmt0h
+.D1 Ic "dd if=boot.fs of=/dev/rmt0h
 .D1 Ic "mt -f /dev/rmt0h rewoffl
 .Pp
-Under NetBSD this is done the same way, except for the tape name:
-.D1 Ic "gunzip miniroot.gz
-.D1 Ic "mt -f /dev/rmt8 rewind
-.D1 Ic "dd if=miniroot of=/dev/rmt8
-.D1 Ic "mt -f /dev/rmt8 rewoffl
-.Pp
 Of course, if you have a tape unit other than unit 0 you have to use
 the corresponding unit number.
 .Pp
+If you wish to install the sets from tape then stage you will need to
+download the *.tgz files from 
+.Dl \&.../NetBSD-\*V/vax/binary/sets Ns Ar {50,33}
+(if your disk is less than 200MB you will probably want to exclude the
+X sets) and then before the 'mt ... rewoffl' run
+.D1 Ic "tar cvf /dev/nrmt0 *.tgz
+When you have booted the bootfs and completed the disk partitioning
+you will be prompted to 'select medium' for install. At this point
+you will need to press ^Z (Ctrl+Z) to suspend the install tool, then
+.D1 Ic "cd /mnt
+.D1 Ic "mt -f /dev/nrmt0 rewind
+.D1 Ic "mt -f /dev/nrmt0 fsf
+.D1 Ic "tar xvf /dev/nrmt0
+.D1 Ic "fg
+then select "install from local dir" and give "/mnt".
+Note: If your disk is small you will need to be careful about filling
+it up.
+.Pp
 If you are using any other OS to create bootable tapes, remember that
 the blocksize
 .Em must
@@ -51,17 +70,17 @@
 .
 .Ss2 Creating boot floppies
 .
-Fetch the bootable miniroot image from
-.Dl \&.../NetBSD-\*V/vax/miniroot/miniroot.gz Ns Ar {50,33}
-and gunzip it. It is a 1.2MB bootable image that will boot from any
-floppy of size 1.2MB and bigger.
+Fetch the bootable bootfs image from
+.Dl \&.../NetBSD-\*V/vax/installation/bootfs/boot.fs.gz
+and gunzip it. It is a 1MB bootable image that will boot from any
+floppy of size 1MB and bigger.
 Note that you
 .Em cannot
 install from RX50 floppies due to the small size. This may change
 in the future.
 .Pp
-All floppies except RX50 uses a standardized format for storing data
-so writing the miniroot to the floppy can be done on any PC. From DOS
+All floppies except RX50 use a standardized format for storing data
+so writing the bootfs to the floppy can be done on any PC. From DOS
 the preferred way to do this is using RAWRITE.EXE.
 .
 .Ss2 Booting from NFS server
@@ -96,21 +115,25 @@
 this. If the server runs another operating system, consult the
 documentation that came with it. (I.e. add_client(8) on SunOS.)
 .Pp
+There is also very useful documentation at
+.Lk http://www.netbsd.org/Documentation/network/netboot/
+.Pp
 You also must install a MOP loader. If you are booting from another
-NetBSD machine, MOP are included in the distribution, otherwise you
-may have to install a MOP loader. A loader can be found at
+NetBSD machine, the MOP daemons are included in the distribution,
+otherwise you may have to install a MOP loader. A loader can be found at
 .Lk ftp.stacken.kth.se:/pub/OS/NetBSD/mopd
 Fetch the latest and read the
 installation instructions.
 .Pp
 The file that should be loaded is called boot.mop and is located in
-.Dl \&.../NetBSD-\*V/vax/installation/netboot/boot.mop Ns Ar {50,33}
+.Dl \&.../NetBSD-\*V/vax/installation/netboot/boot.mop
 .Pp
-The kernel to load is the same kernel as the miniroot uses and can 
+The kernel to load is the same kernel as the bootfs uses and can 
 be found in
-.Dl \&.../NetBSD-\*V/vax/installation/netboot/netbsd.gz Ns Ar {50,33}
+.Dl \&.../NetBSD-\*V/vax/installation/netboot/netbsd.ram.gz
 From the install program started in the kernel the rest of the system
 can be installed.
-There is also a very good FAQ for netbooting VAXen at
+There is also a very good (if somewhat out of date) FAQ for netbooting
+VAXen at
 .Lk http://world.std.com/~bdc/projects/vaxen/VAX-netboot-HOWTO.html
 that describes netbooting of VAXen from many different OS'es.