I prefer this approach: >Systemd is included by default but not enabled. You can scan your MX system and discover files bearing "systemd" names, but those simp

I prefer this approach: >Systemd is included by default but not enabled. You can scan your MX system and discover files bearing "systemd" names, but those simply provide a compatibility hook/entrypoint when needed. >MX Linux uses systemd-shim, which emulates the systemd functions that are required to run the helpers without actually using the init service. This means that SvsVinit remains the default init yet MX Linux can use Debian packages that have systemd dependencies such as CUPS. This approach also allows the user to retain the ability to choose his/her preferred init. Source: https://mxlinux.org/about-us/ https://mxlinux.org/about-us/