It's getting stranger yet. I would suggest that everyone who uses a double or a triple boot setup might want to check their currently loaded setup via terminal. I went ahead and used grub-customizer to revert to the original settings without making any other changes. Just a simple reversal by clicking the button for that. Before saving the file, I could clearly see how MX Linux was now the top choice again, with MX Linux (systemd) being the second choice. Then I rebooted the machine.
At the grub screen, the order was now correct. MX Linux without systemd was the default and I went ahead and let it boot into MX Linux without pausing the process. 5 seconds is more than enough time to see which session was the highlighted session that the system was going to boot into. After logging back in, I went ahead and tried to use the app which won't work correctly without systemd, and yet again everything was fine with the app. Too good to be true? Of course! So I checked the system once again with ...
Code: Select all
ps -aux |grep systemd
(that's directly after rebooting, within 60 seconds of having logged in)
Grub Menu with Grub Customizer and Grub Menu during reboot, both had MX Linux *WITHOUT* systemd as the default. Yet here we are again with systemd. What's going on? Do I really need to re-install MX in order to get MX without systemd back, or is this something that we can correct manually within the terminal?