Originally posted by interested
View Post
His strategy seems now to be make sysvinit the default init system in Linux, a solutions so technically bad, that it will be easy to persuade people afterwards, that multiple init system is mandatory for the Debian maintainers to maintain, among these Upstart. That way he can make Debian work towards Canonical goals.
Don Armstrong has just voted sysvinit as the primary init system (5 4 3 2 1), again putting systemd last, so they seem to have communicated beforehand.
Originally posted by GreatEmerald
View Post
And as far as I can tell, most people in the TC feel that staying with sysvinit is the worst thing that could happen. It's inadequate, and the later they start moving, the longer the transition period will go, and the longer people will have to suffer with init scripts. So delaying a decision and hoping it defaults to sysvinit staying reminds me of the US financial situation ? both sides can't agree with each other, and thus the outcome is what both sides wanted the least. And that's just bad for everyone involved.
About the finality of the decision, well, from what I gathered, most TC members have already decided and I don't see anything changing their decisions. So delaying the vote is rather pointless, as they already investigated the options well enough; it's not rushing, because this question has been raised a while ago. Plus this decision can be overruled in any case. But it will be a basis they can finally agree on, and thus move on to more productive things, like planning the actual transition.
Comment