Hi folks,
We have a language school and two labs with about 20 places each. We
have been working with an LTSP 4.2 for quite some time now, and it's
time to think about upgrading our terminals to be able to use LTSP 5.
Before I start looking for hardware, I would like to know where you
would draw the line between a thin and a fat client.
On our current setup, I learned that transferring the graphics to the
terminals is a bottleneck. Another problem are programs like browsers
which tend to suck a lot of graphical data into the terminal's RAM
(large pictures for instance), so after some time the terminals start to
swap. You know what I mean... Another problem are terminals with no
modern graphics acceleration - like ours.
We would like to use a current KDE desktop and up-to-date browser like
Firefox, Wine etc. So I thought it might be better to let the terminals
each have their own complete OS booting and use a common pool of
individual and public defaults from the server. Maybe just using the
binaries from the individual harddiscs, but deviating all other
directories to those on the server.
But would I need LTSP for such a thing? Would that still be a fat
client, or: how do you define a fat client under LTSP 5? And would you
think thin clients would do? (Personally, I would prefer thin clients.)
Thanks for any opinion :)
Regards
Rolf
------------------------------------------------------------------------------
_____________________________________________________________________
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
