Booting MX-19 with runit

[asqwerth]

You've reminded me, now I recall also using the same vm method to configure a 32-bit version of mx on my pc to suit my father's usage, before snapshotting it to install in his old Acer netbook.

[aldQueiroz]

Ok... Well, I'm afraid the topic will become sort of a "post war" but, let me update (no pun intended!) you about my tests with antiX at the oldest desktop I'm currently using: I've logged the live session and installed antiX_runit at the HDD, but, eventually, I didn't find it better to use than MX Linux.. It boots faster, for sure, but iceWM is too much "frugal" for me! And, at same time, its launching menu has so many entries that it makes harder to find the relevant stuff! Things are organized in a different way of MX with XFCE, and I've got difficulty trying to find how to set Wifi! All these bring the so called learning curve to a steeper level, what I don't think it is suitable for newbies (I'm configuring that old machine not for me, but rather for an 8 years old nephew, accustomed only with Windows...). It is like antiX was a "race car": surely, it is fast, but it lacks many features needed in a daily commuting vehicle...

Further, one thing puzzled me:

Make sure you do a system upgrade either via the terminal, or synaptic or the antiX upgrader script/app under Menu > Applications > antiX.
Then, once you are up to date, use the package Installer app (just like you would/should) on MX Linux to install apps.
You have the option to install the very latest Libreoffice 7 version. Zoom is also installable via this app as is ibus/fcixt.
If you run antiX live with persistence (not dd as you did) then you can experiment on that stick with getting the system set up to how you want it, and then install to hard drive, Alternatively, just run permanently antiX live with persistence from the usb device.

https://antixlinux.com/the-most-extensi ... he-planet/

(Note the dates mentioned in that blog post. It shows how long antiX has been doing its live 'stuff' i.e. for over a decade now.)

I've tried to start the live session with persistence option, from liveUSB boot menu, but the boot failed; What did I wrong?...

On such circumstances, I'll shelve the idea of using antiX with the old machine. I need to keep it as user-friendly and intuitive as possible. So, a default MX Linux installation suits better (by now...).

[seaken64]

I agree that MX XFCE is easier to manage for most people than antiX and IceWM. But once the learning curve is over antiX remains the best choice for limited hardware. It is always the case that ease of use is going to take more resources.

Seaken64

[FraterLinux]

Will there be a package with scripts to optimize the use of Runit in MX???

Runit-MX-Scripts [runit init scripts for MX]

[aldQueiroz]

I've just found out that runit is already available at MX stable Repo! It's exciting! I tried once the liveUSB Antix with runit, and got impressed with how fast it boots (ok, Antix works with Fluxbox instead of Xfce, which is even lighter, what certainly contributes a lot to Antix's speed...). I've been willing to install runit at my own system, but (and there's always a "but"!) I don't know what to do after: I mean, what should I do to configure runit as Init system, replacing SysVInit? Or if such replacement would really increase boot speed and system general "responsiveness" (that last one is more important to me, by far!)...
The opinions and advices of who knows better MX Linux will be very appreciated! Thanks in advance!

[Jerry3904]

Did you already do a web search on "linux switch to runit"? Here's an example of what you might find helpful to get oriented:

http://kchard.github.io/runit-quickstart/

But I know nothing myself about this topic...

[FraterLinux]

I used runit by default on the MX-19. I followed the step by step:

Upgrading from MX-19 to MX-21 without reinstalling
https://mxlinux.org/wiki/upgrading-from ... nstalling/

After upgranding, randomly lightdm would not load.

I installed the packages on the MX-21:

orphan-sysvinit-scripts
sddm-modified-init
rtirq-init

Which of these packages can solve lightdm not loading?

[oops]

...
After upgranding, randomly lightdm would not load.
...

I had the same issue with ligtdm within antiX21, but only with the x32 version.
... I have not investigated, and I still with sysvinit for my x32 eepc.

Runit is better with slim or slimski.

[towwire]

I used runit by default on the MX-19. I followed the step by step:

Upgrading from MX-19 to MX-21 without reinstalling
https://mxlinux.org/wiki/upgrading-from ... nstalling/

After upgranding, randomly lightdm would not load.

I installed the packages on the MX-21:

orphan-sysvinit-scripts
sddm-modified-init
rtirq-init

Which of these packages can solve lightdm not loading?

Did you do this?

Although runit is well configured for Debian systems, MX Linux reserves runlevel 5 for the graphical login screen so we also need to change that with

Code: Select all

sudo sysv-rc-conf

Navigate to the LightDM line and enable the script for runlevels 2, 3 & 4 (as well as 5) then quit to save the change.

[FraterLinux]

I used runit by default on the MX-19. I followed the step by step:

Upgrading from MX-19 to MX-21 without reinstalling
https://mxlinux.org/wiki/upgrading-from ... nstalling/

After upgranding, randomly lightdm would not load.

I installed the packages on the MX-21:

orphan-sysvinit-scripts
sddm-modified-init
rtirq-init

Which of these packages can solve lightdm not loading?

Did you do this?

Although runit is well configured for Debian systems, MX Linux reserves runlevel 5 for the graphical login screen so we also need to change that with

Code: Select all

sudo sysv-rc-conf

Navigate to the LightDM line and enable the script for runlevels 2, 3 & 4 (as well as 5) then quit to save the change.

Yes... I did... But it still randomly doesn't load lightdm. I replaced it with slim.