Jon,

finally get the mopd working, Chuch got it right. It is case problem.
here is what I got so far.

 -ESA0
>> NetBSD/vax boot [980110 22:29] <<
Trying BOOTP
Bootp: no reply.
Trying bootparams
boot: client ip address 10.10.10.10
boot client name: vax
root addr=10.10.10.1 path=/export/vax/root
nfs_open: must mount first
open netbsd.vax :device not configure
>boot netbsd
trying bootp
bootp: no reply
using ip address 10.10.10.10
myip: vax  (10.10.10.10)
root addr=10.10.10.1 path=/export/vax/root
nfs_open: must mount first
open netbsd :device not configured
netbsd: boot failed: device not configured
............
...........
>

The system just wait there and doing nothing. Is this same as the problem
for netbsd.ram.gz...?

Thanks

Hank Lee


> Also, beware that trying to boot netbsd.ram.gz won't work, as it doesn't
> have support for the 4000/200 built in.
>
> Netbooting a generic kernel and nfs mounting root works great,
> though.  Beware that the mopd that is distributed with 1.5 doesn't work,
> either - you'll have to compile mopd from -current (or, at least I
> did) due to a PR with mopd (bin/11253 - closed, but not in 1.5, perhaps in
> -release?)
>
> With the mopd change, and booting a generic kernel, my 4000/200 works
> great.  I've yet to attempt a manual install due to lack of time, so I
> can't vouch for anything past that yet.
>