3 ms·

Usurped how? Who and how forced Debian and Arch to switch to systemd?

• kelnos 7y ago
  GNOME, essentially. If you want to run a fully-functioning GNOME on your distro, you have to be running systemd. Or have the time and patience to maintain a large patch set to work around the systemd dependencies.
  • theamk 7y ago
    This became this way only once systemd has won. At least during Debian systemd debate, both sysvinit and upstart could run Gnome just fine. (also, what were the alternatives? I don't run GNOME myself, but given what GNOME wants do to, it does need a solid session management. I have seen ConsoleKit, it was worse than systemd.)
    • dane-pgp 7y ago
      Debian's tech committee had their infamous vote about the default init system for Jessie in February 2014. Earlier, in October 2013, Josselin Mouette, a GNOME packager for Debian, wrote this: "GNOME in jessie will need systemd as the init system to work with all its features, just like it needs the network configuration to be handled by NetworkManager."
• sergeykish 7y ago
  You're missing a point. It's about feelings. Not my feelings at all. But empathy. Replacement for "no problem" should run without problems. python2 had no problems - there was a clear transition path: 1. "str" => b"str" 2. wait some time 3. "str" is u"str" ALSA had no problems - just wait till PulseAudio is ready. SysV, rc.d had no problems - just wait till systmed is ready. If SysV was as bad there would be same amount of outcry as with systmed Was it really necessary to make it painful? Who? Somehow systemd defenders has no empathy and Lennart Poettering is a prime example. No matter right them or wrong they are perceived as threat. Just be nice. It may hinder innovation but it helps community.