So the old init.d system was better? Come on people, let’s stop infighting. I have zero preference on init systems. You know why? Because they’re just plumbing. Stop this nonsense. Do I click on an init system? Do I use the init system to check my email? Or play games? No. I know poettering can be controversial, but let’s just move on. Run freebsd if you’re so butt hurt.
So much more than an init system though, which I think is why people don’t like it. Personally, the only annoyance I have is I preferred log files over journald.
So the old init.d system was better? Come on people, let’s stop infighting. I have zero preference on init systems. You know why? Because they’re just plumbing. Stop this nonsense. Do I click on an init system? Do I use the init system to check my email? Or play games? No. I know poettering can be controversial, but let’s just move on. Run freebsd if you’re so butt hurt.
Yeah, on a desktop I don’t really mind whatever*. On a server however, I think systemd is great and I wouldn’t want to miss it anymore.
* except Debian’s frankenstein systemd + sysvinit combination. Burn it
So much more than an init system though, which I think is why people don’t like it. Personally, the only annoyance I have is I preferred log files over journald.
Its becoming an behemoth and has security disadvantages in theory
It is much more secure since it supports proper sandboxing and least privilege
Curiously, the cream of the crop in terms of security-focused Linux (i.e. Kicksecure and secureblue) leverage systemd to their benefit.
because those are our only two options…
I hate this argument so much, because it’s just a fallacy.
There are (and have been) more solid init systems.