[EMAIL PROTECTED] wrote:
> [...]
> Now I wanted to start testing how certain software behaves under LTSP. 
> So I installed three software packs (Stellarium, KStars and Celestia to 
> be precise) on the server. By mistake I did install them under the true 
> root '/' of the server as opposed to the "chrooted" '/opt/ltsp/i386' 
> branch. So one would expect that the thin clients would not "see" these 
> applications, right? (OR am I completely wrong when it comes to 
> understanding how LTSP is supposed to work?!)

Sorry, you're completely wrong. :) That is how LTSP is supposed to work. 
The chrooted file system under /opt/ltsp... is what runs on the clients, 
but it's basically just enough to manage the display and peripherals and 
give a remote login to the server. By default everything the user 
experiences is running on the server, not on the client.

> I had noticed before, that when I was logged in as one and the same user 
> on a thin client as well as on the server at the same time, I was for 
> instance unable to open Firefox on the client when I had it already 
> running on the server.

Exactly. Both instances of firefox are running on the server under the same 
user and attempting to use the same profile information.

It's possible to run some applications locally, or even to run everything 
locally, but then you're basically running fat, diskless clients which is 
not the default LTSP model.

I don't know about the nbd0-error, though.

-Steve

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_____________________________________________________________________
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

Reply via email to