Bug#727708: Vote sysvinit 4 jessie
On Mon, Feb 3, 2014 at 11:44 PM, Nikolaus Rath wrote:
> Michael Gilbert writes:
>> On Mon, Feb 3, 2014 at 1:42 PM, Steve Langasek wrote:
>>> So all deferring for another cycle does is leave Debian with annoying
>>> cumbersome init scripts and unsolvable race conditions for another cycle.
>> Which have already been solved for a long time now.
> No, they haven't. Try eg. various combinations of layering md-raid,
> cryptsetup, lvm and btrfs on top of each other. If you feel particularly
> adventurous, add some storage devices that take minutes to initialize or
> need a working network connection (disclaimer: I haven't personally
> tried the latter, but I'm pretty sure it's not going to make things work
For use cases like this where sysvinit is insufficient, the user can
use init-select or whatever to use a newer init that does handle this
Clearly using sysvinit as default does not preclude progress in these
areas. It just means that the user manually decides to use a
different init to "solve" these kinds of tricky problems.