Source-Changes-HG archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

[src/netbsd-1-4]: src/distrib/notes/vax pullup 1.3->1.4 (ragge). Ragge, you o...



details:   https://anonhg.NetBSD.org/src/rev/babe256d7aaf
branches:  netbsd-1-4
changeset: 468690:babe256d7aaf
user:      perry <perry%NetBSD.org@localhost>
date:      Fri May 07 15:06:13 1999 +0000

description:
pullup 1.3->1.4 (ragge). Ragge, you owe me a tanker truck of single malt.

diffstat:

 distrib/notes/vax/hardware |  13 +++++---
 distrib/notes/vax/prep     |   9 +++-
 distrib/notes/vax/upgrade  |   4 +-
 distrib/notes/vax/whatis   |   4 +-
 distrib/notes/vax/xfer     |  73 ++++++++++++++++++++++++---------------------
 5 files changed, 57 insertions(+), 46 deletions(-)

diffs (216 lines):

diff -r 0b10d568de92 -r babe256d7aaf distrib/notes/vax/hardware
--- a/distrib/notes/vax/hardware        Fri May 07 15:05:10 1999 +0000
+++ b/distrib/notes/vax/hardware        Fri May 07 15:06:13 1999 +0000
@@ -1,4 +1,4 @@
-.\" $NetBSD: hardware,v 1.3 1999/01/13 07:30:09 ross Exp $     
+.\" $NetBSD: hardware,v 1.3.2.1 1999/05/07 15:06:13 perry 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 0b10d568de92 -r babe256d7aaf distrib/notes/vax/prep
--- a/distrib/notes/vax/prep    Fri May 07 15:05:10 1999 +0000
+++ b/distrib/notes/vax/prep    Fri May 07 15:06:13 1999 +0000
@@ -1,4 +1,4 @@
-.\" $NetBSD: prep,v 1.3 1999/01/13 07:30:10 ross Exp $ 
+.\" $NetBSD: prep,v 1.3.2.1 1999/05/07 15:06:14 perry Exp $    
 .
 VAX machines usually need little or no preparation before installing
 NetBSD, other than the usual, well advised precaution of BACKING UP
@@ -9,6 +9,9 @@
 either 772150 (DUA) or 760334 (DUB). These two addresses are the
 only recognized by the kernel and boot programs.
 .Pp
-Also; if you are installing on a VAXstation, you must have a serial
-console. The builtin graphic console are not yet supported.
+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.
 
diff -r 0b10d568de92 -r babe256d7aaf distrib/notes/vax/upgrade
--- a/distrib/notes/vax/upgrade Fri May 07 15:05:10 1999 +0000
+++ b/distrib/notes/vax/upgrade Fri May 07 15:06:13 1999 +0000
@@ -1,4 +1,4 @@
-.\" $NetBSD: upgrade,v 1.3 1999/01/13 07:30:10 ross Exp $      
+.\" $NetBSD: upgrade,v 1.3.2.1 1999/05/07 15:06:14 perry Exp $ 
 .\"
 .\" Copyright (c) 1999 The NetBSD Foundation, Inc.
 .\" All rights reserved.
@@ -38,7 +38,7 @@
 .Bl -bullet -offset indent
 .It
 First replace the kernel, /boot and the boot blocks
-with new ones. The boot system has changed since 1.2.
+with new ones. The boot system has changed since 1.3.
 .It
 Reboot the system so you are running with the new kernel.
 .It
diff -r 0b10d568de92 -r babe256d7aaf distrib/notes/vax/whatis
--- a/distrib/notes/vax/whatis  Fri May 07 15:05:10 1999 +0000
+++ b/distrib/notes/vax/whatis  Fri May 07 15:06:13 1999 +0000
@@ -1,6 +1,6 @@
-.\" $NetBSD: whatis,v 1.3 1999/01/13 07:30:10 ross Exp $       
+.\" $NetBSD: whatis,v 1.3.2.1 1999/05/07 15:06:14 perry Exp $  
 .
-This is the second public release of
+This is the third public release of
 .Nx
 for the
 .Tn VAX .
diff -r 0b10d568de92 -r babe256d7aaf distrib/notes/vax/xfer
--- a/distrib/notes/vax/xfer    Fri May 07 15:05:10 1999 +0000
+++ b/distrib/notes/vax/xfer    Fri May 07 15:06:13 1999 +0000
@@ -1,4 +1,4 @@
-.\" $NetBSD: xfer,v 1.3 1999/01/13 07:30:10 ross Exp $ 
+.\" $NetBSD: xfer,v 1.3.2.1 1999/05/07 15:06:14 perry Exp $    
 .
 Installation is supported from several media types, including:
 .Bl -bullet -compact -offset indent
@@ -13,33 +13,35 @@
 .El
 .(Note
 Installing on a "bare" machine requires some bootable
-device; either a tape or floppy drive or Sun-compatible NFS server
-with MOP capabilities. (Yes, NetBSD/vax uses the same netboot
-principles as Sun's does).
+device; either a tape or floppy drive or a NFS server together
+with a machine that can act as a MOP loader.
+NetBSD/vax can use both BOOTP/DHCP and
+BOOTPARAMS for netboot installations.
 .Note)
 .Pp
 The procedure for transferring the distribution sets onto
-installation media depends on the type of media. The most is up to
+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.
 .
 .Ss2 Creating boot tapes
 .
-Fetch the two files from .../NetBSD-1.3/vax/tk50. Write them onto
-the tape, first file1 and then file2. Under Ultrix this is done
-just like this:
+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
 .D1 Ic "mt -f /dev/rmt0h rewind
-.D1 Ic "dd if=tk50-file1-1.3 of=/dev/nrmt0h
-.D1 Ic "dd if=tk50-file2-1.3 of=/dev/rmt0h
+.D1 Ic "dd if=miniroot 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=tk50-file1-1.3 of=/dev/nrmt8
-.D1 Ic "dd if=tk50-file2-1.3 of=/dev/rmt8
+.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 0 you have to use
+Of course, if you have a tape unit other than unit 0 you have to use
 the corresponding unit number.
 .Pp
 If you are using any other OS to create bootable tapes, remember that
@@ -49,13 +51,18 @@
 .
 .Ss2 Creating boot floppies
 .
-Fetch the files from
-.Dl \&.../NetBSD-1.3/vax/rx Ns Ar {50,33}
-depending of which 
-floppy you have. There are three or seven files depending of the
-density of your floppies. Then just write the floppies using dd (under
-Unix, if you are creating floppies from DOS use some nice utility
-for that). There are one bootable floppy and a splitted miniroot image.
+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.
+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
+the preferred way to do this is using RAWRITE.EXE.
 .
 .Ss2 Booting from NFS server
 .
@@ -64,11 +71,11 @@
 the machines on the local network. The boot principle is:
 .Bl -bullet -compact -offset indent
 .It
-The VS2000 broadcast a wish to load an image.
+The VAX broadcast a wish to load an image.
 .It
 A mopd answers and send the boot program to the VAX.
 .It
-The boot program does rarp requests, mounts the root filesystem
+The boot program does rarp/bootp requests, mounts the root filesystem
 and loads the kernel.
 .It
 The kernel is loaded and starts executing.
@@ -92,20 +99,18 @@
 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
-
-\~\~\~\~\~\~
 .Lk ftp.stacken.kth.se:/pub/OS/NetBSD/mopd
-.Pp
 Fetch the latest and read the
 installation instructions.
 .Pp
-The file that should be loaded are called boot and are located in
-.Dl .../NetBSD-1.3/vax/install.
-If you are not using the mopd written
-by Mats O Jansson (NetBSD) then you should get the file
-boot.mopformat instead.
+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}
 .Pp
-The miniroot to start from is the one called
-.Pa miniroot.tar.gz
-located also in the install directory. Fetch it, unzip and untar
-it wherever you have your root filesystem.
+The kernel to load is the same kernel as the miniroot uses and can 
+be found in
+.Dl \&.../NetBSD-\*V/vax/installation/netboot/netbsd.gz Ns Ar {50,33}
+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
+.Lk http://world.std.com/~bdc/projects/vaxen/VAX-netboot-HOWTO.html
+that describes netbooting of VAXen from many different OS'es.



Home | Main Index | Thread Index | Old Index