I never had any purpose fopr it other than messing up great working systems.
It truly is superfluous garbage that truies to do too many things that are done better by separate daemons and programs.
AGAIN, I totally remove systemD and then it works stellar and all my problems disappear with cron not working, sound interference with jack and pulse, alsa that does horrible strange things. etc.
As soon as systemD is gone, these problems resolve...
It seems like no one here ever tried running MX without SyastemD !?
From the responses it sure seems so.
NO, I dont boot the systemD MX kernels. I never will make that mistake again.
The big problem is keeping systemD not to install itself by some dependency I overlooked.
At the moment I first have to grep apt through a pipe to detect systemD before I install anything, but somehow it still installs sometimes.
What will really help me is a means to completely ban systemD from installing through apt/dpkg.
That would be great, but I couldnt find a working solution.
Eadwine Rose wrote: ↑Wed Sep 18, 2019 4:05 am As long as you don't boot in systemd when you are in grub (you can select it in advanced) you are not using systemd.
It is there, yes, for those who DO need it.
It's like a browser and google.
You can open a browser and use google. Or not. If you don't want to use google simply don't go there. It will still BE there even if you don't go there, but it won't influence the browser.
If you absolutely want nothing to do with systemd, then you either remove all of it (although I don't know if it is possible to remove the whole thing *shrug*) or use a distro that is completely systemd free, like antiX.
