You can also read The problem with the anti systemd attitude.
This is not just hatred towards systemd, it can do things very well, the direction it is going isn’t great.
You can also read The problem with the anti systemd attitude.
This is not just hatred towards systemd, it can do things very well, the direction it is going isn’t great.
While I get the sentiment, isn’t the fact that systemd is broken into various components and you can use or choose not to use each part of it still within the unix philosophy? You can use the init system without using the rest. It just integrates well with the other components.
That argument is addressed in the article. With few practical exceptions, systemd components expect you to be running the other systemd services. E.g. running systemd without journald is not a supported usecase.
Not supported doesn’t mean it won’t work
Fair enough, but there’s a reason no one runs almost any of the systemd services in isolation. There’s a big difference between “takes a bit of tinkering” and “need to maintain massive patch files to make journald independent of systemd”
Yeah that’s fair. I will say that I’ve used distro’s that used systemd and journald, but not resolved, networkd, etc and it worked fine.