Remove since long unused files.

This commit is contained in:
ragge 1998-06-20 18:53:01 +00:00
parent abab40ee1c
commit a38dba55a5
5 changed files with 0 additions and 476 deletions

View File

@ -1,12 +0,0 @@
# $NetBSD: BUGS_MISSINGS,v 1.3 1998/01/05 20:51:55 perry Exp $
Programs may be hanging with the D flag set, even if they (HIGH)
don't do I/O at all. (ps, ...) User PTE problem?
950304/Ragge
Uba & devices should be converted to use new style config (MEDIUM)
instead of emulating it. MSCP routines should also be
fixed so that they can support both uda and kdb disks
as device ra?.
/Ragge

View File

@ -1,190 +0,0 @@
$NetBSD: INSTALL,v 1.2 1997/03/15 20:08:33 ragge Exp $
How to install NetBSD/vax
-------------------------
1. 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).
2. Installation.
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
root and the other wanted partitions and put system
to it.
You will have to deal with 2 files, 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.
2.1 INSTALLATION
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
in sequential order; file 1 first and then file2.
_Blocksize_must_be_512!_ Otherwise the tape will not be
bootable. Then type:
>>> B/3 MUA0
This means that you will bring upp boot for asking
from TK50. (MUA0 is DEC naming). It will come up
something like
2..1..0..
howto 0x3, bdev 0x12, booting...
9852+456+34916 start 0x0
Nboot
:
At the prompt you type edlabel to label the disk, see
README.edlabel about how to use it.
When labeling is finished, halt the computer, bring up
the Nboot prompt again and this time load copy, see
README.copy about how to use it. Remember that you are
copying from file 1 on the tape.
Now go to step 3.
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
a couple of files called rxDD-copy?-???.fs, where DD
is 33 or 50 and ??? is the revision of NetBSD.
The RX33 installation will be 3 floppies and RX50
installation will be 7 floppies.
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
Nboot
:
At the prompt you type edlabel to label the disk, see
README.edlabel about how to use it.
When labeling is finished, halt the computer, bring up
the Nboot prompt again and this time load copy, see
README.copy about how to use it. Remember that you are
copying from partition 0 when using floppies.
Now go to step 3.
2.3 Installation from TU58. (VAX 11/750).
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
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.
Good luck! (You may need it)
Ragge

View File

@ -1,57 +0,0 @@
$NetBSD: README,v 1.10 1997/03/15 20:08:34 ragge Exp $
Devices supported in kernel and _known_ to work:
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 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:
* No dynamic linked libraries, all binaries is statically linked.
These things will be fixed in the future.
We who have done parts of the VAX port is:
Joachim Isaksson, first pmap and lots of help with gcc functionality.
Mattias Gr|nlund, locore assembler and interrupt handling.
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.
Have fun with it,
ragge@ludd.luth.se

View File

@ -1,80 +0,0 @@
$NetBSD: README.copy,v 1.3 1997/03/15 20:08:35 ragge Exp $
How to use copy
------------------
Edlabel 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.
Nboot
: copy
^^^^
10480+468+34868 start 0x0
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
>>>
-- Ragge

View File

@ -1,137 +0,0 @@
$NetBSD: README.edlabel,v 1.1 1995/09/16 12:00:19 ragge Exp $
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 /* */.
Nboot
: edlabel
^^^^^^^
11700+576+43200 start 0x0
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 disknames is listed in the installation notes.
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
-- Ragge