Booting MX-19 with runit

[Head_on_a_Stick]

Would it be possible for 18.3 , too ?

Ah, well, the thing is, erm, some absolute idiot[1] managed to get the runit-init package removed from Debian stretch just before it transferred to stable so that can't be done. Sorry.

[1] It was me

[Huckleberry Finn]

[1] It was me

[jeffreyC]

nm

[Huckleberry Finn]

Just a tiny feedback:

The only minor "issue" is that lightdm appears & disappears during shutdown / reboot (1-2 sec) and that prevents the shutdown be immediate. So, I thought something forces it to start at shutdown and opened sysv-rc-conf

Unchecked 3 & 4 and left only 2 & 5 checked (imitated 18.3 Sysv)
Unchecked also 5 and left only 2

On both cases the issue goes on, but everything's the same as with 2,3,4,5 checked (even with only runlevel 2 checked) with no problems: Login, Suspend with locking screen, lock-screen , shutdown, reboot ...

[Head_on_a_Stick]

The only minor "issue" is that lightdm appears & disappears during shutdown / reboot (1-2 sec) and that prevents the shutdown be immediate.

Yes, I noticed that but I don't know why it happens or how to fix it.

The only thing in the log is

Code: Select all

[DEBUG] Session pid=3015: Exited with return value 1

But I have no idea which process was assigned to ID 3015

[oops]

Just a tiny feedback:

The only minor "issue" is that lightdm appears & disappears during shutdown / reboot (1-2 sec) and that prevents the shutdown be immediate. So, I thought something forces it to start at shutdown and opened sysv-rc-conf...

... Is this new init process (runit, and OpenRC) will be the next one for MX (and antiX) , instead sysvinit ? ...
viewtopic.php?f=23&t=54716

[FraterLinux]

Now I tested runit. In MX-19 as it is, without a full support to OpenRC and eudev, elogind, libpam-elogind, etc... The feeling is that booting faster and the system is more responsive.

Tip:
Step 6 in http://smarden.org/runit/replaceinit.html#sysv
Break MX-19 (kernel panic)

The correct thing is:
Don't do anything! This step by step is obsolete due to the package runit-init

Code: Select all

/etc/runit/runsvdir/single/sulogin/run
/lib/runit/async-timeout
/lib/runit/run_sysv_scripts
/sbin/halt
/sbin/init
/sbin/poweroff
/sbin/reboot
/sbin/runit
/sbin/runlevel
/sbin/shutdown
/usr/share/doc/runit-init/buildinfo_i386.gz
/usr/share/doc/runit-init/changelog.Debian.gz
/usr/share/doc/runit-init/changelog.gz
/usr/share/doc/runit-init/copyright
/usr/share/man/man8/halt.8.gz
/usr/share/man/man8/init.8.gz
/usr/share/man/man8/poweroff.8.gz
/usr/share/man/man8/reboot.8.gz
/usr/share/man/man8/runit.8.gz
/usr/share/man/man8/runlevel.8.gz
/usr/share/man/man8/shutdown.8.gz

[aldQueiroz]

Hi, folks. I'm very interested on using runit in MX Linux, having in mind it provides faster boot times and does have a small memory foot-print, specially because the machines I'm using are old computers (> 5 years), with few available RAM (one of them is a system with CPU Single Core AMD Sempron LE-1250 (-UP-) speed: 2210 MHz... and only 3 GB of RAM, DDR2 !!); I've been following the developments of Void Linux, which uses runit as default, but I'm not confident yet to use that distro in a daily basis (XBPS package manager brings a steeper learning curve, and Void installer, without a GUI, can be tricky about how to configure partitions, I'm afraid... Not suitable for an "eternal Newby", like me...).

Then, I've got very excited on knowing that MX Linux does have runit package too! Could you report your findings about it? Besides faster boot times, does runit make the system really more responsive?
Thanks in advance!!

[andyprough]

Hi, folks. I'm very interested on using runit in MX Linux, having in mind it provides faster boot times and does have a small memory foot-print, specially because the machines I'm using are old computers (> 5 years), with few available RAM (one of them is a system with CPU Single Core AMD Sempron LE-1250 (-UP-) speed: 2210 MHz... and only 3 GB of RAM, DDR2 !!); I've been following the developments of Void Linux, which uses runit as default, but I'm not confident yet to use that distro in a daily basis (XBPS package manager brings a steeper learning curve, and Void installer, without a GUI, can be tricky about how to configure partitions, I'm afraid... Not suitable for an "eternal Newby", like me...).

Then, I've got very excited on knowing that MX Linux does have runit package too! Could you report your findings about it? Besides faster boot times, does runit make the system really more responsive?
Thanks in advance!!

If you have older machines with fewer resources, you should try antiX which already has runit installation ISO's on this page: https://mirrors.evowise.com/mxlinux-iso ... it-buster/

antiX is a sister distro to MX, and has many of the same tools that you have gotten used to using in MX, but it is more minimalist and works well on lower resourced and older equipment. The fact that antiX has and supports runit already should make this an easy decision.

[seaken64]

While I do like antiX very much and use it daily, it is not the same experience as MX. I would say that you can go ahead and try antiX but if you are not comfortable in antiX you're better off coming back to MX. 3GB on a 2.2Ghz processor is plenty of power for MX. You can modify MX to manipulate the memory use. And you can choose to use alternate software apps to make response better. Maybe runit will help, I don't know. All I know is that antiX is not the easiest to get used to if you are used to the MX GUI interface.

Here's a link to setting up MX-Fluxbox to use less memory. You can use similar techniques in XFCE. Or you could learn to use MX-Fluxbox, which might be a better choice for some than antiX.

viewtopic.php?f=143&t=56269

Seaken64