There are legitimate reasons to criticise systemd and I’m completely certain that they will never be posted in this community. I swear if I have to read some stupid comment about the unix philosphy from someone who has no idea what systemd is, which parts are optional or what init looked like before this stupid twenty year long debate…
It’s about how one project is trying to do more, and more, and more, and more, and trying to entrench itself as deeply as possible so you can’t just use something else if you don’t like it.
(Oh, and this new political stuff? Now there’s a concrete reason to use something else.)
The problem with systemd isn’t technical, it’s political, IMO. Oh I mean sure there’s plenty of technical reasons to hate it too (binary logs anyone?), but that’s not the main problem.
systemd would actually be pretty nice, if it stuck to just being a service manager. Unfortunately, yeah.
Oh, and everyone ALWAYS goes “oh but the only other option is a hodgepodge of scripts! you don’t want a hodgepodge of scripts! bow down and accept systemd”. Ever seen, like, any of the other init systems that are out there? We’re running OpenRC right now and it’s pretty fantastic. (Granted, sysv scripts are still the lowest common denominator, but there are other options. OpenRC’s got declarative service files too, and they’re actually way nicer than systemd’s service files when you need to break out of the declarative format and do a little script stuff. systemd made us stuff everything into one line.)
And before you dismiss me as Just Some Oldhead™, we actually moved to Linux (from Mac) well AFTER systemd was already entrenched. So this isn’t a “you hate change” thing.
There are legitimate reasons to criticise systemd and I’m completely certain that they will never be posted in this community. I swear if I have to read some stupid comment about the unix philosphy from someone who has no idea what systemd is, which parts are optional or what init looked like before this stupid twenty year long debate…
Why though, I sure love having a load of script files in a folder doing the boot things.
I can easily add another.
Why system not boot, help
/s
It’s not about “the unix philosophy”.
It’s about how one project is trying to do more, and more, and more, and more, and trying to entrench itself as deeply as possible so you can’t just use something else if you don’t like it.
(Oh, and this new political stuff? Now there’s a concrete reason to use something else.)
The problem with systemd isn’t technical, it’s political, IMO. Oh I mean sure there’s plenty of technical reasons to hate it too (binary logs anyone?), but that’s not the main problem.
systemd would actually be pretty nice, if it stuck to just being a service manager. Unfortunately, yeah.
Oh, and everyone ALWAYS goes “oh but the only other option is a hodgepodge of scripts! you don’t want a hodgepodge of scripts! bow down and accept systemd”. Ever seen, like, any of the other init systems that are out there? We’re running OpenRC right now and it’s pretty fantastic. (Granted, sysv scripts are still the lowest common denominator, but there are other options. OpenRC’s got declarative service files too, and they’re actually way nicer than systemd’s service files when you need to break out of the declarative format and do a little script stuff. systemd made us stuff everything into one line.)
And before you dismiss me as Just Some Oldhead™, we actually moved to Linux (from Mac) well AFTER systemd was already entrenched. So this isn’t a “you hate change” thing.
– Frost