To systemd or not systemd - Ever wonder about it?

[skidoo]

If you don't want to see systemd in the system,
you'll have to go back to Devuan and help them catch up.

That's not a helpful comment; it's an eyepoke, and... is it even (still) accurate?
For the Debian10 -based Devuan Beowolf release, is the Devuan collective still bent on performing the busywork of "weeding out" the harmless .service files provided by various upstream Debian packages?

[richb]

@skidoo, You need to add https://= to your link. Right now it goes to a page not found message.

[Richard]

@skidoo,
Apologies if my statement was inacurate.
I last tried ASCII 2 and there were some items missing from the repos.
I only thought too suggest that the poster could support them if he wanted to have systemd completely removed.
Perhaps antiX is closer to his needs?
I have not used Samba for years so you are right, I don't need to comment and neither have I tried Beowulf.

[JBoman]

I cannot say that I understand it or like or dislike it really but will briefly share a recent experience that has left me to use it at boot or to have no online sound after boot and no access to the pulse audio mixer as it will no longer start without systemd. I'm sure it started with the upgrade I did from mx17 to mx18 in which I made a terrible mistake of not checking my repo's list first and found after the fact that I had my Debian Testing and backport repo's open and settings set to upgrade to the highest available distro. The result was my borked sound. After reading something about pulse audio and systemd I decided to try booting with the systemd option in mx and to my surprize the sound issue resolved and I was able to start the pulse audio mixer again. I really prefer the way it was before I borked it as it takes forever to boot with the systemd option but I'm left with it till I figure out what exactly the problem is and I have not had time recently to weed it out.

[zimbodel]

The default may be sysvinit, but there shure is a hell of lot of interference from the systemd.
This is not the way Unix and by large Linux is supposed to work. systemd is a huge fork and all I can think of that it is a dual purpose fork.
The fork per se and the fork that is paid for to kill linux. There is just too much unaccounted for sudden aggresive evangelism for systemd @ Debian.
Looks like the process is funded.
All unneeded.

I am glad that Mx at least attempt to stick with Sysv,

Using systemd with MX can only happen by choice.
The default is sysvinit.

And, if you choose systemd then you are running an untested system, not MX18.
Devs may try to support you, but it is not the interest.
MX18 is designed to avoid systemd init.

Nope, out of the box install with hilarious behavior.

If you don't want to see systemd in the system,
you'll have to go back to Devuan to help them catch up, or BSD.

Exactly what I will do... indeed.!
I rather have installation problems in front of me from the package space than to have the OS byte me due to some savant at Debian's idea that systemd is a good idea.
Irresponsible software, but thanks at least for clearing up that Mx tries not to be dependent on it.

[zimbodel]

I am aware of the contents of that page as it is basically a lift of another systemd page.However it is Irrelevant as systemd uninstalled kills Mx, therefore must be in use or at least relied on.

Maybe you should read a bit about MX Linux on this question. Here's a good start:

https://mxlinux.org/wiki/system/systemd/

[Richard]

@zimbodel,
You misquoted me

Your comment in this line should be preceded by a close comment:

Nope, out of the box install with hilarious behavior.

And then an open comment afterwards to continue my comment.

I haven't had any hilarious behavior with MX since 02-April-2014 when first installed.

[Jerry3904]

I am aware of the contents of that page as it is basically a lift of another systemd page.However it is Irrelevant as systemd uninstalled kills Mx, therefore must be in use or at least relied on.

Maybe you should read a bit about MX Linux on this question. Here's a good start:

https://mxlinux.org/wiki/system/systemd/

Then it sounds to me like it's maybe time that you should look around for another distro that meets your criteria--not much use in complaining about MX when it makes perfectly clear what its policy is and why. Luckily, there are a lot of them out there...

[Adrian]

However it is Irrelevant as systemd uninstalled kills Mx

That's FALSE. Are you the same guy from Google Plus? I responded to a similar incorrect, possibly lying and trollish claim with this:

Also, regardless of your wrong reasoning your claim that you base your fallacy upon is simply incorrect, nothing happens if you remove systemd, some libs get installed some removed as one would expect, everything works just fine, Try it.. and stop lying. Nobody likes lying activists that have an ax to grind.

[Stevo]

A good article for those like me, that prefer Debian based systems but get caught up in Systemd problems.
Basically Debian Fork without systemd. That is the way I am going in the future with all my servers.

https://www.makeuseof.com/tag/debian-wi ... md-devuan/

And you'll find it even more impossible to run those outside programs that rely on systemd on Devuan than MX, since they removed the option.