> I manually mounted the ramdisk.fs file, and here is what I see in /dev:
> 
> dagobah:11# ls /mnt/dev

Say hello to the force and the spirit of Yoda, for us...... when you next
seek out the dagobah system.....(:+}}...

> console   fb        md0c      rcd0a     rsd0d     rsd2c     rxd0d     stdout
> drum      kbd       mem       rcd0b     rsd1a     rsd2d     rxy0a     tty
> eeprom    kd        mouse     rcd0c     rsd1b     rst0      rxy0b     ttya
> enrst0    klog      nrst0     rcd0d     rsd1c     rst1      rxy0c     ttyb
> enrst1    kmem      nrst1     rsd0a     rsd1d     rxd0a     rxy0d     zero
> erst0     leds      null      rsd0b     rsd2a     rxd0b     stderr
> erst1     md0       pipe|     rsd0c     rsd2b     rxd0c     stdin

                                RAW       RAW       RAW      RAW      block?
> 
> So I am stumped, I don't know what I could be doing wrong here.

Does it need a set of block (sdxxx) as opposed to raw (rsdxxx) mounts?
I don't remember offhand which it mounts, raw or block devices.  Ultrix,
makes both, and I was thinking Sunos made both.  VAX NetBSD makes both,
if memory serves me correctly.  I could be totally out to lunch, too, but
that is all I see, offhand....

.....
 
> > As I have a diskless setup with the 3/160, I just ran ./MAKEDEV on the 
> > nfs server machine, and everything was fine...
> 
> All my diskless setups (1.4, 1.4.1) required a MAKEDEV to be run by me
> because the tar balls did not have most of the devices in them...

What exactly is a second MAKEDEV making that is not on the ramdisk?

Alternatively.....

If I take the crude approach and dd miniroot into swap on sunos and boot
from that, is that still known to work?
 
Bob