Responses to Coming changes in impending MX 25 release.

[DeepDayze]

Depends on what you mean by "older". If it's older than anything that can run the current version of systemd, you may be better off with antiX as you will struggle even with a SysV MX.

Absolutely. Doesn't hurt to try the SysV MX and AntiX to see what works best for the use case.

[fehlix]

.... such as not being able to easily tell what kind of system is installed.

I'm using this in one of my conky's to always show me what type of boot-mode and systemd or sysvinit is in use:

Code: Select all

#system
${font Roboto-Light:bold:pixelsize=14}${offset 12}${color3}${no_update ${if_existing /sys/firmware/efi}UEFI${else}BIOS${endif}} \
${offset 2}${color4}\
${font RobotoMono-Light:bold:pixelsize=12}${no_update ${if_existing /run/systemd/system}systemd${else}SysVinit${endif}}

Note the test in "/run/systemd/system" is hardcoded test within systemd source itself, b/c it's needed also when init itself is based on systemd, which is possible, but debian fortunately is using busybox within the init not systemd.

[kd4e]

Isn't Devuan a systemd-free version of Debian?

I don't know if they have the personnel to manage troublesome drivers but, if so, that might resolve some hassles for sys-V users?