>usable in plenty of non-systemd environments That's really unfortunate naming then. Any systemd-foo that "works on it's own" is (rightly) assumed to be tight

>usable in plenty of non-systemd environments That's really unfortunate naming then. Any systemd-foo that "works on it's own" is (rightly) assumed to be tightly coupled to the rest of the systemd ecosystem.