From 10bf322448701b7c0ab4bc55532a86e8e9713e8a Mon Sep 17 00:00:00 2001 From: ragge Date: Sat, 15 Mar 1997 20:08:33 +0000 Subject: [PATCH] Make install docs more up-to-date. --- sys/arch/vax/INSTALL | 69 +++++++++++++++++++++++++++++++++------- sys/arch/vax/README | 29 ++++++++++------- sys/arch/vax/README.copy | 6 ++-- 3 files changed, 78 insertions(+), 26 deletions(-) diff --git a/sys/arch/vax/INSTALL b/sys/arch/vax/INSTALL index 635034c26d61..a5b56e19b175 100644 --- a/sys/arch/vax/INSTALL +++ b/sys/arch/vax/INSTALL @@ -1,4 +1,4 @@ - $NetBSD: INSTALL,v 1.1 1995/09/16 12:00:21 ragge Exp $ + $NetBSD: INSTALL,v 1.2 1997/03/15 20:08:33 ragge Exp $ How to install NetBSD/vax @@ -8,10 +8,14 @@ How to install NetBSD/vax NetBSD standalone system addresses devices like 'devicename(adapter, controller, unit, partition)' Known devicenames are: - tms - TMSCP tape. - ts - TSV05/TS11 tape. - ra - RA??/RD?? disks/floppies. - hp - RP??/RM?? disks. + mt - MSCP tape. (TK50, TU81, ...) + ts - TSV05/TS11 tape. + ra - RA??/RD?? disks/floppies. + hp - RP??/RM?? disks. + rd - RD?? disks on MicroVAX 2000. + sd - SCSI disks. + st - SCSI tapes. + le - LANCE ethernet controller. You can omit parameters; ra(0,0) refers to disk 0 partition a on default controller. On tapes partition refers to file # @@ -23,10 +27,11 @@ How to install NetBSD/vax 2. Installation. - This document only covers installation of a miniroot - filesystem on the swap partition of a disk. Installation - of the remaining system is best done over network or - from tape, but this is your own decision. + This document covers installation of a miniroot filesystem on + the swap partition of a disk from tape/floppy, or setting up + a netbooted environment. + Installation of the remaining system on a local disk is best + done over network or from tape, but this is your own decision. 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 @@ -42,7 +47,7 @@ How to install NetBSD/vax 2.1 INSTALLATION -2.1.1 Installation from TK50. (MicroVAX II) +2.1.1 Installation from TK50. (MicroVAX II/III) You will need a file called tk50-file1-???.fs and a file called tk50-file2-???.fs, where ??? is the revision og NetBSD. These files must be written on tape @@ -76,7 +81,7 @@ How to install NetBSD/vax Now go to step 3. -2.2 Installation from RX33/RX50. (MicroVAX II) +2.2 Installation from RX33/RX50. (MicroVAX II/III) The difference between RX33 and RX50 is its size. RX50 is 400k and RX33 is 1200k. You will need a file called rxDD-bootdisk-???.fs and @@ -107,8 +112,48 @@ How to install NetBSD/vax 2.3 Installation from TU58. (VAX 11/750). - Not yet :-( But will be... + Not yet :-( +2.4 Setting up a net-booted environment (VS2000) + + All VAXen that can boot over network uses MOP, a DEC protocol. + To be able to use MOP, a MOP daemon must be present on one of + the machines on the local network. The boot principle is: + * The VS2000 broadcast a wish to load an image. + * A mopd answers and send the boot program to the VAX. + * The boot program does rarp requests, mounts the root filesystem + and loads the kernel. + * The kernel is loaded and starts executing. + + You must have a mop daemon available to be able to boot. + A mopd written by moj@stacken.kth.se can be found at + ftp.stacken.kth.se:/pub/OS/NetBSD/mopd, and can be compiled + on many different architectures. + The boot program uses bootparamd for the rest of the boot sequence + in exactly the same way as SUNs does. + + To set up a netbooted environment, you need to do the following: + * Get a mop daemon, and read the docs for configuration. The boot + file that shall be loaded is snapshot/boot.mopformat + * Get the snapshot tar files, and unpack them in a exportable + directory somewhere. Do also put the netbsd.GENERIC kernel + in the root of your NetBSD/vax hierarchy. Be sure you + remember to populate the /dev directory. + * Put the VS2000 ethernet number in ethers, the path to mount + root and swap in bootparams and exports and be sure to + export it. See your diskless docs for this. + * Now it shall boot up diskless. + + 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 1: 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 goos though. + Note 2: Mopd won't work on VAXen with de/qe ethernet, due to the + lack of bpf support for those interfaces. 3. Booting up miniroot. When copying is ready, bring the boot program up a third diff --git a/sys/arch/vax/README b/sys/arch/vax/README index 1dc4199312cb..8fb152bfa0e6 100644 --- a/sys/arch/vax/README +++ b/sys/arch/vax/README @@ -1,37 +1,42 @@ - $NetBSD: README,v 1.9 1995/09/16 12:00:21 ragge Exp $ + $NetBSD: README,v 1.10 1997/03/15 20:08:34 ragge Exp $ Devices supported in kernel and _known_ to work: -CPU: VAX 11/750 with 2-14MB of memory. - KA630 (MicroVAX II) with 2-16 MB memory. +CPU: VAX11/750, VAX11/78X, VAX86X0. + MicroVAX II/III (MicroVAX 3200/3300/3400/3500/3600/3800/3900) + VAXstation 2000/MicroVAX 2000. Net: DEUNA/DELUA Unibus ethernet cards. DEQNA/DELQA Q22 bus ethernet cards. + LANCE ethernet. Disks: UDA50 Unibus MSCP controller. KDA50/RQDX3 Q22 bus MSCP controller. RA??-disks on UDA50 or KDA50. RD??-disks on RQDX3. (known as RA?? by system). + RP??/RM?? disks on Massbus. + RD?? disks on MFM ctlr. + SCSI disks. Tapes: DILOG Q22 bus tape ctlr w/ Exabyte. (TMSCP emulating) TSV05 Q22 bus tape ctlr. + SCSI tapes. TK50 (TMSCP) on Q22 bus. Other TMSCP ctlrs may also work, but haven't tried. -To install and run NetBSD/vax you need a MicroVAX II or VAX 11/750 -with at least 4MB of memory, and a usable install media. Supported -install media is TK50 tape and RX33/RX50 floppy. If you do initial -installation from floppy then you need a way to load the rest of -the system, like tape or ethernet. -NOTE! TU58 INSTALLATION IS NOT YET SUPPORTED, BUT WILL BE. +To install and run NetBSD/vax you need at least 4MB of memory, +and a usable install media. I can provide (on request) a kernel that +will netboot and run fine on standard 2MB VS2000. +Supported install media is TK50 tape and RX33/RX50 floppy, or over +the net. If you do initial installation from floppy then you need a way +to load the rest of the system, like tape or ethernet. +NOTE! TU58 INSTALLATION IS NOT YET SUPPORTED. Actually, the system will run fine on only 2MB of memory, but installation program needs 4MB. If this causes trouble for someone tell me and I'll fix it. Differences between the NetBSD/vax port and other ports: - * It uses gcc 2.7.0 as default compiler. - * libm is not the same as the other ports; instead it is 4.4BSD libm. * No dynamic linked libraries, all binaries is statically linked. These things will be fixed in the future. @@ -42,6 +47,8 @@ We who have done parts of the VAX port is: Mattias ]slund, lots of help and ideas everywhere. Bertram Barth, bootblocks and boot routines for MicroVAX. Rick Macklem, fixed all MicroVAX II, TMSCP and DEQNA support. + Gunnar Helliesen is maintaining the NetBSD/VAX FAQ. + Ken Wellsch wrote DHU11 driver and did kernel optimizations. Anders Magnusson (ragge), that's me, who put things together and wrote the rest. diff --git a/sys/arch/vax/README.copy b/sys/arch/vax/README.copy index 610ea12e6eaf..a55d07660ee8 100644 --- a/sys/arch/vax/README.copy +++ b/sys/arch/vax/README.copy @@ -1,4 +1,4 @@ - $NetBSD: README.copy,v 1.2 1995/09/29 16:33:38 ragge Exp $ + $NetBSD: README.copy,v 1.3 1997/03/15 20:08:35 ragge Exp $ How to use copy ------------------ @@ -24,10 +24,10 @@ and install this miniroot onto disk. Specify the device to read from as xx(N,0), where xx is the device-name and N is the unit-number, e.g. -"tms(0,1)" for the first TMSCP-tape (TK50), +"mt(0,1)" for the first TMSCP-tape (TK50), "ra(2,0)" for the third MSCP-disk/floppy (RX33/RX50) -device to read from ? tms(0,1) /* Tape 0, file 1 */ +device to read from ? mt(0,1) /* Tape 0, file 1 */ ^^^^^^^^ Specify number of blocks to transfer. Usually this is sizeof(miniroot) / 512.