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

[Buck Fankers]

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

You are flat rude to people that are helping you and helping others. (interestingly, I don't see you trying to help anyone, funny, how this goes...) You got all good suggestions, those that triggered you are very good suggestions, starting with please.... but you are acting like spoiled brat. It is going to be my way.... Since you are running MX differently that it is designed, you shouldn't be keep ranting for months when thinks breaks. It is your choice, to run it differently. But to me, you are coming across like: "I will rant, it is my right, until you guys change MX the way I want it!!!"

I hope good people here would just start ignoring you and stop helping you.

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.

...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.

...At any rate, you are good people, but I urge you not to try to continue the senseless rants.
Problem solved

Well and you are not good people and you are the one making rants starting early this year. And in many of your posts, there are some kind of insults, snotty responses... Frankly your posts are becoming tiresome.

[Adrian]

For starters sysvinit cron jobs dont run, rc.local dont run anymore etc etc etc.. serious problems.

Never had a problems with those. Cron jobs work just fine, rc.local runs just fine on my systems. You probably mucked up something else but that's just a guess.
Can you replicate the problem, show us how cron jobs/rc.local don't work on a freshly installed and updated MX?

[KoO]

@zimbodel
Maybe windows may solve your snake troubles. It is systemd free.

[JayM]

I would suggest something more robust like FreeBSD which is a true Unix and uses BSD Init, or perhaps Gentoo Linux minimal installation which is available with a choice of several init systems including SysV, rather than modifying and using any consumer-oriented desktop/laptop distro, whether MX, antiX or Devuan, on mission-critical servers. (I would actually choose something like Red Hat Enterprise, SuSE Enterprise or possibly CentOS if I were an IT manager, but these are all systemd distros which zimbodel objects to. In any event I certainly wouldn't run a desktop Linux distro on my servers. I also wouldn't allow updates on my production servers without first installing and testing them on an identical non-production server reserved for that purpose.)

[Buck Fankers]

@zimbodel
Maybe windows may solve your snake troubles.

+1 !!!
Windows indeed are systemd free

(for the record, the reason I come to MX is because it is not running on systemd. So, I too am avoiding systemd.
But I use MX as developers designed it. And I'm running antiX as developers designed it)

[Adrian]

(for the record, the reason I come to MX is because it is not running on systemd. So, I too am avoiding systemd.
But I use MX as developers designed it. And I'm running antiX as developers designed it)

Thanks, and properly reporting a problem might actually get it solved, instead of breaking your system and coming here kicking and screaming and telling developers to read 7 pages of rambling forum posts.

[zimbodel]

You can all continue your systemD party and rant and rave and insult as much as you want.
The thread has been solved if you look at the topic.

I am not taking part in your self-serving pie fight.

Enjoy
Cheers kids.

[Adrian]

You can all continue your systemD party and rant and rave and insult as much as you want.
The thread has been solved if you look at the topic.

I am not taking part in your pie fight.

Enjoy
Cheers kids.

Please ignore the kids, I would still like a clear bug report showing how to replicate the rc.local problem (let's take one problem at a time -- that's the first rule of bug reporting "nothing works" won't lead anywhere)

So here's how to report a problem:
1. let us know what version you use (MX18.3 for example, fully upgraded from regular repos)
2. let us know the version of the relevant package. In case of rc.local I guess the relevant packages would be sysvinit-core sysv-rc-conf, throw in systemd version but I doubt that's relevant)
3. tell us what line you added in /etc/rc.local, preferable something we can try too.
4. how exactly it fails, do you have a log or something that shows that?
5. can you add something else in /etc/rc.local that makes it work?

Then if we have enough information and if we can replicate the problem we might be able to zoom in and fix it, the rest is irrelevant banter...

[rasat]

Lets move on. MX runs well as non-systemd. How zimbodel did is a bit more work instead of using antix repo after removing all systemd based packages. Here is a sample respin.
https://forum.mxlinux.org/viewtopic.php?f=100&t=50981

@zimbodel, I suggest you make a snapshot, one respin and post in a new thread. It will be listed in MX Desktop Respins (list).
https://forum.mxlinux.org/viewtopic.php?f=100&t=48617

[zimbodel]

Please ignore the kids, I would still like a clear bug report showing how to replicate the rc.local problem (let's take one problem at a time -- that's the first rule of bug reporting "nothing works" won't lead anywhere)

So here's how to report a problem:
1. let us know what version you use (MX18.3 for example, fully upgraded from regular repos)
2. let us know the version of the relevant package. In case of rc.local I guess the relevant packages would be sysvinit-core sysv-rc-conf, throw in systemd version but I doubt that's relevant)
3. tell us what line you added in /etc/rc.local, preferable something we can try too.
4. how exactly it fails, do you have a log or something that shows that?
5. can you add something else in /etc/rc.local that makes it work?

Then if we have enough information and if we can replicate the problem we might be able to zoom in and fix it, the rest is irrelevant banter...

Give me the address to the bug tracker and I can deal with it there when I have time.
Although by doing so, I will be helping exactly those systemD attaboys who shout loudest right now, with systemD problems they will encounter in future.
See the conflict of interest ?
Just saying.
I will have to install MX on another partition and do it there.
It will be a cold day in hell before I install systemD on this server again.
It works perfectly now.

Thats all. I wont post in this thread anymore.
Thanks, bye.