Actually the job scheduler is one aspect, complimentary to the object-oriented resource management which I made quite clear was the main point.<p>Regarding file ownership, not necessarily. If you run it as a session-based init, they&#x27;d be owned by the user it serves as an agent to. (see dirs: <a href="http:&#x2F;&#x2F;www.freedesktop.org&#x2F;software&#x2F;systemd&#x2F;man&#x2F;systemd.unit.html" rel="nofollow">http:&#x2F;&#x2F;www.freedesktop.org&#x2F;software&#x2F;systemd&#x2F;man&#x2F;systemd.unit...</a>)<p>Upstart and launchd do not have the same issues. Upstart doesn&#x27;t have dependencies, but named preconditions and postconditions. launchd has neither that nor dependencies. They have many problems of their own, but different ones.<p>My point regarding laziness v eagerness is the way systemd implements multi-paradigm introduces undesirable externalities from both approaches, as I said: &quot;In systemd, one must endure both the non-determinism from aggressive parallelism via dependency information, the object network needing the transaction and job metaphors, all while having its lazy features be thoroughly restricted to its internal Manager and not a flexible toolkit such as UCSPI.&quot;<p>I&#x27;d assume the limited use of C&#x2F;R to simply cut down initialization times <i>is</i> feasible: <a href="http:&#x2F;&#x2F;criu.org&#x2F;Usage_scenarios#Slow-boot_services_speed_up" rel="nofollow">http:&#x2F;&#x2F;criu.org&#x2F;Usage_scenarios#Slow-boot_services_speed_up</a><p>Running shell scripts doesn&#x27;t mean much when the underlying system has a large surface and ill-defined module boundaries. A plugin system most certainly does not have to be complicated: look at finit and initng for examples.<p>What about journald did you not understand? You lose control over the separate stages of collection, rotation and processing. Particularly having custom postprocessing is important for interoperability with foreign services that might expect certain format constraints. Having the logs be per-service instead of globally snarfed is also saner.<p>Yes, I did go overboard on the reservations. It&#x27;s a flame war topic, so I felt it necessary as a precautionary measure.