Can you give a concrete example of a complicated task that's hard in systemd but easy in initd? I've never actually heard of one given although everyone complains about them.
From my standpoint, the average user doesn't interact with systemd or initd beyond spinning up services installed via the package manager. So this whole spat is isolated to power users and admins. The most complicated systems script I wrote myself was a mbsyc service on a timer.
I am the average user and not a power user. I prefer the initd system by far because it's basically impossible to break and very simple. I've run into systemd bugs too many times to ever use it again.
I'm sure you can break the init system if you tried...
Its just really telling to me that everyone who gives non-ideological complaints about systemd are never specific about the issue. Like are you sure it was a systems bug and not a bug with whatever service? Or maybe your weren't using it right?
Because systemd is basically everywhere in a Linux system, I suspect its falling victim to a simple pattern:
Something breaks somewhere in your system
Systemd is always involved in the system that broke because its involved in everything.
User concludes systemd is bad because it has a 100% correlation your systems bugs even if it wasnt the culrpit.
deleted by creator
It's easier than wrestling systemd u noob
deleted by creator
Synthesis: Gentoo with systemd. :comfy-cool:
yeah i fucking will idc if you're a cat
deleted by creator
Can you give a concrete example of a complicated task that's hard in systemd but easy in initd? I've never actually heard of one given although everyone complains about them.
From my standpoint, the average user doesn't interact with systemd or initd beyond spinning up services installed via the package manager. So this whole spat is isolated to power users and admins. The most complicated systems script I wrote myself was a mbsyc service on a timer.
I am the average user and not a power user. I prefer the initd system by far because it's basically impossible to break and very simple. I've run into systemd bugs too many times to ever use it again.
I'm sure you can break the init system if you tried...
Its just really telling to me that everyone who gives non-ideological complaints about systemd are never specific about the issue. Like are you sure it was a systems bug and not a bug with whatever service? Or maybe your weren't using it right?
Because systemd is basically everywhere in a Linux system, I suspect its falling victim to a simple pattern: