There is no question for the current MX release--It already runs systemd and sysVinit. The only reason there is a question at all is because our Debian Buster release for the future MX does not run the systemd shim. So it can only run one or the other init. If MX devs say they believe sysVinit will do the job and not cause a string of endless headaches for users--then we are done here :)gosia wrote: ↑Sun May 19, 2019 12:25 pm
That's right, in that sense it's not a representative survey. But it also shows that 89% of the users work with SysVInit without problems, whether this is a conscious decision or not. It works for them, even if they don't think about it or don't know anything about it. So why should you suddenly switch to systemd?
So far I have still managed without systemd. In case of emergency (which I can't imagine) the answer would be simple: I look for a new distro that runs without systemd. How do BSD or Devuan users live, to name just a few examples? But doesn't the question already show that systemd is the wrong direction? Apps or parts of the computer that suddenly depend on a single init system? That's not what I want.
many greetings gosia
The big but is that we are already starting to run into issues for users unless they boot into systemd on MX. No problem, they, me, just boots into systemd. The question is do we fully abandon systemd, or sysVinit, for the next big MX release?
The good news is they have some time to figure it out. I just want them to take everything into consideration and not get stuck on an pure ideology that we all adore, but leaves us with lots of grief in the end.
Most of us think systemd sucks and Debian should never have followed it down the rabbit hole. But we also need our computers to work correctly, now and in the future.