[src/trunk]: src/distrib/notes/vax Oops, forgot to check in the updated insta...

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

details:   https://anonhg.NetBSD.org/src/rev/0742a11a91e4
branches:  trunk
changeset: 472780:0742a11a91e4
user:      ragge <ragge%NetBSD.org@localhost>
date:      Fri May 07 00:15:16 1999 +0000

description:
Oops, forgot to check in the updated install instructions.

diffstat:

 distrib/notes/vax/hardware |   13 +-
 distrib/notes/vax/install  |  380 ++++----------------------------------------
 distrib/notes/vax/prep     |    9 +-
 distrib/notes/vax/upgrade  |    4 +-
 distrib/notes/vax/whatis   |    4 +-
 distrib/notes/vax/xfer     |   73 ++++----
 6 files changed, 99 insertions(+), 384 deletions(-)

diffs (truncated from 614 to 300 lines):

diff -r 79fa6a188c48 -r 0742a11a91e4 distrib/notes/vax/hardware
--- a/distrib/notes/vax/hardware        Thu May 06 20:51:22 1999 +0000
+++ b/distrib/notes/vax/hardware        Fri May 07 00:15:16 1999 +0000
@@ -1,4 +1,4 @@
-.\" $NetBSD: hardware,v 1.3 1999/01/13 07:30:09 ross Exp $     
+.\" $NetBSD: hardware,v 1.4 1999/05/07 00:15:16 ragge Exp $    
 .
 Hardware supported by NetBSD/vax \*V includes (but may not be limited to): 
 .Bl -tag -width indent -offset indent
@@ -6,7 +6,8 @@
 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,
-MicroVAX 2000/VAXstation 2000 and some VAXstation 3100.
+MicroVAX 2000/VAXstation 2000, VAXstation 3100 model 30,38,40,48,76,
+MicroVAX 3100 (partly) and VAXstation 4000/60.
 .It Em Networking:
 DEUNA/DELUA Unibus ethernet, DEQNA/DELQA Q22 bus ethernet,
 and LANCE chip where available.
@@ -17,12 +18,14 @@
 UDA50 Unibus MSCP controller, KDA50/RQDX1/2/3 Q22 bus
 MSCP controller, KDB50 BI-bus MSCP controller, MFM and
 SCSI controllers on VAXstations, RP04/05/06/07 and
-RM02/03/05/80 Massbus disks, and Console RL02 on 
-VAX 8600.
+RM02/03/05/80 Massbus disks, and Console RL02 on VAX 8600.
 .Pp
 Some third-party controllers are also known to work, other do not.
 .It Em Tapes:
-TMSCP on Q22 bus (TK50/70), SCSI tapes on VAXstations.
+TMSCP on Q22 bus (TK50/70, TU81), TMSCP on BI bus and
+SCSI tapes on VAXstations.
+.It Em Floppy:
+RX33/RX50 on RQDX controllers. RX50 on VAX 8200.
 .El
 .Pp
 The minimal configuration requires 2M of RAM and ~40MB of disk space,
diff -r 79fa6a188c48 -r 0742a11a91e4 distrib/notes/vax/install
--- a/distrib/notes/vax/install Thu May 06 20:51:22 1999 +0000
+++ b/distrib/notes/vax/install Fri May 07 00:15:16 1999 +0000
@@ -1,4 +1,4 @@
-.\" $NetBSD: install,v 1.4 1999/01/13 07:30:09 ross Exp $      
+.\"    $NetBSD: install,v 1.5 1999/05/07 00:15:16 ragge Exp $  
 .\"
 .\" Copyright (c) 1999 The NetBSD Foundation, Inc.
 .\" All rights reserved.
@@ -31,347 +31,51 @@
 .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
 .\" POSSIBILITY OF SUCH DAMAGE.
 .\"
-.
-Installing NetBSD/vax may be a little bit complex, but it shouldn't be too
-hard if you have this document available.
-.
-.Ss2 Device conventions.
-.
-The
-.Nx
-standalone system addresses devices like
-.Ar devicename Ns Ic ( 
-.Ar adapter,\ controller,\ unit,\ partition Ns Ic )
-.No The Ar devicename No values are:
 .Pp
-.Dl mt  No \-  MSCP tape. (TK50, TU81, ...)
-.Dl ts  No \-  TSV05/TS11 tape.
-.Dl ra  No \-  RA??/RD?? disks/floppies.
-.Dl hp  No \-  RP??/RM?? disks.
-.Dl rd  No \-  RD?? disks on MicroVAX 2000.
-.Dl sd  No \-  SCSI disks.
-.Dl st  No \-  SCSI tapes.
-.Dl le  No \-  LANCE ethernet controller.
-.Pp
-You can omit parameters;
-.Ic ra(0,0)
-refers to disk
-.Ic 0
-partition
-.Ic a
-on the default controller. On tapes partition it refers to the file #
-on the tape.
-.(tag Example:
-The DUB1 (DEC syntax) swap partition will be specified as
-.Ic ra(1,0,1) ;
-the DRA2 root partition is
-.Ic hp(2,0) .
-.tag)
-.Pp
-The installation principle is to label the root disk, copy a miniroot
-filesystem onto the swap partition, boot up from that miniroot filesystem,
-then create root and the other wanted partitions and put system to it.
-You will have to deal with 2 different
-.Em units ,
-one is just a boot
-filesystem containing 3 files:
-.Li boot, copy No and Li edlabel ,
-the other is an image of a miniroot filesystem and can be split
-into several pieces depending of what you are going to install from.
-.
-.Ss2 Installation from tape: (MicroVAX II/III)
-.
-Take your newly created boot tape and just boot from it:
-.Dl \*>\*>\*> Ic B/3 MUA0
-This means that you will bring up boot to ask for a boot file from the
-TK50. (MUA0 is the DEC name.) It will come up with something like
-.Bd -literal -offset indent
-
-2..1..0..
-
-howto 0x3, bdev 0x12, booting...done. (31248+22252)
-
-\*>\*> NetBSD/vax boot [970610 23:44] \*<\*<
-: 
-
-.Ed
-.Pp
-At the prompt you type
-.Ic edlabel
-to label the disk, see below about
-how to use edlabel.
-When labeling is finished, halt the computer, bring up the boot program
-again and this time load copy, see below about how to use copy.
-Remember that you must copy from the second file (1) on the tape.
+Installation of NetBSD/vax is now easier than ever!
+For the latest news, problem reports, and discussion, join
+the port-vax mainlist by mailing a line saying
+.Dl subscribe port-vax
+to
+.Mt majordomo%netsbd.org@localhost .
+Also, see
+.Lk http://www.netbsd.org
+for more information.
 .Pp
-Now go to step 3.
-.
-.Ss2 Installation from RX33/RX50. (MicroVAX II/III)
-.
-The difference between RX33 and RX50 is its size. An RX50 is 400k and
-an RX33 is 1200k.
-.Pp
-To boot from floppy type:
-.Dl \*>\*>\*> Ic B/3 DU Ns Ar xy
-.No where Ar x
-is the controller number and
-.Ar y No is the device number.
-.Pp
-You will now get a prompt like
-.Dl \*>\*> NetBSD/vax boot [970610 23:44] \*<\*<
-.Dl :
-At the prompt you type
-.Ic edlabel
-to label the disk, see below about
-how to use it.
-When labeling is finished, halt the computer, bring up the boot program
-again and this time load copy, see below about how to use it.
-Remember that you are will copy from partition 0 when using floppies.
+If you encounter any problems, please report them via the mailing list or the
+.Xr send-pr 1
+program so that they can be fixed for the next release.
 .Pp
-Now go to step 3.
-.
-.Ss2 Installing Over a Network
-.
-You can use the same flags when booting over the net as when
-booting from local disks; like: "\*>\*>\*>B/3 ESA0" will load boot
-in ask state. From here you can load any file you want, even
-copy and edlabel if they are located in the exported root fs.
-.(Note
-Netbooting of MicroVAX II/III systems with DEQNA/DELUA
-ethernet does not work does not work yet because lack of standalone
-drivers. Mounting of root and swap over NFS works well though.
-.Note)
-.(Note
-Mopd won't work on VAXen with de/qe ethernet, due to the
-lack of bpf support for those interfaces.
-.Note)
-.
-.Ss2 Booting up the miniroot
-.
-When copying is complete, bring the boot program up a third
-time, and this time bring up a real system by telling
-boot where you put your miniroot
-.Em and
-also the generic
-kernel name. Example:
-.Ic ra(0,1)gennetbsd
-boots
-.Pa gennetbsd
-from the swap partition on
-.Li ra0 .
+To install or upgrade NetBSD, you need to first boot the installation
+program and then interact with the screen-menu program
+.Ic sysinst .
+The installation program actually consists of the NetBSD kernel plus
+an in-memory file system of utility programs.
 .Pp
-When the kernel is loaded, you will after a while get a
-question about
-.Li Root device?
-Respond to this with
-.Ar xx?* ,
-where
-.Ar xx
-is the device name,
-.Ar ?
-is the unit
-number and * specifies that the system shall use the swap
-partition as root partition. Example:
-.Dl Root device? Ic ra0*
-.Pp
-After that a second question:
-.Dl Enter pathname of shell or RETURN for sh:
-Just type return. Now you will be in a normal single-user
-shell, needing only to
-newfs your partitions, and start installation.
+The usual procedure is to write the installation system to the
+install media, as described earlier.
 .Pp
-A few things that you must remember to do from the miniroot:
-.D1 Ic disklabel -B Ar diskname
-will install boot blocks.
-.Pa MAKEDEV
-your devices in the newly created root filesystem.
-Copy
-.Pa gennetbsd No and Pa boot
-from the miniroot filesystem
-to the newly created root filesystem.
-.
-.Ss2 How to use edlabel
-.
-Edlabel is a program to edit disklabels on any disks in a standalone
-environment. Mostly it is used to set labels when doing initial
-installation procedure. It is started from boot program prompt.
-You will here be guided through a session, things with ^^^^ under
-are typed in by the user, comments are within /* */.
-.Bd -literal -offset indent
-\*>\*> NetBSD/vax boot [970610 23:44] \*<\*<
-: edlabel
-  ^^^^^^^
-With this program you can modify everything in the on-disk
-disklabel. To do something useful you must know the exact
-geometry of your disk, and have ideas about how you want
-your partitions to be placed on disk. Some hints:
-The a partition should be at least ~20000 blocks, the
-b (swap) is depending on your use of the machine but it
-should almost never be less than ~32000 blocks.
-
-Disk geometry for most DEC disks can be found in the disktab
-file, and applicable disk names can be found above.
-
-Remember that disk names is given as disk(adapt, ctrl, disk, part)
-when using the installation tools.
-
-Label which disk? ra(1,0,0)     /* See INSTALL text for device types */
-                  ^^^^^^^^^
-getdisklabel: no disk label
-ra(1,0,0): no disk label
-(E)dit, (S)how, (D)efaults, (W)rite, (Q)uit) : e
-                                               ^
-First set disk type. Valid types are:
-0  unknown
-1  SMD
-2  MSCP
-3  old DEC
-4  SCSI
-5  ESDI
-6  ST506
-7  HP-IB
-8  HP-FL
-9  type 9
-10  floppy
-11  ccd
-12  vnd
-
-Numeric disk type? [0] 2    /* All disks supported this far is MSCP */
-Disk name? [] rd54     ^    /* You must know what type your disk is */
-badsect? [n]  ^^^^          /* No badsectoring yet */
-ecc? [n]                    /* ECC is automatic, don't care */
-removable? [n]              /* Removable or not, like RA60 */
-Interleave? [0] 1           /* All MSCP disks is seen like 1 interleave */
-rpm? [0] 3600   ^           /* 3600 rpm is normal */
-trackskew? [0]              /* don't care */
-cylinderskew? [0]           /* don't care */
-headswitch? [0]             /* don't care */
-track-to-track? [0]         /* don't care */
-drivedata 0? [0]            /* don't care */
-drivedata 1? [0]            /* don't care */
-drivedata 2? [0]            /* don't care */
-drivedata 3? [0]            /* don't care */
-drivedata 4? [0]            /* don't care */
+Booting from install media
+.Pp
+The built-in console monitor understands a bunch of commands, dependent
+of which VAX you have. To just boot from a device, type 'B' at the '>>>'
+prompt. Device naming in the console monitor differs a lot from the
+Unix counterparts. A device looks like "ddcu", where dd is the device
+type, c is the controller number and u is the device unit. Many console
+monitors also support the 'SHOW DEV' command, which shows available
+units to boot from.
+.Pp