Earlier quoted context omitted.
This whole Lennart Poettering thing of naming and bundling otherwise completely independent pieces of software "systemd-${thing}" even when they are at best just sightly related to "things you might want managed for you in your computer" doesn't make a lot of sense, and doesn't help in his defense that "systemd is supposed to be modular". My guess is that if PulseAudio had came later, it would be called "systemd-audi…
Things which talk to the systemd dbus endpoints to add/stop/create/manipulate units are systemd-blahblah. This isn't that confusing. If it dynamically creates systemd units or sets their properties (systemd-homed, systemd-networkd, systemd-resolved) using the dbus endpoints, it's systemd-something. If it uses systemd libraries and lives in the systemd repo because it shares baseline docde, it's systemd-something. sys…
It is because systemd confuses what should be split concepts into one big overarching thing.
'org.freedesktop.systemd1' (the actual systemd init D-Bus interface) somehow is still implied that it is vital to the entire systemd-something ecosystem while it's not really.
A example being systemd-hostnamed and hostnamectl complaining that 'System has not been booted with systemd as init system (PID 1). Can't operate.' [1] while in fact they use 'org.freedesktop.hostname1.${something}' [2] and that is supposed to not be bolted with the entire rest of systemd besides using sd_bus.
[1] https://github.com/systemd/systemd/blob/93258c7d72fae23c9f81... [2] https://github.com/systemd/systemd/blob/93258c7d72fae23c9f81...