|
|
|
|
|
|
by concede_pluto
3247 days ago
|
|
|
The goal of an init system is to start daemons. It shouldn't have any opinions about which daemons you run, and it has no business doing random tampering like intercepting logins and DNS requests and renaming device nodes. Breaking "nohup foo & logout" is shockingly inappropriate; end users should never ever care how an admin may have booted the system much less have to know how to interact with it! |
|
|
I agree with the resolving DNS requests complaint, wasn't aware of that to be honest. That actually does seem somewhat odd.
However the other two make sense, systemd is used to init your system. Supporting login functionality as well as mounting and managing devices through udev (which supports renaming devices, as you said) doesn't seem too odd to me.
> Breaking "nohup foo & logout" is shockingly inappropriate;
Can you explain this to me? I never heard about this and my googlefu isn't returning anything fruitful.
> end users should never ever care how an admin may have booted the system much less have to know how to interact with it!
Unless you have an advanced user running `systemctl --user` or trying to check logs then I highly doubt the average user will need to know which init system you are using. For the most part, if you are just using your computer as a facebook/youtube/netflix machine then you probably don't care about the init system your computer is using (which I suspect describes 75% of users), assuming you even know what an init system is.