3 ms·
Ah, you're that CyberAx. Right. So, briefly: 1) That's a list of systemd features. Some of which are nice to have, but none of which are needed for the softwa
by simoncion 2y ago
Ah, you're that CyberAx. Right.
So, briefly:
1) That's a list of systemd features. Some of which are nice to have, but none of which are needed for the software I mentioned.
2) On-upgrade merge conflicts for entirely-unmodified-from-their-stock-settings system configuration files are why I gave up on Ubuntu. Systemd doesn't solve anything here.
3) Systemd doesn't handle BIND configuration... or any non-systemd application configuration. And most nontrivial init systems (with systemd as one notable exception) have facilities for printing info, warn, and error messages in service startup files rather than demanding that you pick through the application logs to find out why startup failed.