11 ms·
The objections I tend to hear aren't so much about the parts of systemd listed in here, but about the way it seems to have grown to take over the rest of the sy
by ori_b 11y ago
The objections I tend to hear aren't so much about the parts of systemd listed in here, but about the way it seems to have grown to take over the rest of the system.
For example, it has its own syslog replacement, login manager, dbus implementation, network connection manager, dhcp server, udev implementation, boot manager, etc. There's talk of making it a dependency of Gnome, which would make Gnome and its components impossible to run on systems without systemd.
- fpoling 11y agoAdd to that list own DNS resolver and a time manager.
- sseagull 11y ago> which would make Gnome and its components impossible to run on systems without systemd. This is my main complaint. Most programmers know that coupling separate components is a bad idea[0]. After a while, the two components merge; they will begin to interface to lower and lower levels of each other, with the result being a giant mass of interdependent spaghetti code. Your choice of desktop manager should not, in any way, dictate which init system you use. And with system taking udev and everything else with it, it may be almost impossible to separate out systemd ever again. [0] I was going to link to the Stevens paper, but even wikipedia has an article about the problems of coupling: https://en.wikipedia.org/wiki/Coupling_(computer_programming) https://en.wikipedia.org/wiki/Coupling_(computer_programming...
- digi_owl 10y agoNifty. Seems to me that while unix (and thus Linux) have traditionally leaned towards data or stamp coupling, while systemd is over at common coupling.
- otterley 11y agoThose are all optional components, though. Why complain of their mere existence? If people want to use them, that's their business.
- digi_owl 11y agoThey are optional from the pov of pid1 yes, but may well not be from the pov of something user facing. And thus you have systemd taking over pid1 because something user facing depends on something that depends on systemd-pid1. Consider this, upower now is pretty much a wrapper of logind.