Ondrej Valousek wrote: > Hi Scott, > > Thanks for the answers, but I would say > 1. My experience says that clients with less that 512Mb RAM suffer when > used for heavy web browsing - firefox will eat majority of the memory > for pixmaps and if you do not have enough, well....
The vast majority of users of LTSP probably have below 128 megs of memory. All mine do. > 2. NFS (till v.3) is a stateless protocol - the server can not have any > stale mounts, only client can if it uses the share and the server goes > away, but hey, if you have 30 clients booting from your server, no > matter which protocol you use, you must be damn sure your server is rock > solid and will never go away.... If you're going to use NFS for localdev, your thin client will be the server, and the LTSP server will be the nfs client, so, as you point out, the client CAN have stale mounts, if the server goes away. People routinely just hit reset on their thin client if it gets hung up, or something. Hence, the reason for ltspfs. Scott -- Scott L. Balneaves | "Eternity is a very long time, Systems Department | especially towards the end." Legal Aid Manitoba | -- Woody Allen ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _____________________________________________________________________ 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
