SoylentNews

Suggestions for Init System Features?

posted by LaminatorX on Sunday November 23 2014, @01:39AM   
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?

• Re:Features? Fewer please. Re:Features? Fewer please. (Score: 3) by Subsentient on Sunday November 23 2014, @04:46AM

  by Subsentient (1111) on Sunday November 23 2014, @04:46AM (#119036) Homepage Journal

  You can still do that. Epoch uses IPC to transfer its process state information to the updated copy. 'epoch reexec' is all that's needed to upgrade all the way from 1.0 to the current master. And it's a *full* update.

  --
  "It is no measure of health to be well adjusted to a profoundly sick society." -Jiddu Krishnamurti

  Parent

  Starting Score:	1		point
  Moderation		+1
  Underrated=1, Total=1
  Karma-Bonus Modifier		+1
  Total Score:		3

• Re:Features? Fewer please. (Score: 2) by sjames on Sunday November 23 2014, @02:16PM

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

  Surely the state should be serialized to disk in case the new instance crashes.

  Parent