I wonder if a comma would work between the parameters. like this:
option option-129 "NICOPT=duplex=2,speed=10";
Got it working. I tested it out with a \n and the linuxrc script takes it. Looks like any whitespace character other than actual space (0x20) between parameters should work. The line in dhcpd.conf should look like this:
option option-129 "NICOPT=duplex=2\nspeed=10";
For the NICs that didn't default to full-duplex, they will accept these module parameters and display that they're using full-duplex mode. Hooray! After that the system appears to freeze. Then I get a kernel panic. Back to square one.
Oh well, hope that "\n" thing can help someone else down the road. Guess, I'll keep working on my custom kernel and pass the boot parameters.
-kevin
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_____________________________________________________________________
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.freenode.net
