Live data from Hacker News

Debian committee members vote for systemd as init system

lists.debian.org

11–20 of 152 posts

Re: Debian committee members vote for systemd as init system

#11
post #10

Earlier quoted context omitted.

It's not quite as simple as that, because if all the remaining committee members vote F (further discussion) ahead of D (systemd) then D gets dropped before the casting vote stage (Debian constitution A.6.3). So far one of the four remaining committee members has done this, another is expected to, leaving the decisions of the remaining two to determine whether the vote completes or not.

Sorry for spreading misinformation, it seems that I got exited too soon. Still, I find somewhat unlikely that all the others member will vote F ahead of D. Are you referring to the "Technical Committee makes decisions only as last resort." paragraph of the Debian constitution? It's a bit cryptic for a non-native like me, so I'm not sure that I'm reading it right.

No, this is in the voting section A. It reads "Any (non-default) option which does not defeat the default option by its required majority ratio is dropped from consideration."

In this case F (further discussion) is the default option, and this stage in the voting process precedes the casting vote.

I too think it's unlikely that both Colin and Andi will block the decision, but we've known it's likely that systemd will win for some time now. It's still not yet official.

edit: actually there are other possible outcomes, see https://lists.debian.org/debian-ctte/2014/02/msg00309.html

Re: Debian committee members vote for systemd as init system

#14

What happened to the last vote? I saw some criticism that Ian jumped the gun by calling for votes when he did and putting two issues on at once but haven't read the archive in the meantime. Pretty unfortunate it took this long. Even as a casual observer it's looked like they'd eventually pick systemd a month ago. Hopefully this vote is the last one.

> What happened to the last vote?

Steve Langasek objected to the wording of the "tight coupling" and "loose coupling" options, and several others on the committee decided to vote Further Discussion first in response to that. It turns out that Steve (upstart maintainer) and Russ (primary systemd advocate on the committee) both agree fairly closely on that issue, in that the committee really shouldn't be ruling on that question in that way.

Re: Debian committee members vote for systemd as init system

#17
Can anyone give a quick rundown of the different init systems?

For the most part it can get confusing for a non day to day system administrator when I am trying to get a program to "run on boot". Between rc.local, init.d, run levels, etc. sometimes it is just frustrating.

Re: Debian committee members vote for systemd as init system

#18
post #15

Not a surprise, was there a compelling reason for upstart at all?

Upstart was created before systemd. Edit: Upstart was a great sysvinit replacement, at least during those years before systemd appeared.

That's not compelling.

Re: Debian committee members vote for systemd as init system

#20

Not a surprise, was there a compelling reason for upstart at all?

Not that I can think of. Upstart is slightly simpler than systemd to build configuration files for, but that's also because it doesn't have any advanced features like memory/processor/IO limits or the like. Additionally it doesn't even properly manage child processes... so you have to use wrappers to get Unicorn management working right in Upstart.
Post reply on HN