Persisting driver configuration

[Francesco Pretto]

Matthew Garrett <mjg59 <at> srcf.ucam.org> writes:
>
> The correct behaviour is probably a 
> runtime session daemon that handles the configuration (including at a 
> display manager) and can handle switches between different consoles with 
> different input preferences.
> 

No. Adding another default loaded daemon to a standard desktop machine is
NOT the way to go, especially if it isn't system wide for all
configurations storing needs. Still, I'm against the idea of a conf
daemon: Windows Registry proved long time ago that a daemon is not needed
at all. Only gconf and few others disagree but, citing libelektra guys [1],
"GConf is a daemon, so if one day it will be system global, it will
represent a single point of failure". Just 5 minutes ago, my gconf daemon
crashed (wasn't the first time): had to restart gnome.

Until there isn't a sane, system wide, standardized way to persist
configurations, just choose the less-bad way to go. And NO: gconf is not
the less-bad, considering  that even gnome guys are planning to replace
it [2].

Greetings,
Francesco

[1] http://elektra.g4ii.com/GConf
[2] http://live.gnome.org/dconf