5.3Beta7: diskless boot, has someone succeeded?

[spam maps]

Hello,

For a long time I have been using diskless boot
for several of my 4.X systems.

At the moment I have a 5.3-Beta7 PC and want to try
that out as the master for another diskless PC.

I follow the 4.X style from the Handbook, using the
bootpd setup; I have applied modifications for 5.X
here and there (f.ex. in the clone_root script),
but I am still at a loss why it's not working.

tftp is enabled in inetd, but I start bootpd from
the command line, to watch its verbose output:

---------------------------------------------------
# /usr/libexec/bootpd -d4
   bootptab mtime: Wed Oct 13 23:33:16 2004
   reading "/etc/bootptab"
   read 2 entries (1 hosts) from "/etc/bootptab"

   recvd pkt from IP addr 0.0.0.0
   bootptab mtime: Wed Oct 13 23:33:16 2004
   request from Ethernet address 00:A0:B0:0E:3A:95
   found 192.168.123.1 (disklesspc)
   bootfile="//boot/kernel/kernel"
   vendor magic field is 99.130.83.99
   request message length=548
   request has DHCP msglen=1500
   extended reply, length=1458, options=1222
   sending reply (with RFC1048 options)
   setarp 192.168.123.1 - 00:A0:B0:0E:3A:95

   recvd pkt from IP addr 0.0.0.0
   bootptab mtime: Wed Oct 13 23:33:16 2004
   request from Ethernet address 00:A0:B0:0E:3A:95
   found 192.168.123.1 (disklesspc)
   bootfile="//boot/kernel/kernel"
   vendor magic field is 99.130.83.99
   request message length=1460
   request has DHCP msglen=1460
   extended reply, length=1418, options=1182
   sending reply (with RFC1048 options)
   setarp 192.168.123.1 - 00:A0:B0:0E:3A:95
---------------------------------------------------

The diskless PC finds the bootpd server, starts
loading the kernel (lots of "......." on the
screen, and there's a "[done]" at the end.
Then the diskless system waits for a few minutes
and reboots, repeating the above all over again.


I actually can boot the "diskless" PC normally,
because it does have a harddisk; in that case,
when I probe bootpd and rpcbind to the master
(192.168.123.254) I get:

 # bootptest 192.168.123.254
 bootptest: version 2.4.3
 Sending to 192.168.123.254 (request) htype:0 hlen:0
    xid:565 C:192.168.123.1 vend-rfc1395
    Recvd from 192.168.123.254 (reply) htype:0 hlen:0
    xid:565 C:192.168.123.1 S:192.168.123.254
    sname:"lahaye.snu.ac.kr"
    file:"//boot/kernel/kernel" vend-rfc1395
    SM:255.255.255.0 GW:192.168.123.254
    ROOT:"192.168.123.254:/tftpboot" HN:"disklesspc"


   # rpcinfo -s 192.168.123.254
   program version(s) netid(s)  service   owner
    100000  2,3,4  local,udp6,tcp6,udp,tcp  rpcbind
        superuser
    100005  3,1    tcp6,udp6,tcp,udp        mountd
        superuser


What worries me is, when I do on the master:

  # showmount -e -a
  RPC: Port mapper failure
  showmount: can't do mountdump rpc


Any idea what I have done wrong?
Or how to investigate this further?

Thanks,
Rob.

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com