I recently wanted to use a ThinkPad T22 as an LTSP client, which meant
using the PXE magic documented in
http://www.ltsp.org/documentation/pxe.howto.html, which in turn meant
upgrading my version 2.x dhcp as supplied with RedHat 7.1 to 3.x
(intelligent readers will note this was one of those two minute jobs
that took two days...).
As some of my clients require the option-128 stuff, I also then had to
learn about the
option option-128 code 128 = string;
option option-129 code 129 = text;
entries required in dhcpd.conf 3.x. However, despite doing this, one of
my clients now refused to boot. By trial and error, I discovered that I
had to change its dhcdp.conf entry from:
dhcpd v2.x:
host whatever {
hardware ethernet xx:xx:xx:xx:xx:xx;
fixed-address 192.168.0.n;
filename "/lts/vmlinuz-2.4.9-ltsp-6";
option option-128 e4:45:74:68:00:00;
option option-129 "NIC=3c509 IO=0x300";
}
dhcpd v2.x:
host whatever {
hardware ethernet xx:xx:xx:xx:xx:xx;
fixed-address 192.168.0.n;
filename "/lts/vmlinuz-2.4.9-ltsp-6";
option option-128 e4:45:74:68:00:00;
option option-129 "NIC=3c509";
}
I've no idea at all why this should be, but if anyone runs into similar
problems, I suggest you try this solution... and if you upgrade from
dhcpd 2 to 3, reboot all your clients and make sure they still work :-)
John
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_____________________________________________________________________
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
