I’m sad that you have to throw out all the init scripts you’ve written in 30 years.
Maybe stick with Slackware? I’m pretty sure you’ll fit in well there.
I never said init scripts (and more importantly, the init process) were the right answer. It doesn’t change the fact that systemd has some bad fundamental design and implementation decisions; and that any attempt to address them was met by Poettering saying essentially “this is the way I designed it, and therefore it’s right. You’re wrong.” He has no regards for standards, compatibility, or consistency.
It wasn’t even the first replacement for process management out there. Sun had SMF which was effective but flawed; and systemd duplicated almost every one of its flaws.
In other words, saying that init had to be replaced didn’t necessarily mean systemd; but that’s the world we have now.
I’m sad that you have to throw out all the init scripts you’ve written in 30 years.
Maybe stick with Slackware? I’m pretty sure you’ll fit in well there.
Aw gee, thanks!
I never said init scripts (and more importantly, the init process) were the right answer. It doesn’t change the fact that systemd has some bad fundamental design and implementation decisions; and that any attempt to address them was met by Poettering saying essentially “this is the way I designed it, and therefore it’s right. You’re wrong.” He has no regards for standards, compatibility, or consistency.
It wasn’t even the first replacement for process management out there. Sun had SMF which was effective but flawed; and systemd duplicated almost every one of its flaws.
In other words, saying that init had to be replaced didn’t necessarily mean systemd; but that’s the world we have now.