3 ms·

I believe there's a lot of worry about systemd because what Pottering is doing is relatively new. To grossly oversimplify; the ecosystem of inits among Linux di

by ForestC 12y ago

I believe there's a lot of worry about systemd because what Pottering is doing is relatively new. To grossly oversimplify; the ecosystem of inits among Linux distros looked something like "sysvinit -or- spin your own." So when systemd comes along and starts getting integrated into damn near everything, there's naturally some alarm. There have been endless flame wars about init systems for almost 25 years now. It's almost unfathomable that every major distro has managed accepted systemd with relatively little drama. I feel like "the marketing is too aggressive" or "they're being astroturfed" or "they're being forced" are all expected responses to what's going on.

digi_owl 12y ago
Well Fedora/RHEL and the systemd people have something of a relationship. I don't know the politics that went on with opensuse for it to be accepted there. Debian has had a big dustup going about it for some years. Ubuntu was pretty much waiting to see what Debian went with. Arch was pretty much a dictatorial decree (and one "respin" is not adopting systemd iirc). Gentoo is trying to stay init agnostic, and so has ended up forking udev to eudev (and Poettering has taken to making verbal pokes in their direction in systemd release announcements). Slackware is making the choice if it ever comes to a head, but then it has been using BSD init rather than sysv or upstart.