Wow, I suddenly got quite surprised, I thought I was the last person that
sometimes use RL02's :-)

First you may need to create device nodes for all disks; do that by:

# cd /dev; sh MAKEDEV rl0 rl1 rl2 rl3

Creating filesystems on a RL02 is simple. Assuming that you don't want
to have separate partitions on them (hey, they're only 10MB each) you
can just do:

# newfs -I rl0c				Ignore the absence of disklabel
# mount -t ffs /dev/rl0c /mnt		Just mount it

If you want to have a disklabel you can write one to the disk by doing:

# disklabel rl0 > /tmp/foo
# disklabel -R -r rl0 /tmp/foo

and you have gotten a default label on the pack.

Note that the driver is not heavily tested with multiple disks on one
controller; I only had one drive to mine. I have tested it in simh though, 
but reality and emulators may differ sometimes.

Please tell how you this works for you and if you have any problems.

-- Ragge

> Hello from Gregg C Levine
> I am assisting a company in making its Vax system, with a KA655 type
> processor run NetBSD. It works very well. However, they have a quad
> arrangement of RL02 type diskpacks, and they want to use them for storing
> NetBSD based filesystems on them. I am going put down here, the way it
> appeared in the dmesg output for the system:
> rlc0 at uba0 csr 174400 vec 160 ipl 15
> rl0 at rlc0 drive 0: RL02, drive ready
> rl1 at rlc0 drive 1: RL02, drive ready
> rl2 at rlc0 drive 2: RL02, drive ready
> rl3 at rlc0 drive 3: RL02, drive ready
> However, even after going over the man pages for newfs, and disklabel, I am
> baffled. Exactly what steps are to be taken to actually do all of that? As I
> understand things, the disks need to be labeled, and then the newfs program
> creates the filesystem, then if need be fsck would then be run next. But its
> how they are applied, is what gets me. Please understand that I've worked
> with NetBSD/i386 several times, but NetBSD/vax confuses me.
> Gregg C Levine drwho8@worldnet.att.net
> "Oh my!" The Second Doctor's nearly favorite phrase.
> 
> 
>