Manually managing mac and IP addresses for dozens or hundreds of ltsp clients seems a nightmare when dhcpd can dynamically assign IP's and update dns with the ..... hmmmmm..... there is no place to store a hostname for the thin client, is there? You also have the issue of different kernels that may be needed for different hardware.
But IF you had all the thinclient hardware able to boot the same kernel image and dhcpd could derive a hostname for the client (like ltsp-a-b-c-d) and push that to ddns, would it work? Is there some show stopper I should know about before jumping into this (possible) black hole? TIA, Toby Kraft __________________________________________________________________ Your favorite stores, helpful shopping tools and great gift ideas. Experience the convenience of buying online with Shop@Netscape! http://shopnow.netscape.com/ Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.com/ ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _____________________________________________________________________ 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
