> An additional DHCP server is just out of the question. Our clients will be > scattered across the network in different subnets, a dhcp server in every > location a client exist is not worth it. > Is this a limitation with the LTSP diskless client or are all diskless > clients the same?
It's a *feature* of diskless clients. You have to store the configuration SOMEWHERE, yes? You have to have an server SOMEWHERE for the thin client to use, yes? DHCP is lightweight way to get centrally managed config from a server - maybe the ltsp server, maybe not - to a client as it boots. If you have lots of subnets, use dhcp-relay so that you can get dhcp config across routers and have a single common dhcp configuration. The alternative is that you hard code all the details into the client somewhere, such as eprom. Bad idea - as soon as you move hardware from one subnet to another or change the server config, you have to reflash the client. Actually, the point is not whether a client is diskless, but whether it is *dataless* - with no system specific state. ------------------------------------------------------- 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
