modern features and OpenRC (was: Re: Survey answers part 3: systemd is not portable and what this means for our ports)
Dear all,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> writes:
> Says the guy who posted this to back up his chain of arguments:
>
>> http://wiki.gentoo.org/wiki/Talk:Comparison_of_init_systems
Excuse me for hijacking this reply.
On the wiki page.
I revised it into present form last year, after a *shadow* survey (using
each to see its interface and features, by performing service
add/remove/start/stop) of various init systems, including sysvinit +
sysv-rc, Upstart, systemd, OpenRC, SMF and launchd. It is biased, not
mature and started from the biased
http://0pointer.de/blog/projects/why.html to counter-argue Lennart's
points.
For the '??' in Device-based Activation, sorry, at that time I didn't
know what it was so just copy-n-pasted.
Because of the bias, It was soon moved into "Talk" for archieving
purpose. For a objective version have a look at the main page,
http://wiki.gentoo.org/wiki/Comparison_of_init_systems.
For the features that people care most in OpenRC (openrc herd, correct
me if I am wrong):
a. process supervising:
no.
But OpenRC can be integrated with runit (unofficial yet), my personal
effort is targeting to use s6[1] together with OpenRC.
b. event-driven, mostly hotplug events
OpenRC provides a HOTPLUG virtual runlevel. to keep features minimal,
it relies on udev to trigger it. An example of iPhone hotplugging[2].
I forgot if inotify could fit into this. If you need more info I can
dig it out.
c. socket activation
no.
At present no solution yet.
Cheers,
Benda
1. http://www.skarnet.org/software/s6/why.html
2. http://wiki.gentoo.org/wiki/Iphone_USB_Tethering#udev_trigger
Reply to: