When comparing Upstart vs Dinit, the Slant community recommends Dinit for most people. In the question“What are the best Linux init systems?” Dinit is ranked 3rd while Upstart is ranked 6th. The most important reason people chose Dinit is:
Written with a focus on being secure and correct.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Event based startup was fantastic.
Since it is event based, it was simple to have interdependent services emit status messages each other. Service start ordering and shutdown was easily managed in one conf file.
The "lazy" start of systemd is BS and is a mess to debug . service unit files have no clue what another service state is. The maintainers add arbitrary timers that add more complexity and more init hangs. The systemd documentation is poor. When a service fails to start (or stop) systemd follows the Microsoft model of not telling the reason why.
Pro Simple .conf file in /etc/init
Pro Robust
Written with a focus on being secure and correct.
Pro Compact
With a reasonable feature set, but not at the cost of high complexity.
Pro Well documented
Check the extensive manual pages!
• dinit(8) manpage
Pro Portable
Written in portable C++ code; compiles and runs on a variety of Unix-likes (Linux, various BSDs).
Pro Free and Open Source
Distributed under the Apache License version 2.0.
Pro Fast startup times
Boots very fast.
Cons
Con Ubuntu abandoned it
The original developers (Canonical) seem to have abandoned this project. At least they're no longer using it in Ubuntu.
Con It was just sysvinit or systemd in disguise
It really just offered a barely more intuitive way to create init scripts for the actual init system running behind upstart.
Con Still new
It happens to freeze pretty often (tested on 2 different servers, 1 desktop and 2 laptops).
