From: "Jeramy Eling" <[EMAIL PROTECTED]> > Has anyone had any luck in using a Windows 2000 DHCP Server with LTSP > instead of a Linux one? I am looking at Linux as a long term goal for > our network but for the moment I really need to stay with a Windows 2000 > DHCP Server.
Yeah, that's what we're using right now. We used to use Linux-based DHCP, but new MS clients (non-LTSP) were unhappy about it lacking MS extensions. There seems to be a bug in the MS DHCP server, in that a null character is appended to some of the parameters that get served out to its clients.
One workaround is to use a second DHCP server under Linux, configured to only accept clients that will become diskless boot and ignore the rest. Diskless boot clients ignore the MS server because it has no boot image. This is the recommended workaround, for a static and predictable network, but cannot be used if some clients need to boot both as MS and as LTSP.
The other workaround is to fixup the data after it is received by clients. Most of this can be done fairly trivially in the LTSP scripting stuff, but mounting the root filesystem itself occurs before that can be done. You either have to make a custom kernel for the fixup or use this hack:
The null is converted into "000" before the mount is attempted by Linux.
Modify the DHCP rootpath to "server:/ltsp/i386/" and create the link
ln -s /ltsp/i386 /ltsp/i386/000... hope that helps ...
------------------------------------------------------- This SF.Net email sponsored by: Parasoft Error proof Web apps, automate testing & more. Download & eval WebKing and get a free book. www.parasoft.com/bulletproofapps1 _____________________________________________________________________ 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
