> Granted, they seem to be going about the task a little differently, but is > that necessarily a bad thing? I've been using LTSP since version 3. It's > gone through its share of changes through the years, too. > It's hard to say: Disadvantages of LTSP: - single logon server, single point of failure. - if you use Windows terminal server, you need to pay extra CALs - no resource management in Linux (i.e. single user/application can eat your whole memory/CPU and there is nothing/very little you can do about)
Disadvantages of RH Virtualization for Desktops: - more resource hungry as you are running more instances of the same OS - more complicated management (you need to populate image changes somehow) To me, the decision is quite clear - if you intend to use Linux terminal server, I would probably go for LTSP. For Windows, it is probably better go the RedHat way. Also, LTSP/Linux kernel developers should pay more attention to the resource control as that's the biggest gap I am seeing at the moment.... Ondrej ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _____________________________________________________________________ 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
