>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 :-)
It's always been the case that the Linux 3c509 driver does not need or
want an IO parameter, inspite of it being an ISA card (it's special). I
thought that in recent versions of LTSP, this was filtered out so that
the module didn't get the parameter but maybe you are using an older
release.
Oh, and in v3 you can give meaningful names to the options if you wish,
like etherboot-signature and kernel-parameters.
_______________________________________________________________
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
