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: 1, Insightful) by Anonymous Coward on Sunday November 23 2014, @02:23PM

    by Anonymous Coward on Sunday November 23 2014, @02:23PM (#119105)

    The common problem I have with systemd is that when I mess something up, there is nothing to do to fix it. It just hangs forever waiting for the service to magically start working. It the old system, it logged a failure and tried to continue. Thus when an nfs share in the fstab doesn't mount, it still boots. With systemd, because sshd requires that fstab be done, it never loads sshd. Can't get in to fix it. Nope, you're done.

    Starting Score:    0  points
    Moderation   +1  
       Insightful=1, Total=1
    Extra 'Insightful' Modifier   0  
    Total Score:   1  

  • (Score: 2) by urza9814 on Tuesday November 25 2014, @06:21PM

    by urza9814 (3954) on Tuesday November 25 2014, @06:21PM (#119875) Journal

    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...