Comment by palata
9 days ago
> systemd does a lot more than just init. You can preach about whatever alternative inits all you like, but they don't do even 10% of what systemd does.
I didn't mean to preach about alternative inits.
My personal criticism of systemd is that it tries to take over everything, limiting the choice.
I want to have a choice, that's all. And systemd doesn't do anything to help there.
Can you give concrete examples?
systemd-resolved: can be disabled and replaced with your DNS resolver of choice
systemd-timesyncd: can be disabled and replaced with your NTP daemon of choice
systemd-networkd: can be disabled and replaced with your own networking scripts
Modularity would be to be able to use, say, systemd-logind or systemd-udev without using systemd as your init, as there is no tangible or important dependency on the use of systemd as init for those functions.
On a fully-systemd system you can opt out of systemd features. But you cannot opt in to systemd features on a non-systemd system.
> there is no tangible or important dependency on the use of systemd as init for those functions.
How do you catch device events on very early startup (e.g., between start of pid1 and when processes start to fire?) if the thing that manages the devices isn't integrated with pid1 at a deep level?
1 reply →
Thank you, that's what I was trying to say, but worded in a vastly superior way :-).
I am telling you that it is difficult to use systemd subcomponents without running all of systemd, and you give me example of running most of systemd and replacing a few subcomponents.
Can you run those 3 standalone?
>I am telling you that it is difficult to use systemd subcomponents without running all of systemd
Actually it's the first time you have stated that, but I'll bite.
How do you propose that would work, and why would you even want to do that? The entire point of having these modules is for them to plug in to core systemd, which enables a lot of magic that would otherwise require an amalgam of shitty shell scripts. If you don't want to use systemd, why not just use chronyd for NTP, dnsmasq for DNS, and so on? Your problem is completely imaginary.
2 replies →