On Fri, 2014-02-28 at 19:32 -0600, William Hubbs wrote: > On Fri, Feb 28, 2014 at 07:09:08PM -0600, Steev Klimaszewski wrote: > > I'm not exactly a fan of systemd, though I know it has some uses, and > > I'm still curious as to why it installs/stores *configuration* data > > in /lib - if only from an upgrade point of view, we back up /etc, we > > back up /home - now we need to back up /lib, /usr/lib, /var, or whatever > > some random upstream decides is a good place to store configuration > > information!? > > Consider it default configuration information. Basically what they are > doing is, say you have a default udev rules file in > /lib/udev/rules.d/10-foobar.rules, which is provided by some package. > > Now you want to override that default. > > You override in /etc/udev/rules.d/10-foobar.rules instead of editing the > provided file. > > William
Default configuration information makes somewhat more sense - it makes a bit more sense to store it where it has historically been, which was /usr/share, I think anyway, rather than having to dig around the system in arbitrary directories to find out what the default configurations are in the first place, but who am I to judge? :) The way that it's been presented throughout this thread made it seem like the network configurations when using e.g. networkd were being stored in there. As someone who uses the bare minimum of systemd (only to test Gnome 3.10 on ARM), it made no sense to me why it kept being brought up that systemd kept network configuration there, I wasn't familiar and that's why my initial response a while back asked if we were really storing configuration information there. So thank you for clarifying.
