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