3 ms·
Note the irony of the situation. Writing an init.d script is actually really hard. A post attacking Systemd is actually a pretty good argument for using it.
by loftsy 12y ago
Note the irony of the situation. Writing an init.d script is actually really hard. A post attacking Systemd is actually a pretty good argument for using it.
- throwaway7767 12y agoThe common argument that systemd makes init jobs unportable sounds quite funny to me. I've used a lot of *NIX systems and init.d jobs are anything but portable, unless you fill them with OS-specific hacks.
- vertex-four 12y agoThe issue isn't that systemd makes init configurations unportable, it's that it makes programs unportable by tying them to systemd. What do we do 5 years down the line when we realise systemd was a bad idea and want to replace it with something else?
- Tuna-Fish 12y agoWe have that something else, or maybe another component of the system implement the systemd notify api?
- vertex-four 12y agosystemd has a vast number of APIs, especially inter-component ones, which are unstable and undocumented, meaning you'd have to replace the entire thing wholesale if you didn't want certain parts of it (especially its PID 0). The thread we're on is talking about a public API that's not documented sufficiently for alternative implementations to be created without reading its source code.
- mbq 12y agoAlso you can, in principle, write a robust, automatic converter of systemd units into init scripts.