Comment by overfeed

> DNS: Can you from memory recite how name lookups work on Linux

Yes, I can, and I use systemd only because it's the default on debian, I have no reason to try devuan yet.

> ever written the old sysV ones from scratch?

Many, many times, and I was only an enthusiast/user, not a sysadmin.

> did you remember to make yours re-entrant?

Dealing with PID files was only mildly annoying. Init scripts were very boilerplate-y, so I wouldn't forget anything after my copy-paste-edit-delete unnecessary parts cycle. In a single afternoon, one could bash out an CLI init-script generator that uses jinja2 templates and interactively asking <10 questions about the service.

> Systemd is not perfect. But what it replaces was god-awful and far worse.

Init systems shouldn't have anything to do with managing container lifecycles beyond managing the container-runner service using the usual unix interface (signals). Call me a purist, but system services shouldn't be containerized.

An init system shouldn't be managing DNS or logging either, those should be standalone components. If they are problematic, there should be composable, domain-specific tools that solve them, instead of smooshing everything into systemd.

SystemD wasn't the only possible way to solve those logging, DNS, or security policy problems, and I'm glad other PID 1 projects that focus on being init systems are thriving.