[arch-general] On /etc/conf.d deprecation
lisaev at umail.iu.edu
Tue Dec 11 11:15:40 EST 2012
On Mon, 10 Dec 2012 20:27:38 +1100
Gaetan Bisson <bisson at archlinux.org> wrote:
> [2012-12-10 09:14:49 +0100] "Jérôme M. Berger":
> > Tom Gundersen wrote:
> > > However, options that are unrelated to the init-system should not be
> > > specified in ExecStart=, but should be configured in the applications
> > > own configuration file. It has nothing to do with systemd, so for
> > > systemd to just stupidly read it from one location and pass it on to
> > > the program without touching it seems wrong on a conceptual level.
> > >
> > Conceptually, you are right. Unfortunately not all applications
> > work that way today, so we need a way to pass the options to the
> > applications that don't.
> Tomorrow is the new today: "The first option should always be to
> petition upstream to add their own config files with the required
> options." (Tom, in the exact same message you were replying to)
> In other words /etc/conf.d/ is the last resort; if we keep relying on
> it, nothing clean will ever get done.
Do I understand correctly that the plan is to remove conf.d entries
together with corresponding rc.d scrtipts?
GnuPG key: 0x164B5A6D
Fingerprint: C0DF 20D0 C075 C3F1 E1BE 775A A7AE F6CB 164B 5A6D
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 490 bytes
Desc: not available
More information about the arch-general