> Maybe systemd (service management, logind, the DNS resolver, the loggig system, etc) will eventually be re-implemented in a way that does not have the irritat

> Maybe systemd (service management, logind, the DNS resolver, the loggig system, etc) will eventually be re-implemented in a way that does not have the irritating properties of the original systemd. One the topic or an eventual successor, one of the aspects of systemd is how intertwined all of it is. It’s really hard to replace just one part without either (1) replacing it with another which the same general design, or (2) remove all of systemd entirely. Take what op is taking about for example. Instead of relying on small, reusable components for sanboxing, it just re-implement all of it into the monolithic service_manager+service_supervisor_sandboxer+… You can’t even think of replacing the service supervisor or the logging subsystem without replacing all the other parts. Of course, I won’t deny that this design has its upsides: this monolithic approach ships a lot faster than trying to integrate different components to work together.