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

[beardedragon]

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:~ $

bob@mx:~
$ cat /proc/1/comm
init

[timkb4cq]

Of even simpler

Code: Select all

ps 1

[beardedragon]

bob@mx:~
$ ps 1
PID TTY STAT TIME COMMAND
1 ? Ss 0:00 init [5]

[Richard]

$ inxi -Ix

That's a -capital i

[newguy]

As the upstream dev for sysvinit, it's nice to see lots of people still find it useful.

[Jerry3904]

And are grateful for your work!

[KBD]

Much appreciate your work newguy!

[Richard]

Thanks, "new guy".
Many of us are eternally grateful
for your maintenance of sysVinit.

[anticapitalista]

As the upstream dev for sysvinit, it's nice to see lots of people still find it useful.

More than useful IMO - keep up your great work on sysvinit

[baldyeti]

Thanks newguy. As an old-timer who's learned the runlevel-based startup system with SysVr3 i am glad the knowledge still applies. Systemd is not as aggravating as it once was, but MX sure demonstrates it does not boot any faster than its time-tested predecessor.