On Thu, Feb 4, 2010 at 8:29 PM, Joachim Ott <[email protected]>wrote:

> On 4 February 2010 18:20, Tom Hacohen <[email protected]> wrote:
> > On Wed, Feb 3, 2010 at 6:15 PM, Joachim Ott <[email protected]>
> > wrote:
> >>
> >> On 3 February 2010 16:22, Thomas Zimmermann <[email protected]> wrote:
> >> > Am Mittwoch 03 Februar 2010 16:05:12 schrieb Joachim Ott:
> >> >> Very much wanted for fso config files. The last line in a file (e.g.
> >> >> fsodeviced.conf) should be
> >> >>
> >> >> include ~/.config/fsodeviced.conf (or $HOME/.config/fsodeviced.conf)
> >> >>
> >> >> 1. No action is made when the config file does not exist.
> >> >>
> >> >> 2. A warning is written to *syslog* (not somewhere else) when a
> >> >> section or a parameter doesn't exist (anymore)
> >> >>
> >> >> 3. Any parameter in the "local" conf overrides the value from the
> >> >> "system"
> >> >>  conf.
> >> >>
> >> >> Benefits:
> >> >>
> >> >> - no need to modify the system config anymore, no questions from opkg
> >> >>  needed
> >> >>
> >> >> - no longer headaches after an opkg upgrade
> >> >>
> >> >> Downside:
> >> >>
> >> >> - it has to be implemented
> >> >>
> >> >> Any thoughts from you?
> >> >
> >> > It was implemented in a better way 4 days ago:
> >> >
> >> >
> http://git.freesmartphone.org/?p=cornucopia.git;a=commit;h=509f3a582d34d312abbd2a1097bde85068d69be4
> >>
> >> When $HOME/.foo.conf was read, will
> >> /etc/freesmartphone/conf/<machine>/foo.conf be read also? The other
> >> way round (first the system values, then the local values overriding
> >> them) would make me happy already. Otherwise, how do I get aware of
> >> new (or obsolete) sections or parameters?
> >> _______________________________________________
> >
> > I don't think it'll ever happen, as this is a terribly bead idea, system
> > daemons should not rely on user configs.
>
> Well, I don't like the values for dim, idle_dim etc in the standard
> fsodeviced.conf so I have to change them in the file, which is of
> course overwritten with the next upgrade. When I try to change the
> values with shr-settings, my changes are not written back. Even worse,
> when I leave shr-settings and I start it over, the old values come up
> again. Tho I'm always working as root on the FR, a normal user should
> be able to have his personal values for this dim stuff.
>

That may be true, but you still shouldn't be able to control all of
fsodeviced. Maybe there's a need for a way to control it per user, I don't
know.

-- 
Tom.
_______________________________________________
Shr-User mailing list
[email protected]
http://lists.shr-project.org/mailman/listinfo/shr-user

Reply via email to