Debian TC vote on init system coupling

Posted Feb 24, 2014 11:45 UTC (Mon) by anselm (subscriber, #2796)
In reply to: Debian TC vote on init system coupling by nim-nim
Parent article: Debian TC vote on init system coupling

This state of affairs will presumably profit from the enhanced exposure that systemd will get in Debian. This will lead to systemd being exercised in more real-world setups, and more problems being detected and ironed out.

And it's not as if System-V init didn't have any problems at all; the problem there is that nobody is in charge, and that every distribution needs to fend for itself (and the setup itself is pretty brittle, especially in corner cases).

With systemd, at least there is a cross-distribution development community which will help ensure that every distribution profits from enhancements made under the auspices of another distribution. This works for the Linux kernel, so why shouldn't it work in this case? What's not to like?

Debian TC vote on init system coupling

Posted Feb 24, 2014 12:58 UTC (Mon) by vonbrand (subscriber, #4458) [Link] (1 responses)

Don't try to paint Debian as a trailblazer in exercising systemd in new scenarios, that train left some three years back.

Debian TC vote on init system coupling

Posted Feb 24, 2014 13:05 UTC (Mon) by anselm (subscriber, #2796) [Link]

True, but chances are that, with systemd deployed on more Debian machines, somewhere something will break, and be fixed, and systemd (and Debian) will be the better for that. This is just how things work with free software.

People often accuse the systemd developers of »not taking Debian's needs into account«. Regardless of whether this is in fact true or not, the obvious way to fix this is to become more active in systemd development on Debian's behalf. The more systemd is used within Debian, the more enhancements and bug fixes will be contributed to systemd from Debian, and the more influence Debian will have on systemd development. Again, this is just how things work with free software.