MX Linux Forum

MX works absolutely great with the entire systemD removed.
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.

Rrrightio...

“Your worst dungeon might be the room with the most windows.”

JayM wrote: Wed Sep 18, 2019 5:10 am

Reasoning will never make a Man correct an ill Opinion, which by Reasoning he never acquired

-Jonathan Swift, from A Letter to a Young Gentleman, Lately Enter’d Into Holy Orders by a Person of Quality (1721)

I always run MX without systemD. I do not choose it in the boot menu. Therefore I am not running it under systemD.

zimbodel wrote: Wed Sep 18, 2019 5:34 am It seems like no one here ever tried running MX without SyastemD !?
From the responses it sure seems so.

Personally, I do so every single time I turn on my computer. I simply don't select the systemd init option in the grub boot menu. All of my PCs have been systemd-free since I began using MX.

Zimbodel

The thing that is happening here is that the post you made has lots of drama in it, as if systemd just ate your youngest child or something, which is what people are going to react to and the actual question you WANT to get an answer to gets overlooked. Think about it, asking plainly what you want to know without all the swearing and stuff around it will get you the answer you want much sooner.



I wager you really wanted to ask this:

"Can I completely get rid of systemd? I just don't want it installed on my system at all because I don't like it. How do I do that if possible?"


You would have gotten the exact answer you needed in no time, without the need to defend your decision.

zimbodel wrote: Wed Sep 18, 2019 5:37 am Rrrightio...

“Your worst dungeon might be the room with the most windows.”

Hey if Z wants to run systemd-free on the since of it not even installed that ok with me. But MX's repos (and debian's) are not set up for it. At least not without a lot of work. libpam-systemd dpeendecies are usually the culprit.

for those that want to run as systemd-free as possible, they should start with antix (or Devuan but I'm partial to antix)

Or one of these:
(from https://ungleich.ch/en-us/cms/blog/2019 ... t-systemd/)
Alpine Linux, Arctixlinux, Void, Slackware, Gentoo, Funtoo, GUIX, Linux From Scratch, Crux, PCLinuxOS (one of my old favorites.)

I think the answer to his question is:

if you want to keep running mx with no systemd-related packages at all, then you are making a choice to have to conduct occasional pruning and package removal whenever certain packages update, because of systemd-related dependencies.

That is inevitable because of the way mx and Debian is set up, as dolphin has explained.

There's no point complaining about your removal struggles, because it's going to keep happening once in a while.

The problem you have starts with blindly accepting updates without looking at what new dependencies they drag in.
If there is something you want to keep off your computer you must watch what is installed every time.