systemd config files???

[Marko Vojinovic]

On Tue, 22 Jul 2014 12:26:57 +0100
Balint Szigeti <balint.szgt at gmail.com> wrote:

> Why doesn't system respect FSH? What is its benefit?
[snip]
> I think, the config files should store in /etc instead of everywhere
> else. The chroot applications are exceptions. It cause we MUST
> mount /usr in / (root) partion.

The _New_Way_ of looking at config files is the following: the
*default*, rpm-provided config files should reside somewhere in /usr,
while the *customized*, manually tweaked (portions of) config files
should reside in /etc. This way there is a clear demarcation between
the package manager territory (/usr) and admin's territory (/etc).

In such a setup the yum update of a given package can update the default
configuration without destroying your customizations. It will also
make /etc much cleaner, easier to examine, fix, migrate, backup, and so
on.

There is a general push to make this happen for all apps, not just
systemd, and you should get used to seeing it all over the place.
I wouldn't be surprised if the near-future Fedora releases have clean
installs with an almost-empty /etc, waiting for you to put your
customizations in it. Personally, I think it's a good idea, and it will
certainly make my own machines much easier to maintain.

Whether this is FSH-compliant or not, I don't know. Some people say it
is, some people say it is not, most of the people don't really care. :-)

HTH, :-)
Marko