I am the maintainer of the Epoch Init System, a single threaded Linux init system with non-intrusiveness in mind, and I'm preparing to release 2.0. It's mostly a code cleanup release, but while I'm at it, I thought I'd ask the Soylent community what features they'd like to see. I'm open to all good ideas, but I'm wary of feature creep, so as a result, I won't consider the following:
* multithreaded/parallel services, because that goes against design goals of simplicity and harms customizability
* mounting support or networking support; it's an init system, use busybox if you need a mount command.
So what do soylentils want to see in the next release of the Epoch Init System?
(Score: 3, Interesting) by Wrong Turn Ahead on Sunday November 23 2014, @02:36AM
It seems that you are already doing so, however please continue to develop in a sensible manner that reflects the needs of the people who actually use your software. There has been a pattern of 'doacracy thinking' -- those who write the code know better than those who do not -- that has infected and divided some rather large communities.
Unfortunately, systemd has some heavy resources behind it and a strategy that includes getting core applications to build dependencies on it. Currently these minimal dependencies are things that can be worked around (sort of) but that will change with time. The issue isn't a lack of viable init systems to chose from, it's that systemd is the one with the most corporate muscle behind it. It matters not that it's the wrong init system for the users or that it flies in the face of the 'Linux way', so long as it benefits and furthers the agendas of a few key benefactors.
By the way, thank you for your contributions. They are appreciated...