Re: Removing libsystemd0 from a non-systemd system
- Date: Mon, 7 May 2018 06:15:18 +0000 (UTC)
- From: David Griffith <dave@xxxxxxx>
- Subject: Re: Removing libsystemd0 from a non-systemd system
On Sun, 6 May 2018, The Wanderer wrote:
On 2018-05-06 at 21:25, David Griffith wrote:
What's the point of allowing libsystemd0 to exist when systemd has
So that programs which interface with systemd can detect whether or not
systemd is present, and fall back to alternate code paths when it's not.
As I understand matters (without having actually dug into the code),
that detection code literally is what libsystemd0 *is*; when systemd is
present, it passes through function calls to be handled in appropriate
places, and when systemd is not present, it returns an appropriate
default or failure value.
I was under the impression that systemd-shim provided this functionality.
When I look at https://packages.debian.org/stretch/systemd-shim and
https://packages.debian.org/stretch/libsystemd0, their functions appear to
be identical except that the latter actually does talk to systemd if
systemd is present.
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
Q: What is the most annoying thing in e-mail?