[K12OSN] Doing the Pivot Root - befuddling
Petre Scheie
petre at maltzen.net
Sun Aug 28 19:30:16 UTC 2005
Fixed it! Les is correct, lines 5 & 6 need to be in the main part of
the config file--which they already were. With those removed from the
scope, and with a space (not a comma) between the 'NIC=3c509'
specification and the part the wiki told me to add, it now works. In
other words, this is my dhcpd.conf:
host wendolene {
hardware ethernet 00:20:AF:14:DB:0B;
fixed-address 172.26.18.5;
filename "/lts/vmlinuz.ltsp";
option option-128 e4:45:74:68:00:00;
option option-129 "NIC=3c509 MOPTS=nolock,ro,wsize=2048,rsize=2048";
}
Thanks to all for the help.
Les Mikesell wrote:
>On Sun, 2005-08-28 at 13:51, Petre Scheie wrote:
>
>
>>Thanks, Jim. I added the lines to my dhcpd.conf file, thusly (line
>>numbers added here for clarity):
>>
>>1 host wendolene {
>>2 hardware ethernet 00:20:AF:14:DB:0B;
>>3 fixed-address 172.26.18.5;
>>4 filename "/lts/vmlinuz.ltsp";
>>5 option option-128 code 128 = string;
>>6 option option-129 code 129 = text;
>>7 option option-128 e4:45:74:68:00:00;
>>8 option option-129 "NIC=3c509,
>>MOPTS=nolock,ro,wsize=2048,rsize=2048";
>>9 }
>>
>>But when I try to start dhcpd, it says "option definitions may not be
>>scoped." in reference to lines 5 and 6. I tried commenting them out,
>>thinking they were perhaps just examples of the syntax, but then the
>>client says it can't find the 3c509 module during the modprobe stage.
>>Suggestions?
>>
>>
>
>"May not be scoped" means that the option type declarations have
>to be in the global part of the config file, not inside the
>{} braces for any particular subnet or hardware address. Just
>move lines 5 and 6 to the top of the file with other globals.
>The values for any option (lines 7 and 8) can be different for
>each scope, just not the type of the data.
>
>
>
More information about the K12OSN
mailing list