Aren/NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Distribution notes for vax. These files should really have been here

Browse Source 
many years ago.
This commit is contained in:
ragge 1997-06-30 19:00:52 +00:00
parent 1c1a1ceb84
commit cdb53701a8
8 changed files with 604 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

127
distrib/notes/vax/contents Normal file
View File

@ -0,0 +1,127 @@
The vax-specific portion of the NetBSD _VER release is found in the
"vax" subdirectory of the distribution. That subdirectory is laid
out as follows:
.../NetBSD-_VER/vax/
INSTALL Installation notes; this file.
binary/ vax binary distribution sets;
see below.
security/ vax security distribution;
see below.
tk50/ Files to install from tape.
rx50/ Files to install from RX50 floppy.
rx33/ Files to install from RX33 floppy.
netboot/ Files needed when netbooting.
.../vax/netboot/
There are a couple of files in the netboot directory; the boot program
in different flavours, a generic kernel and a miniroot image. The files
are described below:
boot The NetBSD loader program, needed to load the
kernel or any standalone program from disk/tape/net.
boot.mopformat The same as above, but in MOP format.
gennetbsd.gz A generic NetBSD/vax kernel, gzipped.
miniroot.tar.gz A tar'ed and gzipped miniroot, unpack this to
get a small netbooted environment.
.../vax/tk50/
.../vax/rx50/
.../vax/rx33/
In these directories there are splitted files of both a small boot
utility filesystem and a miniroot. See the section for installing
to get more about this.
.../vax/binary/
The NetBSD/vax binary distribution sets contain the binaries which
comprise the NetBSD _VER release for the vax. There are seven binary
distribution sets, and the "security" distribution set. The binary
distribution sets can be found in the "vax/binary" subdirectory of
the NetBSD _VER distribution tree, and are as follows:
base13 The NetBSD/vax _VER base binary distribution. You
MUST install this distribution set. It contains the
base NetBSD utilities that are necessary for the
system to run and be minimally functional. It
includes shared library support, and excludes
everything described below.
[ 7.6M gzipped, 21.5M uncompressed ]
comp13 The NetBSD/vax Compiler tools. All of the tools
relating to C and C++. This set includes the system
include files (/usr/include), the linker, the compiler
tool chain, and the various system libraries (except
the shared libraries, which are included as part of the
base set). This set also includes the manual pages for
all of the utilities it contains, as well as the system
call and library manual pages.
[ 5.4M gzipped, 17.2M uncompressed ]
etc13 This distribution set contains the system configuration
files that reside in /etc and in several other places.
This set MUST be installed if you are installing the
system from scratch, but should NOT be used if you are
upgrading. (If you are upgrading, it's recommended that
you get a copy of this set and CAREFULLY upgrade your
configuration files by hand.)
[ 68K gzipped, 350K uncompressed ]
games13 This set includes the games and their manual pages.
[ 2.9M gzipped, 7.0M uncompressed ]
man13 This set includes all of the manual pages for the
binaries and other software contained in the base set.
Note that it does not include any of the manual pages
that are included in the other sets.
[ 0.9K gzipped, 3.5M uncompressed ]
misc13 This set includes the system dictionaries (which are
rather large), the typesettable document set, and
man pages for other architectures which happen to be
installed from the source tree by default.
[ 1.9M gzipped, 6.5M uncompressed ]
text13 This set includes NetBSD's text processing tools,
including groff, all related programs, and their
manual pages.
[ 0.8M gzipped, 2.9M uncompressed ]
.../vax/security/
The vax security distribution set is named "secr13" and can be found
in the "vax/security" subdirectory of the NetBSD _VER distribution
tree. It contains executables which are built in the "src/domestic" portion
if the NetBSD source tree. It can only be found on those sites which carry
the complete NetBSD distribution and that can legally obtain it. (Remember,
because of United States law, this distribution set may not be exported to
locations outside of the United States and Canada.)
[ 128K gzipped, 275K uncompressed ]
The vax binary distribution sets are distributed as gzipped tar files.
Each vax binary distribution set also has its own "CKSUMS" file, just
as the source distribution sets do.
The instructions given for extracting the source sets work equally
well for the binary sets, but it is worth noting that if you use that
method, the files are extracted "below" the current directory. That
is, if you want to extract the binaries "into" your system, i.e.
replace the system binaries with them, you have to run the command:
tar --unlink -zxvpf set.tar.gz
from /. Note that the "--unlink" flags is very important!
For best results, it is recommended that you follow the installation
and/or upgrade procedures documented in this file.

39
distrib/notes/vax/hardware Normal file
View File

@ -0,0 +1,39 @@
Hardware supported by NetBSD/vax _VER includes (but may not be limited to):
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,
MicroVAX 2000/VAXstation 2000 and some VAXstation 3100.
Networking:
DEUNA/DELUA Unibus ethernet, DEQNA/DELQA Q22 bus ethernet
and LANCE chip where available.
Serial lines:
DHU11/DHV11/DL11/DLV11/DZ11/DZQ11/DZV11 Unibus/Q22 bus
asynchronous lines and DZ11-compatible lines on
VAXstations.
Disks:
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. Some third-party controllers are also
known to work, other do not.
Tapes:
TMSCP on Q22 bus (TK50/70), SCSI tapes on VAXstations.
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.
Here is a table of recommended HD partition sizes for a full install:
partition: advise needed
root (/) 20M 10M
user (/usr) 80M 45M
swap (2 or 3 * RAM)
Anything else is up to you!

310
distrib/notes/vax/install Normal file
View File

@ -0,0 +1,310 @@
Installing NetBSD/vax may be a little bit complex, but it shouldn't be too
hard if you have this document available.
Device conventions.
NetBSD standalone system addresses devices like
'devicename(adapter, controller, unit, partition)'
Known devicenames are:
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 #
on the tape.
Example: DUB1 (DEC syntax) swap partition will be referred as
ra(1,0,1), DRA2 root partition is hp(2,0).
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 "units", one is just a boot
filesystem containing 3 files: boot, copy and 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.
Installation from tape: (MicroVAX II/III)
Take your newly created boot tape and just boot from it:
>>> B/3 MUA0
This means that you will bring upp boot to aks for boot file from TK50.
(MUA0 is DEC naming). It will come up something like
2..1..0..
howto 0x3, bdev 0x12, booting...done. (31248+22252)
>> NetBSD/vax boot [970610 23:44] <<
:
At the prompt you type 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.
Now go to step 3.
Installation from RX33/RX50. (MicroVAX II/III)
The difference between RX33 and RX50 is its size. RX50 is 400k and
RX33 is 1200k.
To boot from floppy type:
>>> B/3 DUxy
where x is the controller number and y is device number.
You will now get up a prompt like
>> NetBSD/vax boot [970610 23:44] <<
:
At the prompt you type 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.
Now go to step 3.
Installing over 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 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.
Booting up miniroot.
When copying is ready, bring the boot program up a third
time, and this time bring up a real system by telling
boot where you put your miniroot _and_ also the generic
kernel name. Example: ra(0,1)gennetbsd, boots gennetbsd
from swap partition on ra0.
When kernel is loaded, you will after a while get a
question about Root device?. Respond to this with
xx?*, where xx is the device name, ? is the unit
number and * tells that the system shall use the swap
partition as root partition. Example:
Root device? ra0*
After that a second question:
Enter pathname of shell or RETURN for sh:
Just type return. Now you will be in a normal single-user
shell, and it's just to newfs your partitions, and start installation.
A few things that you must remember to do from miniroot:
disklabel -B <diskname> to install boot blocks.
MAKEDEV devices in the newly created root filesystem.
Copy gennetbsd and boot from miniroot filesystem
to the newly created root filesystem.
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
is typed in by the user, comments are within /* */.
>> 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 */
bytes/sector? [0] 512 /* Probably only sive on VAX systems */
^^^
sectors/track? [0] 17 /* You must know this, check disktab file */
^^
tracks/cylinder? [0] 15 /* You must know this, check disktab file */
^^
sectors/cylinder? [0] 255 /* sectors/track * tracks/cylinder */
^^^
cylinders? [0] 1221 /* You must know this, check disktab file */
^^^^
a partition: offset? [0] /* Partition sizes are set by you. */
size? [0] 20000 /* Take default sizes from disktab or */
b partition: offset? [0] 20000 /* calculate your own partition sizes */
size? [0] 20000
c partition: offset? [0]
size? [0] 311200
d partition: offset? [0]
size? [0]
e partition: offset? [0] 40000
size? [0] 271200
f partition: offset? [0]
size? [0]
g partition: offset? [0]
size? [0]
h partition: offset? [0]
size? [0]
(E)dit, (S)how, (D)efaults, (W)rite, (Q)uit) : s /* Show what you've typed */
^
disk type 2 (MSCP), rd54:
interleave 1, rpm 3600, trackskew 0, cylinderskew 0
headswitch 0, track-to-track 0, drivedata: 0 0 0 0 0
bytes/sector: 512
sectors/track: 17
tracks/cylinder: 15
sectors/cylinder: 255
cylinders: 1221
8 partitions:
size offset
a: 20000, 0
b: 20000, 20000
c: 311200, 0
d: 0, 0
e: 271200, 40000
f: 0, 0
g: 0, 0
h: 0, 0
(E)dit, (S)how, (D)efaults, (W)rite, (Q)uit) : w /* Write label to disk */
This program does not (yet) write bootblocks, only disklabel.
Remember to write the bootblocks from the miniroot later with the
command "disklabel -B <diskname>".
(E)dit, (S)how, (D)efaults, (W)rite, (Q)uit) : q
How to use copy:
Copy is a standalone program that can copy multiple volumes
from disk/tape to disk/tape. Mostly it is used to copy the
miniroot filesystem onto the swap partition during initial
installation.
You will here be guided through a session, things with ^^^^ under
is typed in by the user, comments are within /* */.
This is an installation from TK50.
>> NetBSD/vax boot [970610 23:44] <<
: copy
^^^^
copy:
This program will read miniroot from tape/floppy/disk
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.
"mt(0,1)" for the first TMSCP-tape (TK50),
"ra(2,0)" for the third MSCP-disk/floppy (RX33/RX50)
device to read from ? mt(0,1) /* Tape 0, file 1 */
^^^^^^^^
Specify number of blocks to transfer. Usually this is
sizeof(miniroot) / 512.
It's safe to transfer more blocks than just the miniroot.
number of blocks ? 4096 /* Miniroot size is 4096 block */
^^^^
If your miniroot is split into volumes, then you must
specify the number of blocks per volume.
(e.g. 800 blocks per RX50, 2400 blocks per RX33)
number of blocks per volume ? [4096]
Make sure unit tms(0,1) is online and holds the proper volume.
Then type 'g' to Go or 'a' to Abort.
OK to go on ? [g/a] g /* g == go, a == abort */
^
Reading ... Reading of miniroot done. (4096 blocks read)
Now specify the device to write miniroot to as xx(N,1)
where xx is the drive type and N is the drive number.
For example: ra(0,1) refers to MSCP drive #0, b partition
Root disk ? : ra(0,1) /* Actually DUA0, partition b (swap) */
^^^^^^^^^
Initializing partition ... done.
(4096 blocks written.)
Halt the machine and reboot from distribution media,
giving second partition as part to mount as root. Ex:
: ra(0,1) for ra disk 0, hp(2,1) for massbuss disk 2
Halt/Reboot the machine NOW.
?02 EXT HLT
PC = 001005F3
>>>

9
distrib/notes/vax/legal Normal file
View File

@ -0,0 +1,9 @@
This product includes software developed at Ludd,
University of Lule}, Sweden.
This product includes software developed by Gordon W. Ross.
This product includes software developed by Ben Harris.
This product includes software developed by Adam Glass,
David Jones, and Gordon Ross.

12
distrib/notes/vax/prep Normal file
View File

@ -0,0 +1,12 @@
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.
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.
Also; if you are installing on a VAXstation, you must have a serial
console. The builtin graphic console are not yet supported.

19
distrib/notes/vax/upgrade Normal file
View File

@ -0,0 +1,19 @@
There are no upgrade program for NetBSD/vax, you will have to
upgrade your system by hand. Anyway, here are small hints about
how to do it:
* First replace the kernel, /boot and the boot blocks
with new ones. The boot system has changed since 1.2.
* Reboot the system to be sure you run with the new kernel.
* Untar the wanted distributions. Remember to use the --unlink
flag to tar, otherwise you will run into trouble.
* Reboot the system once again.
* Now you will (hopefully) be up and running in the new world.
NOTE: you SHOULD NOT extract the `etc' set if upgrading. Instead, you
should extract that set into another area and carefully merge the changes
by hand.

1
distrib/notes/vax/whatis Normal file
View File

@ -0,0 +1 @@
This is the second public release of NetBSD for the VAX.

87
distrib/notes/vax/xfer Normal file
View File

@ -0,0 +1,87 @@
Installation is supported from several media types, including:
* Tape
* NFS
* Floppy
* FTP
Note that 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).
The procedure for transferring the distribution sets onto
installation media depends on the type of media. The most 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.
* 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:
mt -f /dev/rmt0h rewind
dd if=tk50-file1-1.3 of=/dev/nrmt0h
dd if=tk50-file2-1.3 of=/dev/rmt0h
mt -f /dev/rmt0h rewoffl
Under NetBSD this is done the same way, except for the tape name:
mt -f /dev/rmt8 rewind
dd if=tk50-file1-1.3 of=/dev/nrmt8
dd if=tk50-file2-1.3 of=/dev/rmt8
mt -f /dev/rmt8 rewoffl
Of course, if you have another tape unit than 0 you have to use
the corresponding unit number.
If you are using any other OS to create bootable tapes, remember that
the blocksize _must_ be 512 for the file to be bootable! Otherwise it
just won't work.
* Creating boot floppies:
Fetch the files from .../NetBSD-1.3/vax/rx{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.
* Booting from NFS server:
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.
If your machine has a disk and network connection, it may be
convenient for you to install NetBSD over the network. This
involves temporarily booting your machine over NFS, just long enough
so you can initialize its disk. This method requires that you have
access to an NFS server on your network so you can configure it to
support diskless boot for your machine. Configuring the NFS server
is normally a task for a system administrator, and is not trivial.
If you are using a NetBSD system as the boot-server, have a look at
the diskless(8) manual page for guidelines on how to proceed with
this. If the server runs another operating system, consult the
documentation that came with it (i.e. add_client(8) on SunOS).
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
ftp.stacken.kth.se:/pub/OS/NetBSD/mopd. Fetch the latest and read the
installation instructions.
The file that should be loaded are called boot and are located in
.../NetBSD-1.3/vax/install. If you are not using the mopd written
by Mats O Jansson (as the NetBSD are) then you should get the file
boot.mopformat instead.
The miniroot to start from is the one called miniroot.tar.gz located
also in the install directory. Fetch it, unzip and untar it wherever
you have your root filesystem.