In reference to: https://lemmy.world/post/23862757
I use Void btw
Image text:
Most people rejected his message.
“Systemd is Satan’s creation! Pure Evil!”
They hated Talking Pig because He told them the truth.
In reference to: https://lemmy.world/post/23862757
I use Void btw
Image text:
Most people rejected his message.
“Systemd is Satan’s creation! Pure Evil!”
They hated Talking Pig because He told them the truth.
I don’t really get the hate for systemd. At least for someone who started really using Linux after it was introduced, it always seemed easier to control and manage than the init.d stuff.
Obviously it’s a hassle to migrate if you have a ton of legacy services, but it’s pretty nice.
It’s because you now need to do
systemctl restart sshdinstead of/etc/init.d/sshd restart, I see no other reason than having to learn new syntax.Arguably, init.d scripts were easier to understand, and systemd is a bit of a black box, it somehow works, but who knows where it writes logs or saves the process pid (it’s all in the documentation somewhere), with init.d script you can just open the script itself and look.
I think it’s okay to not 100% know every little detail of how a system works, as long as it’s possible to find out what you need when you need it.
This post was sponsord by the Backdoor Buddies
Don’t minimize those strengths. Init.d scripts are something you can figure out just knowing a bit of shell script, or historical knowledge from before there was an internet. For something I rarely use, why do I need to learn something more complex to do the same thing - I either haven’t been sold on all the new functionality they piled in or do not need it. After all these years crowing about the Unix/linux way being many independent flexible tools that can work together, why do we now have this all-in-one monstrosity that might as well have come directly from Microsoft?