On Thu, Nov 1, 2012 at 5:21 AM, Kay Sievers <k...@vrfy.org> wrote: > On Wed, Oct 31, 2012 at 9:04 PM, Kok, Auke-jan H > <auke-jan.h....@intel.com> wrote: >> On Wed, Oct 31, 2012 at 11:30 AM, Zbigniew Jędrzejewski-Szmek > >>> Does this mean that there'll be a file in /etc/systemd/ always? >>> This goes against the practice of moving default configuration >>> to /usr. >> >> no, the defaults are perfectly fine and ordinary users should have no >> need to modify any of the settings. We can opt to not install the >> config file by default as well. > > It would be fine to install a file with the defaults (ideally > everything commented out) in /etc. The goal is that there is no > difference in behaviour if this config file is not around.
That's how it currently works... >>> Also, if the binary is supposed to be invoked directly, >>> then is should go into /usr/bin, not /usr/libexec. >> >> /usr/lib/systemd - not /usr/libexec. And systemd-readahead also has a >> "analyze" option that is for interactive use, so that folder should >> really be fine. > > We should be in general very careful with installing things in > /usr/bin. We make a kind of promise by doing that. Only things that we > consider ABI, and things we intend to keep stable should be in > /usr/bin, if in doubt, /usr/lib/systemd/ is in most cases the better > choice. I have a secondary motivation to put it in /usr/lib/systemd - there are other bootchart implementations around and I'd like to draw a clear line in between the systemd version and the others. Putting it as "systemd-bootchart" in /usr/lib/systemd accomplishes that. Auke _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
