Chuck McManis wrote:

> At 02:00 PM 1/14/01 +0000, Paul Duncan wrote:
> >Okay, so it turns out I had the wrong hostname  in my bootparams file.
> >
> >So now what happens is this (on the console):
> >
> >     > boot
> >     Trying BOOTP
> >     bootp: no reply
>
> This really looks like a DHCP boot without any parameters in the other
> fields, are you sure DHCP isn't answering for this machine somehow?
>

If it is, I want to know how!! I've just checked. there is no process with the
characters dhcp in it running. And there is no reference to dhcp in
/etc/inetd.conf.

>
> Can you describe in detail the "players" in this dance, what your network
> number is, what the IP address of the server is, what the IP address is
> that you want for the VAX client, and what daemons are running on the
> server. Also what other machines are on this network. (I discovered that
> MOPD on VMS will try to "help" a booting VAX sometimes and really confuse it!)
>

LOL at ""players" in this dance" :-) Okay. There's a linux server at 192.168.1.1,
and its running mopd, rpc.bootparamd, rarp -f and nfsd.

The vax should be 192.168.1.20, and its picking that up from rarp.

There is another Linux box, but its isn't running anything except an NFS server.
Anyway, I've just killed that, and re-tried booting. Okay ist still doing the
same thing, but when it first goes to attempt to boot via bootparamd, one of the
messages it comes up with, which I forgot to include earlier is:

    nfs_open: must mount first
    open netbsd.vax: Device not configured

Hopefully this will make something go click and you can tell me what I'm doing
wrong!

Paul
~~~~