Re: Xsession and LDM_DEFAULT_SESSION thoughts

hi,
Am Mittwoch, den 18.06.2008, 10:51 -0400 schrieb Jim McQuillan:
> As the author of the "Muekow" specification, I really don't remember 
> "eliminating lts.conf" as one of the goals.  I just re-read the spec and 
> it's not there.
> 
> I think it's great that for most people, an lts.conf file isn't needed, 
> but it doesn't necessarily mean that it's evil to have an lts.conf file 
> if you need it.  There's always gonna be somebody wanting to override 
> the default.
> 
> The lts.conf file wasn't intended to be used for "PER USER" settings. 
> It's supposed to be "PER WORKSTATION" settings.
> 
> In a world where all workstations are the same, and a user moves around 
> and they want their config to follow them, having a per user setting in 
> the user's home directory that gets read by the global Xsession script 
> makes sense.  But there's plenty of times that you have workstations 
> installed with a specific purpose, and no matter who logs in, you want 
> that workstation to behave a certain way.  Take a point-of-sale device 
> for example.  You always want that device to bring up the point-of-sale 
> software with no, (or minimal) window manager.  If you don't have a 
> lts.conf file, how can you specify how you want that particular terminal 
> to behave?
i dont oppose the usage of a setting or adding of a variable ... 
i oppose the fact that you will be forced to use lts.conf on one
distro ... it took us massive amounts of support work to make sure
people try without any lts.conf in the beginning and to make them
understand that its used to *override* autodetected default or *work
around bugs* and that the defaults should be tried first so that we can
eleminate the bugs in the packages instead of forcing people to edit
confg files where possible, while stll giving them the opportunity to
work around them or make adjustments to their needs.

having one single distro *forcing* the use of an lts.conf to set a
*default* value will mean that the urge and force of using lts.conf
returned and will retur into teh others as well at some point ... 
i would think all the work many of us have put in to lower support
stress and make autodetection and sane defaults work and be cautious to
not make "lts.conf by default" return in ltsp would be worthless ...

imho *forcing* the use of lts.conf (which this parameter does in all
cases, else your ltsp wont work on fedora as i understood) is the
totally wrong attempt and i still re state its a massive step backwards
in the improvements we have achieved ...

beyond that in the bug warren talks about per-user session settings
which i said before should be in the users home as you agreed on
above ...

ciao
	oli

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php

_____________________________________________________________________
Ltsp-developer mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-developer
For additional LTSP help,   try #ltsp channel on irc.freenode.net

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBIWSSYSsOT+6LQaTYRArMfAJ97m/7zCeywg1AZWOXR3vKYl6s1lACgjz+M
d3jIOONcJNbKfl8Y2kwn+jg=
=GRS1
-----END PGP SIGNATURE-----