5 ms·

I wonder why Debian didn't go with OpenRC (https://en.wikipedia.org/wiki/OpenRC https://en.wikipedia.org/wiki/OpenRC) as it is compatible with both Linux and *B

I wonder why Debian didn't go with OpenRC (https://en.wikipedia.org/wiki/OpenRC https://en.wikipedia.org/wiki/OpenRC) as it is compatible with both Linux and *BSD, which also offers 'Process segregation through cgroups'.

kaeso 13y ago
The OpenRC port effort is currently ongoing and been sponsored by this year GSoC: http://wiki.debian.org/SummerOfCode2013/StudentApplications/LeiWang http://wiki.debian.org/SummerOfCode2013/StudentApplications/...
bkor 13y ago
Change happens by people doing work. There are at least 3 people actively working on systemd support. Meaning: they help out other packagers, file bugs, look at bugreports, coordinate with upstream, etc. For OpenRC, there is just one person advocating it. There is a summer of code thing, but seems not much work is done. Furthermore, OpenRC seems nice, but parallel starting of services is actually experimental/buggy (just ask one of the OpenRC maintainers!). So although you can have a similar boottime, one init system (systemd) will be running in a supported configuration, the other (OpenRC) in something that is known to have issues. That all said, I don't think Debian really makes decisions. What is being proposed is maintaining two. Aside from above, there is also the practical bit in that systemd provides something to replace the unmaintained and deprecated ConsoleKit with. This bit can be used on another init system (Canonical is using or will use it on Upstart), but at one point seems easier to rely on the existing systemd supporters in Debian to get things working correctly.
- synchronise 13y ago
  Surely the Debian Foundation can see that an init project that can support more than one kernel/OS, pretty much as Debian does with Hurd and kFreeBSD, would be a better platform to support through the long term.

5 ms·

I wonder why Debian didn't go with OpenRC (https://en.wikipedia.org/wiki/OpenRC https://en.wikipedia.org/wiki/OpenRC) as it is compatible with both Linux and *B

by synchronise 13y ago

kaeso 13y ago
The OpenRC port effort is currently ongoing and been sponsored by this year GSoC: http://wiki.debian.org/SummerOfCode2013/StudentApplications/LeiWang http://wiki.debian.org/SummerOfCode2013/StudentApplications/...
bkor 13y ago
Change happens by people doing work. There are at least 3 people actively working on systemd support. Meaning: they help out other packagers, file bugs, look at bugreports, coordinate with upstream, etc. For OpenRC, there is just one person advocating it. There is a summer of code thing, but seems not much work is done. Furthermore, OpenRC seems nice, but parallel starting of services is actually experimental/buggy (just ask one of the OpenRC maintainers!). So although you can have a similar boottime, one init system (systemd) will be running in a supported configuration, the other (OpenRC) in something that is known to have issues. That all said, I don't think Debian really makes decisions. What is being proposed is maintaining two. Aside from above, there is also the practical bit in that systemd provides something to replace the unmaintained and deprecated ConsoleKit with. This bit can be used on another init system (Canonical is using or will use it on Upstart), but at one point seems easier to rely on the existing systemd supporters in Debian to get things working correctly.
- synchronise 13y ago
  Surely the Debian Foundation can see that an init project that can support more than one kernel/OS, pretty much as Debian does with Hurd and kFreeBSD, would be a better platform to support through the long term.