SoylentNews is people
SoylentNews
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?
This discussion has been archived.
No new comments can be posted.
Suggestions for Init System Features?
|
Log In/Create an Account
| Top
| 50 comments
| Search Discussion
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Love is the delusion that one woman differs from another.
-- H. L. Mencken
(Score: 2) by urza9814 on Tuesday November 25 2014, @06:21PM
Hah, that reminds me of a minor gripe of my own with Systemd....the way it ends up handling encrypted disks *sucks so hard*. Took me a few boots to realize it was actually sitting there waiting for my password and hadn't just hung -- because it never displayed a password prompt! Or more accurately: it did, for about half a second, before it was overwritten by a message from a different process. I've got ten line shell scripts that handle I/O with parallel processes better than that!
No readable logs, no prompt or error message printed, it just sits there and hangs and you've gotta *guess* why...