Stories
Slash Boxes
Comments

SoylentNews is people

Suggestions for Init System Features?

posted by LaminatorX on Sunday November 23 2014, @01:39AM   Printer-friendly
from the first-do-no-harm dept.

Subsentient writes:

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
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: 2) by tynin on Sunday November 23 2014, @03:54AM

    by tynin (2013) on Sunday November 23 2014, @03:54AM (#119025) Journal

    Equally, you don't want the system to be done mounting a filesystem when the filesystem is remote and the network hasn't finished coming up. Parallelism in an init has its use cases, but it doesn't fit all cases.

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  
    Total Score:   2  

  • (Score: 3, Insightful) by tibman on Sunday November 23 2014, @06:41AM

    by tibman (134) Subscriber Badge on Sunday November 23 2014, @06:41AM (#119047)

    Init systems usually have a dependency chain to resolve that issue.

    --
    SN won't survive on lurkers alone. Write comments.

  • (Score: 2) by sjames on Sunday November 23 2014, @02:24PM

    by sjames (2882) on Sunday November 23 2014, @02:24PM (#119107) Journal

    A simple solution is to have a barrier at each priority transition. It isn't perfect, but may be a good compromise between slow serialized init and complex dependency driven start.