Warning. Un-verified speculation ahead.
I don't actually have any PXE bootable NICs, but if I read correctly then
I think it should be possible to boot using PXE and Etherboot (as per
http://www.ltsp.org/documentation/pxe.howto.html) with DHCPD version 2 by
using multiple host definitions like:
host PXEClient {
filename "/eepro100.lzpxe";
}
host ws137 {
hardware ethernet xx:xx:xx:xx:xx:xx;
filename "/lts/vmlinuz-test.nbi";
}
In theory the PXE stage should use the client identifier "PXEClient" which
would be matched against the hostname (and use the first block), and the
etherboot stage would use a different client identifier and drop through to
match by its MAC address in the second block.
n.b. dhcpd apparently considers all host definitions containing a "fixed
address" line before all that don't, and I don't think you'd want to have
all your PXE boot clients get the same address when trying to load
etherboot. Definitions like:
host fubar {
some option;
}
Should result in dhcpd doing a host lookup (as per resolv.conf) for "fubar"
and assigning the corresponding address if it's in the right subnet
(otherwise it would assign an address from its dynamic address range).
Would anyone (who uses PXE) like to try this and tell me if it works?
Otherwise I'll have to wait until I get more expensive NICs ;)
--
Microsoft is not the answer!
"Microsoft?" is the question.
"NO!" is the answer.
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.openprojects.net
