7 ms·
Yes, systemd not being a monolith is a myth. You can forward logs to rsyslog or something, but you really can't disable systemd-journald. Technically you don't
by rnhmjoj 2mo ago
Yes, systemd not being a monolith is a myth.
You can forward logs to rsyslog or something, but you really can't disable systemd-journald. Technically you don't need to run systemd-boot, you can use grub or something else, but then bootctl and systemd kexec stop working. You don't need to run dbus, but if you don't several systemd features break, and it's not even documented what needs it. The list goes on and on.
Also, the fact that all components are in the same repository and need to be built together causes a lot of headaches with packaging due to dependency cycles (like, systemd -> cryptsetup -> lvm2 -> udev -> systemd).
- preg_match 2mo agoSystemd is literally not a monolith because it's not one big piece of software. It's a collection of software. For example, systemd-boot has basically nothing to do with systemd-init. Yes, some software is more tightly coupled than others, naturally. systemd-init and systemd-journald work tightly together because logging is a core requirement of any init system.
- rnhmjoj 2mo agoIt's literally not a monolith, but in practice it may well be, that was my point.
- preg_match 2mo agoI think that mostly comes down to distro choice and a lot of distros are more than okay with systemd soup. That’s the beauty of OSS, you can always choose not-Fedora ;)