On Mon, 03.11.14 09:48, Łukasz Stelmach ([email protected]) wrote: > It was <2014-11-02 nie 19:06>, when Lennart Poettering wrote: > > On Fri, 31.10.14 14:06, Łukasz Stelmach ([email protected]) wrote: > > > >> Hello. > >> > >> I am working to upgrade systemd in Tizen to v217 from v212. To verify > >> rpm packages we use rpmlint with some rules from opensuse[1]. For > >> whatever reason v217 package exceed allowed badness because it puts > >> config files (system.conf, journald.conf etc) in /etc/systemd. The check > >> [2] forbids putting anything in there and it seems to go along weel with > >> the "sateless system" goal of systemd. > >> > >> My question: is v217 ready to run without /etc/systemd/*.conf and read > >> them from /usr/lib/systemd wher I (vendor) can put properly tailored > >> files? > > > > Yes, /etc/systemd is unnecessary for booting. If you find any of our > > tools not working if /etc/systemd is removed it would be a bug. > > As I wrote in a message to Zbyszek, what if I want my distro defaults to > be different than those (no matter they are sane) of yours?
Well, if it's units and stuff they should live in /usr. If you want to configured things like system.conf or logind.conf or so, then I figure you currently would have to patch the systemd source code. Would be happy to take a patch that makes those cases check for a config file in /usr/lib as fallback though, to cover all bases. Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
