[solved] @#$%^*&! SystemD .. the snake strikes again

[zimbodel]

But please do not issue another complaint post if you find that despite your efforts, you still have to carry out another systemd-removal exercise in future when more updates drop.

I will post as much and what I want thank you very much, as long as I stay within forum rules.
That said, it is non of your business what I should or should not post.
I comply to the forum rules, thats it.

The thread is closed and solved unless you didnt notice and I thank again those users who made a positive contribution.
Move on.

[JayM]

But please do not issue another complaint post if you find that despite your efforts, you still have to carry out another systemd-removal exercise in future when more updates drop.

MX was made to boot into sysvinit by default, but not to be completely free of systemd-related packages by default. So you may have to expend the effort every once in a while to clear your garden. That is the potential consequence if you want to run MX your way.

And if you need to post another help request when (not if) your systems break again please do so in the MX Modified forum as your MX installations have clearly been modified from the original setup. Thanks.

[zimbodel]

It's refreshing though that you are one of the rare people who rant against systemd for practical reasons rather than philosophical ones.

Believe me, I have philosophically no problem using systemD if it actually worked for me I would adopt it.
I honestly encountered so many problems that resolved with systemD removed that it became a threat to me running my rackservers.
That is just what it is and what I have to deal with.

[zimbodel]

And if you need to post another help request when (not if) your systems break again please do so in the MX Modified forum as your MX installations have clearly been modified from the original setup. Thanks.

You are going in circles arn't you getting tired?
So to break this psychological loop you are in.
As I already clearly stated in the thread.
1) System ran spectacular, best I ever had for 6 months till systemD crept in again . So dont blame me for having turned MX into Antix. Rant at Antix then not me if you dont like that it works better for me.
2) SystemD will now be pinned as we discussed and I will alter apt with a wrapper to always grep for systemD so it never happens again.
3) Once MX18 gets too old and I am forced to upgrade, I will move to Antix, because that is actually what I made out of MX18 it seems. Until then, I will ask any question I want and post it where I feel it is relevant. Its none of your business as long as it complies to forum rules.
4) The Antix maintainer indicated that he will hard pin systemD, so the few users with positive contributions did help achieve something good.
5) I refuse to run an application that is completely sytemD dependent. I always find a substitute.

Thats it, MX18 runs like greased lightning again with 2.8ms latency and no xruns - freekin enormous.
I take my hat off to the MX developers.

At any rate, you are good people, but I urge you not to try to continue the senseless rants.
The thread is closed, Problem solved
Move On.

[JayM]

I made a polite request saying "please" and "thanks". There's no need for the snotty responses.

[zimbodel]

I made a polite request saying "please" and "thanks". There's no need for the snotty responses.

Lets agree to disagree,

Snotty, no. Accurate summary of the scope of the thread yes.
Thanking the maintainers and complimenting MX is a snotty remark ??

Break your psychological circle please
Lets Move on.
Thank you

[Adrian]

The thread is closed, Problem solved
Move On.

I don't think it works this way. You open a discussion you have to be open to hear what people think about it, you cannot shut them up when you don't like what they tell you. Especially if you kick and scream about something you should expect that people who disagree will respond to your posts.

Also, you claim you follow the forum rules, but you are a bit rude and I see you already have a warning. I think we are on 3 strikes = you are out, you are probably half-way towards the 2nd strike, so now it would probably be a good idea to tone the level of your rhetoric down and stop telling people who respond here what is their business or not.

Ultimately, f you hate systemd touching your system I would actually urge you to use another OS, MX is probably not for you, antiX will probably be a better choice, although I hate it to point you their direction, they've done only nice things for us...

[zimbodel]

The thread is closed, Problem solved
Move On.

Ultimately, f you hate systemd touching your system I would actually urge to use another OS, MX is probably not for you, antiX will probably be a better choice, although I hate it to point you their direction, they've done only nice things for us...

1) The entire Antix option has been discussed in detail in this thread. I even explained how I was invited to MX and why that was relevant. You seemingly missed that.
2) I donot HATE systemD (althought that is not what you imply), but it is catastrophic what it actually does to my system. I cannot just ignore the facts because some systemD attaboy Jedi waves fingers at me to adopt it regardless. I will use systemD if it works for me which it clearly doesnt as I verified empirically. If systemD worked I would be the first to use it. No hate, just factual experience that negates its use
As I said about five times during the life of this topic/thread, I will move to Antix once this systemD pinned MX18 becomes too old.
Regardless MX18 without systemD is the best Distro I ever had.-- no contest.

We already discussed all this.
Please take the time and read the thread before you repost old issues that has been solved and addressed.

[Adrian]

2) I donot HATE systemD (althought that is not what you imply), but it is catastrophic what it actually does to my system.

The only catastrophic thing happened when you mucked up with your system trying to remove packages. What does systemd do to your system if you leave in on? I'm interested to know because hey, I run MX on a multitude of systems and never had one issue... But again the use cases might be different, so I am interested to know what danger systemd poses on systems booted up with sysvinit. I'm open to learn new things.

[zimbodel]

2) I donot HATE systemD (althought that is not what you imply), but it is catastrophic what it actually does to my system.

The only catastrophic thing happened when you mucked up with your system trying to remove packages. What does systemd do to your system if you leave in on? I'm interested to know because hey, I run MX on a multitude of systems and never had one issue... But again the use cases might be different, so I am interested to know what danger systemd poses on systems booted up with sysvinit. I'm open to learn new things.

No, the catastrophic thing happened when systemD was installed as a dependency after I ran MX systemD free for 6 months, you are twisting my words.
Read the thread, I listed a couple, but there are hordes.
For starters sysvinit cron jobs dont run, rc.local dont run anymore (crucial to me) etc etc etc.. serious problems and that is just the tip of the iceberg.
alsa/jack gets borked solid until systemD is removed again and the list goes on.
I am really not going to repeat the thread to you.

It all resolves when I remove systemD for some reason.

I kindly ask that we move on.
The problem has been resolved with the help of positive contributions.
thanks