on /etc/sysconfig

[Kay Sievers]

On Mon, Jul 18, 2011 at 21:59, Tom Lane <tgl at redhat.com> wrote:
> Lennart Poettering <mzerqung at 0pointer.de> writes:
>> On Mon, 18.07.11 15:34, Tom Lane (tgl at redhat.com) wrote:
>>> Well, if they didn't need fixed before, they'll certainly need fixed
>>> when you make them start keeping their configuration info someplace else
>>> than /etc/sysconfig.  This proposal sounds more like "wait, systemd has
>>> not yet broken everything in sight, how can we solve that problem?"
>>> than like something that will actually improve matters for anyone.
>
>> What does systemd break in this regard?
>
> There's a big difference between "a daemon might not need /etc/sysconfig
> anymore once it's been fully integrated into the systemd world" and
> "let's deprecate /etc/sysconfig and force packages to stop using it".
> Maybe you meant the first, but it's coming across as the second.

The 'force' seems to be in your head only. :)

We are just communicating that /etc/sysconfig should be phased out,
and no new work should be based on it. It should be seen as legacy.

Many basic configurations formerly in /etc/sysconfig we have already
move to proper /etc config files, and we might continue to do so.

/etc/sysconfig is a hack and a pretty bad idea in the first place.
Stuff should get native configurations as much as possible, not
distro-specific configs.

Some day /etc/sysconfig should be almost empty, and then we will see
what to do about it, but that might take a very long time, until then
there is no need to rush anything.

Kay