>> Yes, >> We are using it and it works great. >Huh? How could you do that? I'm just curious as I was also thinking >about how could I possibly implement it just in case there would be an >existing Windows 2000 DHCP server. Would you mind sharing it to us your >experience and how did you do that here?
>Thanks. See this from Alex Perry's comment: >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 We also use Microsoft's NFS and TFTP servers. I called the NFS share /ltsp3000. Then I reference it as /ltsp3 in DHCP. I am glad that I was not the only one who saw the "000" appended on the end of the DHCP rootpath. Abraham Pearson Network Administrator www.atlantiscasino.com [EMAIL PROTECTED] (775) 825-4700 ext. 3671 --- MARVIN T. PASCUAL E-mail: mpascualATqsrDOTcomDOTph URL: http://www.qsr.com.ph Tel. No. +63 2 4554171 Mobile No. +63 919 3141254 Yahoo! Messenger ID: bintut Jabber ID: [EMAIL PROTECTED] GnuPG Key ID: 7269E38D GNU/Linux User No. 247127 ------------------------------------------------------- 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