Bug#940034: libelogind0: replacing a core system library and conflicting against the default init considered harmful

Mark Hindley mark at hindley.org.uk
Fri Sep 20 13:28:59 BST 2019


On Fri, Sep 20, 2019 at 01:29:43PM +0200, Laurent Bigonville wrote:
> Can't this be stubbed or mocked on the elogind side?

I presume you mean slices here? (I am not sure that slices are the only
difference in implementation, but let's ignore that for now).

To be honest, I am not sure. Possibly, but I have my doubts that upstream would
be interested in doing it: elogind has no use for them. Although they have
already been very accommodating by stubbing out all the APIs in libelogind0 to
be binary compatible with libsystemd0.

As I see it, if you want slices and all of the other features that systemd
provides, use systemd. If you want a slimmed down implementation of DBus login1
and sd-login(3) to use when systemd is not PID1, then elogind might be useful.


More information about the Debian-init-diversity mailing list