On Thu, 14 Mar 2002, Stephen M Jones wrote:

> otaku's /etc/bootptab:
> 
> bjork:\
>         :ht=ether:\
>         :ha=08002BC3C532:\
>         :sm=255.255.255.240:\
>         :lg=207.202.214.131:\
>         :ip=207.202.214.137:\
>         :hn:\
>         :bf=netboot:\
>         :bs=auto:\
>         :hd=/tftpboot:\
>         :vm=rfc1048:
> 
> (note, I'm using hd instead of rp, hd is where my netbsd.gz file is)

  I believe that will cause you problems once you manage to get netboot
loaded and running.  Netboot needs rp to nfs mount the path to the kernel
file.

  I can't see any obvious reason netboot isn't getting loaded.  One thing
that could be done is to run tcpdump and capture all the traffic to/from
bjork and see if it's even attempting a tftp transfer.

  Another difference I see between your bootptab and the one I've used to
netboot alphas is that your bootptab doesn't have an sa entry for the
address of the tftp server.  That shouldn't be a problem though, since
bootpd should be sending back it's own IP address if the sa entry is
missing.

> what /tftpboot looks like on otaku:
> 
> drwxr-xr-x  2 root  wheel      512 Mar 13 02:56 mop
> -r--r--r--  1 root  wheel    61392 Mar 11 21:49 netboot
> -rw-r--r--  1 root  wheel  2538549 Aug 18  2001 netbsd.gz
> lrwxr-xr-x  1 root  wheel        1 Mar 14 06:33 tftpboot -> .
...
> So, I sort of assumed that mopd might be able to be used to grab 'netboot',
> so I tried it:
> 
> bjork:
> 
> P00>>>boot ewa0 -p mop -fi netboot
> (boot ewa0.0.0.2.1 -file netboot -flags -a)
> Trying MOP boot.
> ..
> 
> Network load complete.
> bootstrap code read in
> base = 200000, image_start = 0, image_bytes = 0
                                  ^^^^^^^^^^^^^^^
  This doesn't look too good, I think that's supposed to be the size of
the image loaded from the MOP server.

> otaku:
> 
> # mopd -a -d -f
> MOP DL 802.3 8:0:2b:c3:c5:32   > ab:0:0:1:0:0      len   54 code 08 RPR 
> MOP DL 802.3 0:60:97:d1:61:b1  > 8:0:2b:c3:c5:32   len    9 code 03 ASV 
> MOP DL 802.3 8:0:2b:c3:c5:32   > 0:60:97:d1:61:b1  len   54 code 08 RPR 
> MOP DL 802.3 0:60:97:d1:61:b1  > 8:0:2b:c3:c5:32   len   14 code 02 MLD
> 
> So I suppose thats not possible (maybe there is a boot.mop for the 
> alpha as there is for the VAX?).

  What do you have in /tftpboot/mop?

  I don't know of a boot.mop file for the alpha, although a brief look
through mopd seems to indicate that it might not take too much effort to
convert the netboot file into a mop-loadable image.

--
Michael L. Hitch			mhitch@montana.edu
Computer Consultant
Information Technology Center
Montana State University	Bozeman, MT	USA