Sitat "Jason A. Pattie" <[EMAIL PROTECTED]>:

> If you are really serious about having the thin clients boot off
> the 
> Internet, I would also recommend a VPN connection between the
> offices. 

This is the only way to set up the connection, it gives you 
encryption and solves a number of routing issues as well. I think 
some of the VPN implementations can do some compression as well, 
but I might mistaken.

>  However, if you want to maintain any semblance of performance, 
you
> will 
> need to modify the thin client environment from a "pure" NFS
> mounted 
> root filesystem scenario to a purely RAMdisk root filesystem.  
This
> 
> won't be that difficult, but the thin clients will possibly 
take a
> few 
> minutes to boot up depending on how much of the LTSP root
> filesystem you 
> package into the RAMdisk, especially if you want to run local 
> applications.  You will also only want to use VNC or lbxproxy or
> dxpc 
> protocols, instead of straight X protocol.  This is easily
> accomplished 
> by adding the vncviewer and a handful of other tools to the 
RAMdisk
> 
> image.  If you go with a RAMdisk image, you will need more 
memory
> in all 
> your thin clients.  Probably on the order of 96MB of RAM 
possibly
> 64MB 
> on the low end.  That should be enough space to allow X to run 
with
> a 
> VNC session and store the RAMdisk image completely in memory.  
You
> will 
> not be able to take advantage of network swap space, although 
you
> would 
> be able to take advantage of local swap space if the thin 
clients
> have 
> hard drives (which you probably don't want).

This will alleviate some of the bandwidth problems. Running some 
VNC variant departs quite a bit from straight LTSP, though. The 
guy asked about using LTSP, so I tried to answer him on that :-)

> 
> Another scenario would be to have a full workstation in the 
remote
> 
> office that all the thin clients boot from, but configure the
> lts.conf 
> and the full workstation to use the other office's resources as
> their 
> login and application servers.

Once I gave some thought to this idea as well, having a tiered 
LTSP-environment with "slave" servers, but I never tested it out. 
Anyone look at that?



--
Mvh Ragnar Wisløff
------------------
life is a reach. then you gybe.


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_____________________________________________________________________
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

Reply via email to