I fully agree. I am a user with a bit of technical background, but not a lot of detailled knowledge about the inner workings of an operating system (i know boolean logic and basic programming structures - in Pascal lol - from the 90’s, what a transistor does and stuff, how to build my own PCs and handle filesystems and troubleshooting).
With init scripts, i hit a wall pretty fast.
With Systemd i know how to start, stop and configure services, and the suite built around it uses the same conventions everywhere, making the everyday life with Linux for someone like me so much easier and more transparent than ever before.
Have you considered that just “reaping old process IDs” wasn’t enough responsibility for an init daemon on a secure, robust system? That maybe it should be protecting other parts of the system and tracking the liveness of a desired service?
What is the benefit of specifically doing that in init?
If I see an argument like this then I can only assume the interlocutor doesn’t do software engineering.
Its more likely that the user simply has simple needs like running stuff at startup which any init system can do and doesn’t see as much benefits as poster.
Being able to assign a nameserver per interface with a domain wildcard is a fucking godsend. I use it every day with a hook script because my job uses some private domains but I don’t want to send my entire DNS history through the VPN. Now ~job.com goes to tun0 and that’s the end of it.
systemd-resolved is not perfect but with libnss’s overly rigid nature the only alternative for my use-case would be to recreate similar functionality to resolved with dnsmasq – which is just objectively worse especially when you want to use DHCP sometimes but not always. Why reinvent the wheel? resolved does its job and does it well. I had some issues with it a few years ago but have been using it for the past couple years without complaint.
Systemd has been a complete, utter, unmitigated success.
I fully agree. I am a user with a bit of technical background, but not a lot of detailled knowledge about the inner workings of an operating system (i know boolean logic and basic programming structures - in Pascal lol - from the 90’s, what a transistor does and stuff, how to build my own PCs and handle filesystems and troubleshooting).
With init scripts, i hit a wall pretty fast.
With Systemd i know how to start, stop and configure services, and the suite built around it uses the same conventions everywhere, making the everyday life with Linux for someone like me so much easier and more transparent than ever before.
What is the benefit of specifically doing that in init?
Its more likely that the user simply has simple needs like running stuff at startup which any init system can do and doesn’t see as much benefits as poster.
Also who loves systemd-resolved?
Being able to assign a nameserver per interface with a domain wildcard is a fucking godsend. I use it every day with a hook script because my job uses some private domains but I don’t want to send my entire DNS history through the VPN. Now
~job.comgoes totun0and that’s the end of it.systemd-resolved is not perfect but with libnss’s overly rigid nature the only alternative for my use-case would be to recreate similar functionality to resolved with dnsmasq – which is just objectively worse especially when you want to use DHCP sometimes but not always. Why reinvent the wheel? resolved does its job and does it well. I had some issues with it a few years ago but have been using it for the past couple years without complaint.
What’s the alternative?
I don’t think I will ever love anything DNS-related, but it’s still the best solution I’ve used for name resolution on a system with many interfaces.