>  > 	Looks like the build forgot to run /dev/MAKEDEV on the ramdisk
>  > 	for netbsd-rd... Todd - one for you? :)

I didn't have a build log saved for that part, so I ran a make clean && make
and according to the build log it did this:

SPECIAL mkfifo dev/pipe
COPY    ${TOPDIR}/common/rd.MAKEDEV     dev/MAKEDEV
SPECIAL cd dev; sh MAKEDEV std md0 cd0 st0 st1 sd0 sd1 sd2 xd0 xy0
SPECIAL /bin/rm dev/MAKEDEV

I manually mounted the ramdisk.fs file, and here is what I see in /dev:

dagobah:11# ls /mnt/dev
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

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

> I had the same problem with the other snapshot I installed - there were 
> no devices in /dev 

That's usually the case with the *.tgz files, I think.

sysinst runs ``sh MAKEDEV all'' as pretty much the last step of installation.

> 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...

Todd Whitesel
toddpw @ best.com