TO network boot you need two things apart from a working image. A Bootp server and a TFTP server. A netboot host necessarily only know one thing, its mac address. So you need to set your bootp server up to hand out an IP address a tftp server and an image filename. Obviously you don't want to give this same info to any bootp request because it might be comming from another peice of kit so you need to put the MAC into the Bootp server as a means of identifing who to respond to. I also seem to recall that Bootp only works in MAC to IP mappings, I don't think it works with pools like DHCP does, although I may be wrong there because my net-booting experience comes from Nortel switches which always have fixed addresses anyway.
Damn Small linux may do what you want. Other small Distros, off the top of my head, are feather and puppy. I quite like DSL cos its about 56meg and you can boot it from a flash key
I would suggest you look at NX for your thin client protocol.
Last edited by baldy3105; 01-19-2006 at 04:49 AM.