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 CRCulver on Sunday November 23 2014, @08:33AM

    by CRCulver (4390) on Sunday November 23 2014, @08:33AM (#119055) Homepage

    USB is still messy, and potentially another reason to reboot. The weirdest part is the way the Linux system may increment the IDs it assigns. Plug in and remove the same flash drive repeatedly, and it may be /dev/sdb the 1st time, /dev/sdc the 2nd time, /dev/sdd the 3rd time, and so on. The system doesn't always do that, but I've seen that behavior on numerous occasions. /dev/sdb is somehow not available ever to be used again, until the system is rebooted.

    Even if the /dev/sdX number is changing, the UUID of the USB device remains the same every time it is plugged in. For years now, fstab has allowed one to specify devices by UUID, not the /dev/ device, e.g. UUID=41c22818-fbad-4da6-8196-c816df0b7aa8 /disk2p2 ext3 defaults,errors=remount-ro 0 And in your shell scripts, it's easy to grab the UUIDs of the devices attached to your computer and do something with the corresponding device.

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

  • (Score: 0) by Anonymous Coward on Sunday November 23 2014, @09:05AM

    by Anonymous Coward on Sunday November 23 2014, @09:05AM (#119057)

    It is a bit boring to hunt for the partition's UUID, and too hard for most users.. but funnily you can use "gnome disk utility" to deal with that crap for you (even if you're not running Gnome 3).