[systemd-devel] [PATCH 2/2] sysusers.d: split files to cope with split packages.
Gustavo Sverzut Barbieri
gustavo.barbieri at intel.com
Tue Sep 30 10:44:14 PDT 2014
On Tue, Sep 30, 2014 at 04:26:31AM +0200, Zbigniew Jędrzejewski-Szmek wrote:
> On Thu, Sep 25, 2014 at 06:12:51PM -0300, Gustavo Sverzut Barbieri wrote:
> > move each user/group creation to a file that represents its own split
> > package, so it's possible to ship them in separate.
> > ---
> > Makefile.am | 33 +++++++++++++++++++++++++++++++--
> > sysusers.d/systemd-journal-remote.conf | 9 +++++++++
> > sysusers.d/systemd-journal-upload.conf | 8 ++++++++
> > sysusers.d/systemd-journald.conf | 8 ++++++++
> > sysusers.d/systemd-kdbus.conf | 8 ++++++++
> > sysusers.d/systemd-networkd.conf | 8 ++++++++
> > sysusers.d/systemd-remote.conf | 10 ----------
> > sysusers.d/systemd-resolved.conf | 8 ++++++++
> > sysusers.d/systemd-timesyncd.conf | 8 ++++++++
> > sysusers.d/systemd.conf | 12 ------------
> > 10 files changed, 88 insertions(+), 24 deletions(-)
> > create mode 100644 sysusers.d/systemd-journal-remote.conf
> > create mode 100644 sysusers.d/systemd-journal-upload.conf
> > create mode 100644 sysusers.d/systemd-journald.conf
> > create mode 100644 sysusers.d/systemd-kdbus.conf
> > create mode 100644 sysusers.d/systemd-networkd.conf
> > delete mode 100644 sysusers.d/systemd-remote.conf
> > create mode 100644 sysusers.d/systemd-resolved.conf
> > create mode 100644 sysusers.d/systemd-timesyncd.conf
> > delete mode 100644 sysusers.d/systemd.conf
> Hm, kdbus is either compiled in, or not, so splitting out configuration doesn't seem
> useful.
I did this because I was trying to make bus-proxyd optional, however
it does not work as stdio-bridge uses that. so yes we can leave the
kdbus part in without worries.
> systemd-timesyncd is ~400kb. Other binaries aren't too big
> either. Splitting everything up complicated things, and I'm not convinced
> that this is a useful change.
indeed they are not big per se, but see my other email about tmpfiles,
they contribute to a misinterpretation of systemd. since they are
optional I want to make that clear and help the user to choose.
I do have a complete set of packages for yocto that generates that
nicely and the final system size difference is huge: 7.5 to 30Mb
(whole system, not just systemd, but the dependencies, etc -- in
contrast sysvinit + busybox is 6.5Mb).
as I wrote in the other email, I'll make sure that some packages are
highly recommended (ie: journal, udev, sysctl...), but forcing
everyone to ship a ntp client (timesyncd) is asking for trouble when
people analyze systemd x options.
systemd is great and it avoid people doing mistakes where it provides
elegant solutions, but we need to get it in :-)
--
Gustavo Sverzut Barbieri
Intel Open source Technology Center
More information about the systemd-devel
mailing list