Hello, On Thu, Jan 29, 2009 at 01:56:44PM -0500, Dimitry Golubovsky wrote:
> Thanks for the reference. As I follow the "The boot process of a thin > client" chapter, I believe that my client goes up to item 8 (I see > reply from ipconfig). If NBD is used, which IP will the client's init > use to connect? It is desired to be the VM's IP, not the boot server > IP. Sorry, but I'm not sure anymore for now of what exactly you want to achieve... This afternoon, I've understand that you want an application server different from the boot server. (And I'm sure this setup works since I've tried myself.) But now, I begin to think that you could also well be after something different, like : - a boot server (providing the kernel and the initial ramdisk to the TCs) ; - a "root" server (providing root image through NBD) ; - an application server (providing the desktops and the applications to the TC's users - eventualy residing on the same machine as the root server). In others words, do you want to split the multiserver setup between machines *before* the point where it is habitualy done with LTSP, as pointed out by this afternoon suggested readings ? If you're after that septup, I'm not sure if it's possible... (At first sight, I see no means to give the TC's a root server different from the boot server.) But if I'm right OTOH, what could be the reasons to not follow the so-called Multiserver setup ? P.S. cc'ing to the list where your question will have more audience. A+ -- JFS. ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _____________________________________________________________________ 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
