At 06:21 PM 12/25/00 -0800, Ben wrote:
>Hi folks, it's Christmas day and I should be playing with the kids,
>but I'm playing with my MV3300 instead :-)

Ah but my daughter and I have been playing with a cluster of VLCs so that's 
considered "quality time" :-)

>On doing b/100 esa0, then entering mopboot as the mop file, I get
>
> >> NetBSD/vax boot [Nov 17 2000 07:23:42] <<
> >> Press any key to abort autoboot 0
>Trying BOOTP
>Using IP address: 192.168.1.28
>myip:  (192.168.1.28)
>root addr=192.168.1.1 path=/

This means that your DHCP server is misconfigured. It gave your VAX an IP 
address but it did not tell the VAX where the NFS files were that it should 
use as its "root" file system.

This varies from DHCP implementation, but what you want is an entry that says
         "for ethernet address 08:00:2b:xx:yy:zz we want:
                 ip address ...
                 server ...
                 root mount point ...
                 hostname ...
                 domainname ..
On my system I do that with this text in my dhcp.conf file:

         host halfvax {
                 hardware ethernet 08:00:2b:26:33:78;
                 fixed-address 192.168.110.64;
                 option subnet-mask 255.255.255.0;
                 option routers 192.168.110.254;
                 option domain-name-servers 192.168.110.254;
                 option host-name "halfvax";
                 option domain-name "hq.home.mcmanis.com";
                 server-name "demon.hq.home.mcmanis.com";
                 option swap-server 192.168.110.30;
                 option root-path "/export/vax/netboot/root.1.4.x";
         }

>After which, the Vax waits and waits and waits, then it reports that
>it is trying to boot netbsd.gz, etc etc

Once you get DHCP set up correctly it will boot the kernel, and if you have 
devices made and the rc.conf configured it will come up multiuser.
--Chuck