> Robert, > >> > If your tftpd is using the "-s" option (which it says it is), then you >> > shouldn't need to put the "/tftpboot" bit in there. /tftpboot becomes >> > the root directory for any tftp clients.
Tried with and without the -s option ((Apparently atftpd does not use it anyway) >> I understand that but (perhaps wrongly) assumed that the section >> shared-network WORKSTATIONS >> was not used if there is a section for specific hosts/MAC addresses. > > True enough. It's probably a good idea to fix it just in case you get > another computer and forget to add it to your dhcpd.conf. This did not work either. >> Well I think the network booting must be OK for it to get as far as >> it >> > > does. Is that a fair assumption. >> > > If you have EPROMs on your network cards, or have etherboot floppy's > then you are using etherboot. Yes there are eeproms on the NIC's As I said earlier it gets an IP address OK so the initial part is fine. We have tried all suggestions so far but still the clients just hang on loading the vmlinuz file >
