u/Naivemun

It's all in the title. Not asking if u can notice a difference tho if u do don't hesitate to say so. I'm asking from those who know, if they're literally identical or not and if not, how so?

Bonus: is there an upgrade in place tutorial that upgrades to the dual-init version of MX25?
Now that MX25 is dual-init, can u maintain a systemd or sysv only and not be harmed by upgrades? Like I guess the more general versoin of that question is, is the choice of init system like just 3 different separate ones , sysv, systemd, dual-init or is there wider ramifications of using one or another of them?

Beyond just being curious which is also why I wanted to go back to dual-init, I have no familiarity working with sysv, never noticed a difference in booting either when using MX21 or 23 except for a couple times when I needed systemd for something that had nothing to do with the OS itself. And then I learned how to do things with systemd so I probably don't have a use for dual-init since I created systemd services.

I followed the installs and removals on https://mxlinux.org/blog/mx-25-dual-init-setup/

I did the one coming from systemd only. The last install I get an error after the last step

sudo apt install sysvinit-init-diversity elogind-init-diversity

Errors were encountered while processing:
/tmp/apt-dpkg-install-Mp8rKw/5-initscripts-_3.14-4_all.deb
Error: Sub-process /usr/bin/dpkg returned error code (1)

I tried install initscripts on its own and get the same error.

My current MX25 install is from when it was beta iirc. I did the install in place from a snapshot of my running MX23.6 which I installed in a VM. The install in place was working. Just including that for history of the system. I wonder if that's the source. Either way I have no idea what this is about. And not urgent as this is a vm for testing the process. Still have my real MX23 install on my drive.

I tried it once and after this failure rebooted to see what would happen. It hung on the splash screen. I chrooted from a live session and did the revert to systemd only instructions and it booted. So currently I'm in my second trial. Got the same result, which is the resulting error I wrote above. Tho I started trying to fix it and probably muddied it now. To fix it I tried to do the revert to systemd only again, but I hadn't rebooted this time, I just, as soon as I got the error this time I did not reboot. I just started the steps for systemd only and it didn't work this time