Quoting Alkis Georgopoulos <alk...@gmail.com>: > Στις 26/03/2012 12:54 μμ, ο/η Ben Green έγραψε: >> I don't think this setting -color depth- should be conditional, if >> there's going to be a default, it should be the same for all, >> otherwise it gets confusing. > > I strongly disagree; the default should be to try hard to work in all > cases. That's true in other lts.conf options already (e.g. NBD_SWAP was > always automatically enabled for clients with <=48 MB RAM), and in other > environments too (e.g. if gnome-shell doesn't work for you, you > automatically get gnome-fallback; if unity-3d doesn't, you get unity-2d; > if your screen is small enough, you get kde-plasma-netbook instead of > the standard one; etc etc).
The situations where having =auto as the default would cause problems are: 1. Where clients don't support 16-bit colour and are not using local apps. 2. Where clients don't support 32-bit colour but want to use local apps. Many clients don't support either 16-bit or 32-bit colour. Setting the default to be a fixed value (32 is the least problematic) is less confusing to the beginner who hasn't read all the documentation. Beginners will be asking "why doesn't my client start X now that I've disabled local apps?" or "why doesn't my client start X now I've enabled local apps?". "the default should be to try hard to work in all cases" - I absolutely agree, and setting a default to be 32-bit colour is the best setting for that, as that's the one that will get results for most clients. Cheers, == From Ben Green ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _____________________________________________________________________ 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
