What init system do you use on MX, the default (sysVinit) or systemd?

[esbeeb]

I'm actually really grateful that MX Linux provides that tool. I appreciate their views on avoiding systemd, and I'm OK with them having a preference that they make the default, that of sysVinit, but then they let me have an "out" if I needed it. This shows respect that they are not out to shove their views down my throat. That means a lot.

Sincerely thanks, MX Linux devs, for not being unreasonable idealists. You came up with a way to accommodate the views on both sides of the camp.

[mr_dashi]

I voted default. I've only been using Linux for 4 years and pretty much only "know" systemd. It works for my modest means, but I am very sympathetic to the idea of "init freedom" and those who question systemd's trajectory. As it stands right now, I don't need systemd - all my tools work perfectly. I roll vanilla Arch with systemd on my desktop, but MX/sysVinit on other installs. I really hope MX/anitX can continue to provide an alternative init to systemd. When WW3 comes around, I'm camping up with those that know how to hunt, fish, canoe, and pitch a tent. I predict a huge init fork down the road. We're in good hands.

[jsomonte]

Systemd creates more problems than solutions. Systemd will not provide any improvement to MX Linux.

[Otter]

Don't care about systemd for now.

I use MX Linux because it doesn't use systemd and I guess there are many others like me.

[beardedragon]

To find out which init you are using in MX run the following in terminal:
sudo dpkg -S /sbin/init

[Head_on_a_Stick]

sudo dpkg -S /sbin/init

That won't work with MX because the systemd-sysv package isn't installed, a kernel parameter is used to boot with systemd instead of sysvinit.

This will work though:

Code: Select all

cat /proc/1/comm

For example, I've just installed MX and I'm running systemd as PID1 so I see

Code: Select all

empty@mx:~ $ dpkg -S /sbin/init
sysvinit-core: /sbin/init
empty@mx:~ $ cat /proc/1/comm
systemd
empty@mx:~ $

[Adrian]

Yeah, or "ps -p1" if you see "init" in output it's sysvinit, if you see "systemd" guess what...

[beardedragon]

@Head_on_a_Stick
That won't work with MX because the systemd-sysv package isn't installed, a kernel parameter is used to boot with systemd instead of sysvinit.


bob@mx:~
$ sudo dpkg -S /sbin/init
[sudo] password for bob:
sysvinit-core: /sbin/init

[Head_on_a_Stick]

Code: Select all

bob@mx:~
$ sudo dpkg -S /sbin/init
[sudo] password for bob: 
sysvinit-core: /sbin/init

Try that again after rebooting and selecting the systemd option from MX's "Advanced Options" GRUB sub-menu, it will return the same output even when systemd is running as init.

And that dpkg command will work as your normal user btw.

@all: apologies for the noise.

[beardedragon]

Code: Select all

bob@mx:~
$ sudo dpkg -S /sbin/init
[sudo] password for bob: 
sysvinit-core: /sbin/init

Try that again after rebooting and selecting the systemd option from MX's "Advanced Options" GRUB sub-menu, it will return the same output even when systemd is running as init.

And that dpkg command will work as your normal user btw.

@all: apologies for the noise.

I don't want systemd, thanks anyway.