MX Linux Forum

Posted: **Fri Dec 06, 2019 1:39 pm**

runit is a cross-platform Unix init scheme with service supervision, a replacement for sysvinit, and other init schemes.

http://smarden.org/runit/

Unlike sysvinit, runit offers true process supervision and unlike systemd it has a smaller codebase (and hence potentially fewer bugs). For comparison: runit-init is 9KiB, sysvinit is 52KiB and systemd is 1.5MiB.

To change from sysvinit to runit use these commands and reboot:

Code: Select all

sudo apt update && sudo apt install runit{,-init}

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.

See this page for a guide to migrating from sysvinit service files to runit scripts (step 5, purely optional): http://smarden.org/runit/replaceinit.html#sysv

In case of problems, boot with systemd (using the Advanced Options boot sub-menu) and re-install the sysvinit-core package to return to the stock configuration.

Preliminary ISO images are available from this post: viewtopic.php?p=545422#p545422

Posted: **Fri Dec 06, 2019 4:33 pm**

Thanks.

Tried this in VBox with antiX-19 (net install) - seems to be working well. Testing some more.

Posted: **Fri Dec 06, 2019 4:44 pm**

Just to add that boot time to a fluxbox 'desktop' with slim login manager (auto-login) takes <6 secs! Usually it is 10 secs in these tests with sysvinit.

Posted: **Fri Dec 06, 2019 4:47 pm**

Thanks,

I will try too, into a small partition.

Posted: **Fri Dec 06, 2019 4:51 pm**

I was trying on 18.3 without success and was wondering if MX Team would consider Runit.. Will try on 19 :)

Edit: Wooooooooohooooooooooow

Writing on MX 19 Runit "Baremetal" - 32bit :D

Yes, started manually with startx,

First Feedback: Conky shows exactly same numbers of Ram and Cpu as it was with sysvinit 2.96

Will now do the automation for startx.

(Meanwhile, maybe you edit the command and add: sudo apt update ; at the beginning :) )

Can give more feedback if asked or observed anything interesting.

Posted: **Fri Dec 06, 2019 5:14 pm**

I just made antiX-19.1-full-runit iso and will play with this to see how well (or not) persistence/snapshot/frugal works

Posted: **Fri Dec 06, 2019 5:19 pm**

The only negative observation: There was a screen glitching with Thunar only (1.8.9) on 4.9.200 kernel (and previously 4.9.193) and that became increased so much. ( Graphics: Intel Mobile 915GM/GMS/910GML Express Graphics, driver i915)

Other observations:

pm-suspend works perfectly as it was with sysvinit
the default suspend xfce4..logout also works but screen doesn't get locked (also screen-lock doesn't work, as it seems there's something with light-dm or lightlocker as mentioned)

Posted: **Fri Dec 06, 2019 5:29 pm**

anticapitalista wrote: ↑Fri Dec 06, 2019 4:44 pm Just to add that boot time to a fluxbox 'desktop' with slim login manager (auto-login) takes <6 secs! Usually it is 10 secs in these tests with sysvinit.

Nice!

For MX-19 I have a delay before the console login shows, this seems to be caused by Plymouth. Removing it fixes the problem.

Huckleberry wrote: ↑Fri Dec 06, 2019 4:51 pm Writing on MX 19 Runit "Baremetal" - 32bit :D

Fantastic news, thanks for testing

Huckleberry wrote: ↑Fri Dec 06, 2019 4:51 pm Conky shows exactly same numbers of Ram and Cpu as it was with sysvinit 2.96

Yeah the difference is only a few hundred KiB, try ps_mem for a detailed break down of RAM usage.

Huckleberry wrote: ↑Fri Dec 06, 2019 4:51 pm maybe you edit the command and add: sudo apt update ; at the beginning :)

Good point, thanks!

Huckleberry wrote: ↑Fri Dec 06, 2019 5:19 pm screen doesn't get locked

Yes, that is a problem — light-locker is tightly integrated with LightDM so an alternative is needed.

Posted: **Fri Dec 06, 2019 5:33 pm**

Thank you so much :) I've been wondering Runit since a long time ago :)

Soon there would be a solution about light-dm. Maybe something simple, or an alternative as you say..

Will now reboot to try the automated startx.

Edit: That one is ok, too. As mentioned, you just type username & password manually on tty1 .

(And I see nothing related to light-dm on init text .. )
______________________________________________________

Default commands xfce4-... -suspend -reboot -halt

and also :

sudo init 0
sudo init 6

All work normal (as on sysvinit v 2.96)
_______________________________________________________

By the way, Ram usage on the same conky dropped by 5MİB :

The min. point was 210 MİB when new booted & idling on sysvinit, and now I saw 204 and it settled at 205 MİB

(Which was 340 when MX 19 was first installed)

Posted: **Fri Dec 06, 2019 6:27 pm**

Ran
sudo apt update && sudo apt install runit{,-init}
on EeePC 32 bit netbook.

But it still rebooted into SysVinit.
Rereading the thread and continuing trials.

Posted: **Fri Dec 06, 2019 8:12 pm**

Just a hey cool, it's interesting to see nixers playing with their systems and doing this type of thing. Someone is bound to have some fun and learn things in the process. Also gone with getting rid of any display manager and auto-login/startx for awhile now. Dang it, was hoping to see less system overhead by a wider margin here. But considering runit vs sysV, what they do, makes sense it's not by much and lightdm is all of like 8mbs-RAM or so anyway. Cool how-to Head_on and thanks for posting your findings other nixers. Nothing ventured, nothing gained. :)

Posted: **Fri Dec 06, 2019 9:03 pm**

It looks like Artix has a runit service to start lightdm.

Posted: **Fri Dec 06, 2019 9:24 pm**

I've always been wanting to play more with runit, it is lighter and faster than OpenRC.

I haven't tried Artix yet, but I did like Manjaro-OpenRC.

I don;t know if the Gentoo wiki is still accurate:
https://wiki.gentoo.org/wiki/Comparison_of_init_systems

What's the downside (if any) or "so what" of Per-service configuration being no?

Posted: **Fri Dec 06, 2019 9:33 pm**

jeffreyC wrote: ↑Fri Dec 06, 2019 9:03 pm It looks like Artix has a runit service to start lightdm.

Yes. Maybe there's a way to adapt..

Meanwhile I learned that Slim and LXDM also don't work.
_____________________________________________________________________________

Also found this: https://github.com/mat8913/runit-script ... ightdm/run

And http://smarden.org/runit/faq.html#run :

How do I run a service under runit service supervision ?

I want a service to be run under runit service supervision, so that it's automatically started on system boot, and supervised while system uptime. How does that work?

Answer: runit doesn't use the usual /etc/init.d/ init script interface, but uses a directory per service. To integrate a service into the runit init scheme, create a service directory for the service, and tell runit about it.

How do I create a service directory for the use with runit ?

Answer: Service directories usually are placed into the /etc/sv/ directory. Create a new directory for your service in /etc/sv/, put a ./run script into it, and make the script executable. Note that for the use with runit, service daemons must not put themself into the background, but must run in the foreground. Here's a simple example for a getty service:

$ cat /etc/sv/getty-2/run
#!/bin/sh
exec getty 38400 tty2 linux
$

Note the exec in the last line, it tells the shell that interprets the script to replace itself with the service daemon getty; this is necessary to make controlling the service work properly.

How do I tell runit about a new service ?

I created a service directory for a service that should run under runit service supervision. How do I tell runit about the new service directory, so that it picks up and runs the service by default?

Answer: Create a symbolic link in /service/ pointing to the service directory, runit will pick up the service within the next five seconds, and automatically start it on system boot. E.g.:

# ln -s /etc/sv/getty-2 /service/

Posted: **Sat Dec 07, 2019 7:18 am**

slim works with runit on antiX-19. You have to edit /etc/slim.conf.

Uncomment this line:

Code: Select all

# login_cmd         exec /bin/bash -login /etc/X11/Xsession %session

Comment this one:

Code: Select all

login_cmd   setsid /usr/local/bin/desktop-session %session

Posted: **Sat Dec 07, 2019 7:27 am**

Richard wrote: ↑Fri Dec 06, 2019 6:27 pm Ran
sudo apt update && sudo apt install runit{,-init}
on EeePC 32 bit netbook.

But it still rebooted into SysVinit.

How are you checking the init system? I use this:

Code: Select all

cat /proc/1/comm

Make sure that the packages are installed:

Code: Select all

apt policy systemd{,-shim} runit{,-init}

jeffreyC wrote: ↑Fri Dec 06, 2019 9:03 pm It looks like Artix has a runit service to start lightdm.

Do you have a link to that? I can't find it in the live ISO or their LightDM package.

The display manager can be started manually with

Code: Select all

sudo /etc/init,d/lightdm start

Or

Code: Select all

sudo service lightdm start

But then the reboot & poweroff buttons are greyed out in the exit dialogue (they work fine with a console login).

SwampRabbit wrote: ↑Fri Dec 06, 2019 9:24 pm What's the downside (if any) or "so what" of Per-service configuration being no?

Not entirely sure what that means tbh, the Gentoo wiki doesn't elaborate further

Huckleberry wrote: ↑Fri Dec 06, 2019 9:33 pm How do I run a service under runit service supervision ?

Debian's implementation automatically runs any services in /etc/rc2.d/ because runleveles 2-5 are identical. MX separates the runlevels further, perhaps this is why it won;t work. The LightDM init script has different runlevels listed for the Debian and MX package versions.

Posted: **Sat Dec 07, 2019 7:28 am**

anticapitalista wrote: ↑Sat Dec 07, 2019 7:18 am slim works with runit on antiX-19. You have to edit /etc/slim.conf.

Ah, so good. (I've read on some forum yesterday but that's such a good news).

In fact, I'd installed Slim on 18.3 (just to try) but couldn't make it work no matter what I did... I'll try on 19 again.

Posted: **Sat Dec 07, 2019 7:36 am**

I've got LightDM working now

Edit the file at /etc/runit/2 and add some lines for the other runlevels so it looks like this:

Code: Select all

#!/bin/sh

PATH=/usr/local/sbin:/usr/local/bin:/sbin:/usr/sbin:/bin:/usr/bin
SVDIR=/etc/service

# This script is also invoked in runit-systemd and runit-sysv packages.
# We must start sulogin and sysv scripts only if `runit' is current init
# system.
if [ -f /run/runit.stopit ] ; then
        # single mode
        if grep -q -w -i 'single' /proc/cmdline ; then
                chpst -P /sbin/sulogin -p /dev/tty1
        fi


        # Give sysv scripts 90 seconds (hardcoded in async-timeout source) to
        # start. If something goes wrong, they are detached from controlling
        # terminal.
        #
        # In this case tty1 would likely look ugly -- output from sysv scripts
        # is written over terminal session, but at least we would be able to
        # login.

        /lib/runit/async-timeout /lib/runit/run_sysv_scripts '/etc/rc2.d'
        /lib/runit/async-timeout /lib/runit/run_sysv_scripts '/etc/rc3.d'
        /lib/runit/async-timeout /lib/runit/run_sysv_scripts '/etc/rc4.d'
        /lib/runit/async-timeout /lib/runit/run_sysv_scripts '/etc/rc5.d'
fi

exec env - PATH=$PATH \
runsvdir -P "${SVDIR}" 'log: ...........................................................................................................................................................................................................................................................................................................................................................................................................'

It's not perfect because some services are started several times but LightDM runs and the exit dialogue works.

Posted: **Sat Dec 07, 2019 7:36 am**

Head_on_a_Stick wrote: ↑Sat Dec 07, 2019 7:27 am
jeffreyC wrote: ↑Fri Dec 06, 2019 9:03 pm It looks like Artix has a runit service to start lightdm.
Do you have a link to that? I can't find it in the live ISO or their LightDM package.

Would this work? https://github.com/artix-linux/runit-artix
(Edit: I see nothing related to DM )

https://wiki.artixlinux.org/Main/Runit

Posted: **Sat Dec 07, 2019 7:39 am**

Huckleberry wrote: ↑Sat Dec 07, 2019 7:36 am Would this work? https://github.com/artix-linux/runit-artix

Ah-ha, that's the ticket — thanks!

LightDM now works after a fashion (see my last post) but migrating to a runit script would be ideal.

Posted: **Sat Dec 07, 2019 7:41 am**

Thank you. I believe you'll make it perfect soon :)

Yesterday I thought to install and try GDM but quit.. Wondering Slim also :)

Posted: **Sat Dec 07, 2019 7:46 am**

https://github.com/artix-linux/packages ... htdm-runit

:D

Posted: **Sat Dec 07, 2019 9:28 am**

Head_on_a_Stick wrote: ↑Sat Dec 07, 2019 7:36 am It's not perfect because some services are started several times but LightDM runs and the exit dialogue works.

I have a better fix now: just edit /etc/runit/2 and change "/etc/rc2.d" to "/etc/rc5.d".

This command will change the file:

Code: Select all

sudo sed -i -e 's/rc2/rc5/' /etc/runit/2

Then reboot to test.

Posted: **Sat Dec 07, 2019 9:38 am**

... Not tested yet, but one thing I especially like into sysvinit is: sysv-rc-conf , does an equivalent exist too for runit ?

Posted: **Sat Dec 07, 2019 9:50 am**

oops wrote: ↑Sat Dec 07, 2019 9:38 am one thing I especially like into sysvinit is: sysv-rc-conf , does an equivalent exist too for runit ?

Yes:

Code: Select all

sudo sysv-rc-conf

:-)

But note that the stock runit package only runs services symlinked to /etc/rc2.d (runlevel 2) because in Debian runlevels 2-5 are identical. MX reserves runlevel 5 for the graphical desktop and their LightDM package only symlikns the init script to /etc/rc5.d, which is why it won't run OOTB.

Posted: **Sat Dec 07, 2019 10:30 am**

Head_on_a_Stick wrote: ↑Sat Dec 07, 2019 9:28 amjust edit /etc/runit/2 and change "/etc/rc2.d" to "/etc/rc5.d"

That's It !!!

Did it manually: "Edit as Root", saved, Rebooted and also tested screen-lock, then suspend with screen-lock...

All Fine ! That simple :D

Thank you so much.

( Maybe MX Team consider an MX-runit version -at least, non-official- :) )

Posted: **Sat Dec 07, 2019 10:53 am**

Where is the ISO?!?

Seriously, someone has to post it, later, when you guys sort everything out, for people like me, that have two left hands...

I hope I can at some point end up with having antiX with runit and Xfce, yay!

Btw, since Void Linux uses Runit exclusively, they probably have some other solutions it they may be needed...

https://docs.voidlinux.org/config/runit/

Posted: **Sat Dec 07, 2019 11:53 am**

Huckleberry wrote: ↑Sat Dec 07, 2019 7:41 am Thank you. I believe you'll make it perfect soon :)

Yesterday I thought to install and try GDM but quit.. Wondering Slim also :)

Slim always worked well for me under Gentoo with OpenRC.

But I see ya’ll found a fix for LightDM possibly already.

Posted: **Sat Dec 07, 2019 12:40 pm**

Buck Fankers wrote: ↑Sat Dec 07, 2019 10:53 am Where is the ISO?

64-bit (amd64) image here: https://drive.google.com/open?id=1Y9Y_Q ... NkgrGBdNes

sha512sum: https://drive.google.com/open?id=1rEoJ1 ... M4RtLeDxfw

Image integrity is crucial so please remember to check by placing the sha512sum file and the ISO image in the same working directory and then running

Code: Select all

sha512sum -c MX-19_runit.iso.sha512

Expected output:

Code: Select all

MX-19_runit.iso: OK

The image has a slightly different fix: LightDM's init script is now enabled for runlevels 2-5 rather than just runlevel 5; /etc/runit/2 is not modified.

Posted: **Sat Dec 07, 2019 12:44 pm**

"Congratulations" with a single word.

Posted: **Sat Dec 07, 2019 1:11 pm**

Hold on a minute, the new fix doesn't seem to work in the live image

It certainly works in an installed system but the live environment is different for some reason.

I'll build another version with /etc/runit/2 modified so that the live desktop loads automatically but I prefer the sysv-rc-conf fix.

EDIT: that doesn't work either, I'll try editing /etc/skel/.profile instead.

EDIT2: adding automatic startx to /etc/skel/.profile works for the live image, uploading the new version now.

Posted: **Sat Dec 07, 2019 5:52 pm**

Head_on_a_Stick wrote: ↑Sat Dec 07, 2019 12:40 pm
64-bit (amd64) image here: https://drive.google.com/open?id=1Y9Y_Q ... NkgrGBdNes
sha512sum: https://drive.google.com/open?id=1rEoJ1 ... M4RtLeDxfw

Cool, this is going to my testing partition, many thanks!!!

Posted: **Sat Dec 07, 2019 7:21 pm**

... I tried (a fast test) your iso MX19-runit (into VirtualBox), congratulation that's work. and I have only: 1116KB for xinit in use.

One problem for me is that I can not see the processus lightdm via the user demo (all is under runit)... so I can not change for an other user via lighdm easily (via switch-user). Nor via Ctrl+Alt=F7, Ctrl+Alt=F8 , Ctrl+Alt=Fn

Code: Select all

demo@mx1:~
$ pstree -p ${pid}
runit(1)─┬─ModemManager(3158)─┬─{ModemManager}(3183)
         │                    └─{ModemManager}(3192)
         ├─NetworkManager(3086)─┬─dhclient(3162)
         │                      ├─{NetworkManager}(3087)
         │                      └─{NetworkManager}(3090)
         ├─VBoxClient(3571)───VBoxClient(3572)───{VBoxClient}(3582)
         ├─VBoxClient(3581)───VBoxClient(3584)
         ├─VBoxClient(3590)───VBoxClient(3591)───{VBoxClient}(3592)
         ├─VBoxClient(3597)───VBoxClient(3598)─┬─{VBoxClient}(3599)
         │                                     └─{VBoxClient}(3600)
         ├─VBoxService(2799)─┬─{VBoxService}(2801)
         │                   ├─{VBoxService}(2802)
         │                   ├─{VBoxService}(2803)
         │                   ├─{VBoxService}(2804)
         │                   ├─{VBoxService}(2805)
         │                   ├─{VBoxService}(2807)
         │                   └─{VBoxService}(2809)
         ├─accounts-daemon(3110)─┬─{accounts-daemon}(3116)
         │                       └─{accounts-daemon}(3119)
         ├─acpi_fakekeyd(2612)
         ├─anacron(2834)
         ├─at-spi-bus-laun(3642)─┬─dbus-daemon(3647)
         │                       ├─{at-spi-bus-laun}(3643)
         │                       ├─{at-spi-bus-laun}(3644)
         │                       └─{at-spi-bus-laun}(3646)
         ├─at-spi2-registr(3649)─┬─{at-spi2-registr}(3655)
         │                       └─{at-spi2-registr}(3657)
         ├─avahi-daemon(3023)───avahi-daemon(3024)
         ├─cgmanager(2644)
         ├─colord(3833)─┬─{colord}(3839)
         │              └─{colord}(3841)
         ├─conky(4027)─┬─{conky}(4031)
         │             ├─{conky}(4032)
         │             └─{conky}(4033)
         ├─cron(2904)
         ├─cups-browsed(3198)
         ├─dbus-daemon(2935)
         ├─dbus-daemon(3545)
         ├─dbus-daemon(3557)
         ├─dbus-launch(3544)
         ├─dbus-launch(3556)
         ├─fbxkb(3732)
         ├─gnome-keyring-d(3741)─┬─{gnome-keyring-d}(3745)
         │                       ├─{gnome-keyring-d}(3747)
         │                       └─{gnome-keyring-d}(3754)
         ├─gpg-agent(3661)
         ├─gvfs-afc-volume(3892)─┬─{gvfs-afc-volume}(3893)
         │                       ├─{gvfs-afc-volume}(3894)
         │                       └─{gvfs-afc-volume}(3896)
         ├─gvfs-goa-volume(3887)─┬─{gvfs-goa-volume}(3888)
         │                       └─{gvfs-goa-volume}(3889)
         ├─gvfs-gphoto2-vo(3882)─┬─{gvfs-gphoto2-vo}(3883)
         │                       └─{gvfs-gphoto2-vo}(3885)
         ├─gvfs-mtp-volume(3877)─┬─{gvfs-mtp-volume}(3878)
         │                       └─{gvfs-mtp-volume}(3880)
         ├─gvfs-udisks2-vo(3859)─┬─{gvfs-udisks2-vo}(3860)
         │                       └─{gvfs-udisks2-vo}(3861)
         ├─gvfsd(3626)─┬─{gvfsd}(3627)
         │             └─{gvfsd}(3628)
         ├─gvfsd-fuse(3631)─┬─{gvfsd-fuse}(3636)
         │                  ├─{gvfsd-fuse}(3637)
         │                  ├─{gvfsd-fuse}(3638)
         │                  ├─{gvfsd-fuse}(3639)
         │                  └─{gvfsd-fuse}(3640)
         ├─gvfsd-metadata(3903)─┬─{gvfsd-metadata}(3904)
         │                      └─{gvfsd-metadata}(3905)
         ├─polkitd(3128)─┬─{polkitd}(3139)
         │               └─{polkitd}(3143)
         ├─pulseaudio(3672)─┬─{pulseaudio}(3691)
         │                  └─{pulseaudio}(3692)
         ├─python(3941)─┬─{python}(3986)
         │              ├─{python}(3987)
         │              ├─{python}(3994)
         │              ├─{python}(3995)
         │              └─{python}(3996)
         ├─rpc.idmapd(2124)
         ├─rpc.statd(2108)
         ├─rpcbind(2077)
         ├─rsyslogd(2661)─┬─{rsyslogd}(2662)
         │                ├─{rsyslogd}(2663)
         │                └─{rsyslogd}(2665)
         ├─runsvdir(2390)─┬─runsv(3339)───getty(3346)
         │                ├─runsv(3340)───login(3349)───startx(3458)───xinit(3497)─┬─Xorg(3498)─┬─{+
         │                │                                                        │            ├─{+
         │                │                                                        │            ├─{+
         │                │                                                        │            └─{+
         │                │                                                        └─xfce4-session(+
         │                ├─runsv(3341)───getty(3345)
         │                ├─runsv(3342)───getty(3351)
         │                ├─runsv(3343)───getty(3347)
         │                └─runsv(3344)───getty(3352)
         ├─systemd-logind(3081)
         ├─systemd-udevd(993)
         ├─tumblerd(3725)─┬─{tumblerd}(3733)
         │                ├─{tumblerd}(3736)
         │                ├─{tumblerd}(3897)
         │                ├─{tumblerd}(3898)
         │                ├─{tumblerd}(3899)
         │                └─{tumblerd}(3900)
         ├─udisksd(3863)─┬─{udisksd}(3864)
         │               ├─{udisksd}(3866)
         │               ├─{udisksd}(3869)
         │               └─{udisksd}(3874)
         ├─upowerd(3680)─┬─{upowerd}(3682)
         │               └─{upowerd}(3683)
         ├─volumeicon(3906)─┬─{volumeicon}(3907)
         │                  ├─{volumeicon}(3908)
         │                  └─{volumeicon}(3909)
         ├─xfce4-notifyd(3786)─┬─{xfce4-notifyd}(3795)
         │                     └─{xfce4-notifyd}(3796)
         ├─xfce4-power-man(3797)─┬─{xfce4-power-man}(3814)
         │                       └─{xfce4-power-man}(3816)
         ├─xfconfd(3548)─┬─{xfconfd}(3549)
         │               └─{xfconfd}(3550)
         ├─xfconfd(3651)─┬─{xfconfd}(3652)
         │               └─{xfconfd}(3653)
         └─xfsettingsd(3673)─┬─{xfsettingsd}(3675)
                             └─{xfsettingsd}(3676)

Posted: **Sat Dec 07, 2019 7:34 pm**

Head_on_a_Stick wrote: ↑Sat Dec 07, 2019 1:11 pm
EDIT: that doesn't work either, I'll try editing /etc/skel/.profile instead.
EDIT2: adding automatic startx to /etc/skel/.profile works for the live image, uploading the new version now.

I installed your latest version, I did had to start GUI manually after entering password, but after install startx starts automatically. I'm keeping this one, thanks!

Posted: **Sat Dec 07, 2019 10:34 pm**

Thanks, Head_on_a_Stick.
Appreciate the pointers.
I had omitted a step.

Runit is interesting, but will be leaving the 32 bit netbook, running MX-18.3, with a friend in Columbia in a couple of days.

Will do trials on 64 bit in a few weeks.
Limited to Android until then.

Posted: **Sun Dec 08, 2019 6:43 am**

oops wrote: ↑Sat Dec 07, 2019 7:21 pm One problem for me is that I can not see the processus lightdm via the user demo (all is under runit)... so I can not change for an other user via lighdm easily (via switch-user). Nor via Ctrl+Alt=F7, Ctrl+Alt=F8 , Ctrl+Alt=Fn

Doesn't look like LightDM is running at all for you, I think I did have an image up without LightDM (briefly) so you may have installed that.

Check if LightDM is installed and use sysv-rc-conf to activate it for runlevels 2, 3, 4 & 5.

Buck Fankers wrote: ↑Sat Dec 07, 2019 7:34 pm I did had to start GUI manually after entering password

Yeah, I'm going to add some stuff to startx automatically in the live environment. Watch out for a new version soon :-)

Posted: **Sun Dec 08, 2019 6:57 am**

Head_on_a_Stick wrote: ↑Sun Dec 08, 2019 6:43 am ...
Check if LightDM is installed and use sysv-rc-conf to activate it for runlevels 2, 3, 4 & 5.

... Yes it was installed, I launched it into the root account with success with your iso ... and after (or before, I don't remember), with the user demo, the loggin screen was automatic.

EDIT: OK, in fact I have to login first to root, then start lightdm, then disconnect the root user, and then connect to demo or the other users ... I will test more later.

EDIT2: FI: and the mxuser file is missing into my iso (I have only the antixers one) ceni instead - network-manager, etc:
/etc/sudoers.d/mxuser

Code: Select all

# sudoers file.
 
%users ALL=(root) NOPASSWD: /sbin/halt 

%users ALL=(root) NOPASSWD: /sbin/poweroff

%users ALL=(root) NOPASSWD: /sbin/reboot  

%users ALL=(root) NOPASSWD: /sbin/blkid 

%users ALL=(root) NOPASSWD: /sbin/fdisk.distrib 

%users ALL=(root) NOPASSWD: /usr/local/bin/persist-config

%users ALL=(root) NOPASSWD: /usr/local/bin/persist-save 

%users ALL=(root) NOPASSWD:SETENV: /usr/sbin/minstall 

%users ALL=(root) NOPASSWD: /bin/chvt 

%users ALL=(root) NOPASSWD: /usr/sbin/service network-manager restart

Defaults env_keep += "RESTARTED HOME"
Defaults  !requiretty
Defaults  !tty_tickets

I am waiting for your new/latest iso. (but you already did a good job)

Posted: **Sun Dec 08, 2019 10:01 am**

oops wrote: ↑Sun Dec 08, 2019 6:57 am OK, in fact I have to login first to root, then start lightdm, then disconnect the root user, and then connect to demo or the other users ... I will test more later.

For the current image a manual console login is required for the live system (after which the desktop will launch automatically) but once the system is installed then LightDM should function as normal with no need for user intervention.

oops wrote: ↑Sun Dec 08, 2019 6:57 am the mxuser file is missing into my iso

Hmm, yes, I didn't delete that but it certainly isn't there

Thanks for the feedback, I will investigate some more.

EDIT: the official MX-19_x64.iso also lacks /etc/sudoers.d/mxuser so I presume this is intended for that release.

Posted: **Sun Dec 08, 2019 11:08 am**

Head_on_a_Stick wrote: ↑Sun Dec 08, 2019 10:01 am
EDIT: the official MX-19_x64.iso also lacks /etc/sudoers.d/mxuser so I presume this is intended for that release.

... Good question, I don't know. (but I have it _ MX19 amd64)

Posted: **Sun Dec 08, 2019 5:57 pm**

Would it be possible for 18.3 , too ?

It looks runit is already installed here, (in MXPI) but it still needs to be done manually..
__________________________________________________________

By the way;

On 19 I did the changes via sysv-rc-conf then changed /etc/runit/2 back to original as "/etc/rc2.d"

Rebooted: Everything's fine :)

Posted: **Mon Dec 09, 2019 12:54 pm**

Huckleberry wrote: ↑Sun Dec 08, 2019 5:57 pm 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

Posted: **Mon Dec 09, 2019 1:52 pm**

Head_on_a_Stick wrote: ↑Mon Dec 09, 2019 12:54 pm[1] It was me

Posted: **Mon Dec 09, 2019 2:29 pm**

Posted: **Fri Dec 13, 2019 8:28 am**

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 ...

Posted: **Fri Dec 13, 2019 8:53 am**

Huckleberry wrote: ↑Fri Dec 13, 2019 8:28 am 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

Posted: **Fri Dec 13, 2019 9:16 am**

Huckleberry wrote: ↑Fri Dec 13, 2019 8:28 am 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

Posted: **Wed Jun 10, 2020 6:03 pm**

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

Posted: **Mon Aug 31, 2020 10:21 am**

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!!

Posted: **Mon Aug 31, 2020 10:49 am**

aldQueiroz wrote: ↑Mon Aug 31, 2020 10:21 am 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.

Posted: **Mon Aug 31, 2020 11:23 am**

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

Posted: **Mon Aug 31, 2020 11:42 am**

andyprough wrote: ↑Mon Aug 31, 2020 10:49 am (...) 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.

Thanks, andyprough ! I wish I knew it sooner! I should have tried antiX at first option to the oldest machine, with Sempro CPU and 3 GB DDR2 RAM (do you believe that system was meant to run "Windows 10" before? And with only 1 GB of RAM ?!..). I will download one of those antiX ISOs for tests later, but I'm afraid I won't install any of them right now. The machines running with MX Linux are functional (although some minor cons...) and I'm afraid it isn't worth to replace the whole OS just to try runit as init system (it took me two days configuring the oldest machine, which I'll donate to a 8 years old nephew...). However, if antiX had a runit liveUSB version, I could give a try!
By the way, which Desktop environment comes as default with antiX runit ISOs ? XFCE, I suppose.. That's ok to me. And, probably, the only feasible option for older machines. But I wish there was option for Plasma 5, or something else...

Posted: **Mon Aug 31, 2020 12:08 pm**

There is a Live iso for antiX 19.2 runit version.

The default "desktop" in antiX is "rox-icewm", which is a Window Manager setup instead of a Desktop Environment. You can add XFCE or KDE using the repos. But antiX really shines because it does not use a Desktop Environment. It uses three Window Managers by default along with some alternatives and a couple of different file managers. IceWM, Fluxbox, and JWM, along with Herbstluftwm and ROX and SpaceFM. It's a little different approach than XFCE or KDE but it works very well. And it works in low memory much better than any of the DE's.

Seaken64

Posted: **Mon Aug 31, 2020 12:15 pm**

aldQueiroz wrote: ↑Mon Aug 31, 2020 11:42 amThanks, andyprough ! I wish I knew it sooner! I should have tried antiX at first option to the oldest machine, with Sempro CPU and 3 GB DDR2 RAM (do you believe that system was meant to run "Windows 10" before? And with only 1 GB of RAM ?!..). I will download one of those antiX ISOs for tests later, but I'm afraid I won't install any of them right now. The machines running with MX Linux are functional (although some minor cons...) and I'm afraid it isn't worth to replace the whole OS just to try runit as init system (it took me two days configuring the oldest machine, which I'll donate to a 8 years old nephew...). However, if antiX had a runit liveUSB version, I could give a try!
By the way, which Desktop environment comes as default with antiX runit ISOs ? XFCE, I suppose.. That's ok to me. And, probably, the only feasible option for older machines. But I wish there was option for Plasma 5, or something else...

antiX comes with icewm as the default desktop, but you can add any desktop you like. I don't have a copy of antiX running right now, but I think plasma and xfce are available along with some others like Mate.

Posted: **Tue Sep 01, 2020 10:25 am**

seaken64 wrote: ↑Mon Aug 31, 2020 12:08 pm There is a Live iso for antiX 19.2 runit version.

The default "desktop" in antiX is "rox-icewm", which is a Window Manager setup instead of a Desktop Environment. You can add XFCE or KDE using the repos. But antiX really shines because it does not use a Desktop Environment. It uses three Window Managers by default along with some alternatives and a couple of different file managers. IceWM, Fluxbox, and JWM, along with Herbstluftwm and ROX and SpaceFM. It's a little different approach than XFCE or KDE but it works very well. And it works in low memory much better than any of the DE's.

Seaken64

Thank you, pal! It's interesting, but I'm not sure if such approach would fit my immediate needs... The machine I'm configuring is meant to be used by my 8 years old nephew (it'll be his first computer, and must be used mainly for studying "online"), and it must be easy and intuitive to use by any Newbie (and fully localized in Portuguese_BR); I'm afraid an environment with only Window Managers won't suffice those requirements...

Posted: **Tue Sep 01, 2020 10:39 am**

andyprough wrote: ↑Mon Aug 31, 2020 12:15 pm (...)
antiX comes with icewm as the default desktop, but you can add any desktop you like. I don't have a copy of antiX running right now, but I think plasma and xfce are available along with some others like Mate.

Thanks, again! If antiX runit edition proves to be more responsive (not only faster to boot, but faster to launch and run general applications!) than my current MX Linux, it is worth to give a try! But I prefer to do it with a liveUSB session. Some tip about how to make it?...

Posted: **Tue Sep 01, 2020 11:50 am**

aldQueiroz wrote: ↑Tue Sep 01, 2020 10:39 am Thanks, again! If antiX runit edition proves to be more responsive (not only faster to boot, but faster to launch and run general applications!) than my current MX Linux, it is worth to give a try! But I prefer to do it with a liveUSB session. Somo tip about how to make it?...

Just download the antiX runit full ISO from here: https://mirrors.evowise.com/mxlinux-iso ... 4-full.iso

And then go to the Main Menu on your MX system and select - MX Tools - MX Live USB Maker, which will make your live USB for you.

If you put XFCE on antiX and spent an hour setting up a nice theme and visuals and installing the programs you want, your son could use it just fine I'm sure. And then you would be using runit without any of the hassle of getting it running on MX.

Posted: **Tue Sep 01, 2020 12:06 pm**

andyprough wrote: ↑Tue Sep 01, 2020 11:50 am (...) Just download the antiX runit full ISO from here: https://mirrors.evowise.com/mxlinux-iso ... 4-full.iso

And then go to the Main Menu on your MX system and select - MX Tools - MX Live USB Maker, which will make your live USB for you.

If you put XFCE on antiX and spent an hour setting up a nice theme and visuals and installing the programs you want, your son could use it just fine I'm sure. And then you would be using runit without any of the hassle of getting it running on MX.

"download antiX19-2-runit_x64-full.iso" : checked!!
"go to the Main Menu on your MX system and select - MX Tools - MX Live USB Maker, which will make your live USB for you." : next to go!!

If the antiX_runit proves to be faster, I shall use it at my own "production machine" as well!!
Thank you, andyprough!!
Regards!

Posted: **Thu Sep 03, 2020 12:03 pm**

Hi, a report of antiX+runit experience: I've made the liveUSB, did start a live session at my own desktop and... "man"!!! Where antiX was all my life?!?

It did boot fast, as expected (thanks to runit, right?), and start "X" in less than 3 seconds!!! All applications launch fast too, even from the USB! I guess it will be even faster if properly installed at the HDD (or at a SSD, as I'm planning to do with my desktop!). I really wish I had known about antiX_runnit sooner! And I'm seriously tempted to change the current MX Linux 19-2 I'm configuring at that old Sempro CPU for antiX (replace the "Patito feo" for a "Roadrunner"!!!)

Posted: **Thu Sep 03, 2020 1:23 pm**

aldQueiroz wrote: ↑Thu Sep 03, 2020 12:03 pm Hi, a report of antiX+runit experience: I've made the liveUSB, did start a live session at my own desktop and... "man"!!! Where antiX was all my life?!? It did boot fast, as expected (thanks to runit, right?), and start "X" in less than 3 seconds!!! All applications launch fast too, even from the USB! I guess it will be even faster if properly installed at the HDD (or at a SSD, as I'm planning to do with my desktop!). I really wish I had known about antiX_runnit sooner! And I'm seriously tempted to change the current MX Linux 19-2 I'm configuring at that old Sempro CPU for antiX (replace the "Patito feo" for a "Roadrunner"!!!)

Yes, it is seriously fast. Zoom zoom.

Posted: **Thu Sep 03, 2020 1:43 pm**

andyprough wrote: ↑Thu Sep 03, 2020 1:23 pm ...Yes, it is seriously fast. Zoom zoom.

... I will try via a frugal install the x32 version of antix-19 runit.

Posted: **Thu Sep 03, 2020 2:31 pm**

andyprough wrote: ↑Thu Sep 03, 2020 1:23 pm
aldQueiroz wrote: ↑Thu Sep 03, 2020 12:03 pm (...) I'm seriously tempted to change the current MX Linux 19-2 I'm configuring at that old Sempro CPU for antiX (replace the "Patito feo" for a "Roadrunner"!!!)
Yes, it is seriously fast. Zoom zoom.

Tell me, pal, how about the availability of apps in antiX repos? I saw it comes with LibreOffice 6.1.4, an older version than MX Linux default install, what's already sort of... outdated! In MX Linux we can get a later version of it using flatpack (from default flathub repository), what I didn't see at antiX live session... How about Zoom? I could name some few other apps of my interest (like iBus and/or fcixt, for multilingual input, which is a "must" to me) which I would make use...
In a second thought, I'm afraid I will not install antiX right now at that old computer I mentioned; not before I myself become acquainted with this system and its environment (ok, I could install XFCE, but if so, probably the general responsiveness wouldn't be so fast...!); but I'm planning to use this version of antiX_runit for a next upgrade of my own system (did I mention that I'll move it to a SSD?...)
Thanks again, andyprough! I look forward to exchange more knowledge with you all!!

Posted: **Thu Sep 03, 2020 3:06 pm**

aldQueiroz wrote: ↑Thu Sep 03, 2020 2:31 pmTell me, pal, how about the availability of apps in antiX repos? I saw it comes with LibreOffice 6.1.4, as the se version as MX Linux default install, what's already sort of... outdated! In MX Linux we can get a later version of it using flatpack (from default flathub repository), what I didn't see at antiX live session... How about Zoom? I could name some few other apps of my interest (like iBus and/or fcixt, for multilingual input, which is a "must" to me) which I would make use...
In a second thought, I'm afraid I will not install antiX right now at that old computer I mentioned; not before I myself become acquainted with this system and its environment (ok, I could install XFCE, but if so, probably the general responsiveness wouldn't be so fast...!); but I'm planning to use this version of antiX_runit for a next upgrade of my own system (did I mention that I'll move it to a SSD?...)
Thanks again, andyprough! I look forward to exchange more knowledge with you all!!

antiX has its own package installer similar to MX Package Installer. I don't have it installed right now, so you will have to go through the various tabs and folders and see if the software you are looking for is available. Definitely one reason to stick with MX is that all the great software is at your fingertips. But, you wanted to use runit, so I recommended you at least try the antiX runit version before going through the trouble of getting and keeping MX running with runit.

As far as getting the latest LibreOffice - just download the debian package from the LibreOffice website, de-compress it, cd into the DEB folder, and

Code: Select all

sudo apt install ./*deb

Bam! You'll have the latest LibreOffice. Works on every Debian-based distro I've tried.

Posted: **Thu Sep 03, 2020 3:29 pm**

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.)

Posted: **Thu Sep 03, 2020 3:37 pm**

anticapitalista wrote: ↑Thu Sep 03, 2020 3:29 pm 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 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.)

Thank you anticapitalista. Normally I have a machine running antiX runit that I could answer questions from, but recently I converted that into an MX package building system.

@aldQueiroz - listen to anticapitalista - he is the founder and lead dev for antiX.

Posted: **Thu Sep 03, 2020 4:13 pm**

aldQueiroz wrote: ↑Thu Sep 03, 2020 2:31 pm In MX Linux we can get a later version of it using flatpack (from default flathub repository),

In MX Linux you can get latest LibreOffice version (currently 7.0.1) from MX Package Installer Populare Apps:

LO7-POP-APPS.png

EDIT: precised the comment to be applicable in MX Linux

Posted: **Thu Sep 03, 2020 4:47 pm**

@fehlix - user is running antiX not MX. We do not have a flatpak install option in our version of package Installer (deliberately).

Posted: **Thu Sep 03, 2020 7:05 pm**

andyprough wrote: ↑Thu Sep 03, 2020 3:06 pm (...)
antiX has its own package installer similar to MX Package Installer. I don't have it installed right now, so you will have to go through the various tabs and folders and see if the software you are looking for is available. Definitely one reason to stick with MX is that all the great software is at your fingertips. But, you wanted to use runit, so I recommended you at least try the antiX runit version before going through the trouble of getting and keeping MX running with runit.

As far as getting the latest LibreOffice - just download the debian package from the LibreOffice website, de-compress it, cd into the DEB folder, and
Code: Select all
sudo apt install ./*deb
Bam! You'll have the latest LibreOffice. Works on every Debian-based distro I've tried.

Thanks, andyprough! I'm curious about runit since I knew Void Linux (which didn't become my first choice due to it's not meant for newbies, like me...), and I know runit grants boot times significantly shorter than SysVinit and others. But my biggest concern is responsiveness of the system! It's acceptable to wait around 30 seconds from boot until the system be ready to use, but it's a pain in the a...rchive (!) to wait up to 5 seconds to launch apps like LibreOffice! Or worse, click on a button and get some response within a gap of 2, 3 seconds!...
I've already installed LibreOffice and other apps using packages from the website, exactly because I needed the latest version. But, definitely, it isn't as easy as installing from the distro's repos (and, sometimes, it doesn't work due to missing dependencies...)

Posted: **Thu Sep 03, 2020 7:08 pm**

anticapitalista wrote: ↑Thu Sep 03, 2020 3:29 pm 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'll check it out this minutely, anticapitalista! "Obrigado"!!

Posted: **Thu Sep 03, 2020 7:14 pm**

fehlix wrote: ↑Thu Sep 03, 2020 4:13 pm
aldQueiroz wrote: ↑Thu Sep 03, 2020 2:31 pm In MX Linux we can get a later version of it using flatpack (from default flathub repository),
In MX Linux you can get latest LibreOffice version (currently 7.0.1) from MX Package Installer Populare Apps:
LO7-POP-APPS.png
EDIT: precised the comment to be applicable in MX Linux

That was a recent update of LibreOffice package at MX Linux, wasn't it? The last time I saw it, the version available from Backports repo was still 6.4.5 (while the version from flatpack was 7.0.3; but the version available there now is 7.0.1-2, I don't know why...)

Posted: **Thu Sep 03, 2020 7:30 pm**

anticapitalista wrote: ↑Thu Sep 03, 2020 4:47 pm @fehlix - user is running antiX not MX. We do not have a flatpak install option in our version of package Installer (deliberately).

anticapitalista, I am considering antiX, runit version. But I am, currently, a MX user (after have been using Ubuntu, and Mageia)
I liked Mageia; its MCC (Mageia Control Center) is excellent! But, unfortunately, Mageia is adherent to systemd, which I "abhor" ! The same with Ubuntu (this last one has a lot of idiosyncrasies I bear no longer...). That's why I chose MX Linux; I wish a distro "systemd free", but still simple to install (sorry, Gentoo!) and configure (sorry, Void!...) and with a good portfolio of applications! If I knew sooner of antiX, probably I had chosen it!

Posted: **Thu Sep 03, 2020 7:40 pm**

aldQueiroz wrote: ↑Thu Sep 03, 2020 7:30 pmI wish a distro "systemd free", but still simple to install (sorry, Gentoo!) and configure (sorry, Void!...) and with a good portfolio of applications!

You're talking about antiX - completely systemd free. On MX we still have systemd, we just have the option to not enable it at boot time which is the default.

Posted: **Thu Sep 03, 2020 7:53 pm**

andyprough wrote: ↑Thu Sep 03, 2020 7:40 pm
aldQueiroz wrote: ↑Thu Sep 03, 2020 7:30 pmI wish a distro "systemd free", but still simple to install (sorry, Gentoo!) and configure (sorry, Void!...) and with a good portfolio of applications!
You're talking about antiX - completely systemd free. On MX we still have systemd, we just have the option to not enable it at boot time which is the default.

I know, andyprough. And I do think it is a clever approach: having systemd installed (then solving the troubles about systemd dependency of a lot of applications!) but disabled by default! And if people prefer to use it, it's up to them! I prefer not!!

Posted: **Thu Sep 03, 2020 8:43 pm**

aldQueiroz wrote: ↑Thu Sep 03, 2020 7:14 pm
fehlix wrote: ↑Thu Sep 03, 2020 4:13 pm
aldQueiroz wrote: ↑Thu Sep 03, 2020 2:31 pm In MX Linux we can get a later version of it using flatpack (from default flathub repository),
In MX Linux you can get latest LibreOffice version (currently 7.0.1) from MX Package Installer Populare Apps:
LO7-POP-APPS.png
EDIT: precised the comment to be applicable in MX Linux
That was a recent update of LibreOffice package at MX Linux, wasn't it? The last time I saw it, the version available from Backports repo was still 6.4.5 (while the version from flatpack was 7.0.3; but the version available there now is 7.0.1-2, I don't know why...)

Within MX Package Installer (MXPI) -> Populare Apps, we have a "special" LibreOffice installer for both the stable buster version and the buster backports version. The idea was, you can switch between those versions back and forth. Whatever version becomes available within buster-backports shall be installable with this "special" MXPI-PopApps installer. In addttiion the language packs for LO shall also be available for the installed version.
Note:
We do also have a MX-testrepp version of latest LibreOffice. As this can become difficult to sort all dependency, it's recommended to install/keep first LO-buster-stable version before upgrade to MX-testrepo latest version.

Posted: **Thu Sep 03, 2020 9:01 pm**

I think you should be able to install flatpaks in antiX. It's just that you'll have to install and enable the relevant flatpak programs and repos, and then search for and install the flatpak apps manually without the help of any gui tools.

Posted: **Thu Sep 03, 2020 9:04 pm**

asqwerth wrote: ↑Thu Sep 03, 2020 9:01 pm I think you should be able to install flatpaks in antiX. It's just that you'll have to install and enable the relevant flatpak programs and repos, and then search for and install the flatpak apps manually without the help of any gui tools.

Thank you, asqwerth! The more I hear from you all, the more excited, anxious to use antiX I get!!

Posted: **Thu Sep 03, 2020 9:28 pm**

Just be aware that:

1. flatpak apps and their corresponding runtime (to run in their own enclosed environment) are huge. 1 runtime can take 1 GB. If you update a flatpak app and the runtime has also been updated, you'll add an additional 1+ GB of disk usage, and the old runtime will remain on your system until you manually delete it (if you're not using it for any other flatpak app)

2. flatpak apps come from third party sources so the quality of their creation will vary. Some flatpak apps might work better than others.

Posted: **Fri Sep 04, 2020 9:19 am**

... Yes runit is fast and light, I have tried the antix19 standard buster x64 version, added lightdm, xfce, and some other apps ... into a virtualBox VM ... and tried to create a new iso via a snapshot (antixcc.sh) successfully generated ... but after, impossible to boot via this(these) snapshot (lightdm or slim or even a grub single mode I do not have the console) into virtualBox, so is this behavior is normal with the runit versions (or maybe a workaroud exists) ?

Posted: **Fri Sep 04, 2020 10:27 am**

oops wrote: ↑Fri Sep 04, 2020 9:19 am ... Yes runit is fast and light, I have tried the antix19 standard buster x64 version, added lightdm, xfce, and some other apps ... into a virtualBox VM ... and tried to create a new iso via a snapshot (antixcc.sh) successfully generated ... but after, impossible to boot via this(these) snapshot (lightdm or slim or even a grub single mode I do not have the console) into virtualBox, so is this behavior is normal with the runit versions (or maybe a workaroud exists) ?

I thought we were supposed to remaster a live usb after making our changes to it, not try to take a snapshot from virtualbox. Do snapshots from virtualbox boot at all?

Posted: **Fri Sep 04, 2020 10:32 am**

andyprough wrote: ↑Fri Sep 04, 2020 10:27 am
oops wrote: ↑Fri Sep 04, 2020 9:19 am ... Yes runit is fast and light, I have tried the antix19 standard buster x64 version, added lightdm, xfce, and some other apps ... into a virtualBox VM ... and tried to create a new iso via a snapshot (antixcc.sh) successfully generated ... but after, impossible to boot via this(these) snapshot (lightdm or slim or even a grub single mode I do not have the console) into virtualBox, so is this behavior is normal with the runit versions (or maybe a workaroud exists) ?
I thought we were supposed to remaster a live usb after making our changes to it, not try to take a snapshot from virtualbox. Do snapshots from virtualbox boot at all?

They should, but I don't know about runit versions.

Few years ago, I set up a VM install of antiX16 (on my desktop PC), installed MATE, customised it the way I wanted, then made a snapshot iso. I made a live USB from within the VM which I then used to install onto my old laptop.

Posted: **Fri Sep 04, 2020 10:44 am**

asqwerth wrote: ↑Fri Sep 04, 2020 10:32 am ...
They should, but I don't know about runit versions.

Few years ago, I set up a VM install of antiX16 (on my desktop PC), installed MATE, customised it the way I wanted, then made a snapshot iso. I made a live USB from within the VM which I then used to install onto my old laptop.

Yes, I do this way usually for my old eepc (worked like a charm for antiX19 classic and MX19).

Posted: **Fri Sep 04, 2020 10:53 am**

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.

Posted: **Fri Sep 04, 2020 1:22 pm**

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:

anticapitalista wrote: ↑Thu Sep 03, 2020 3:29 pm 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...).

Posted: **Wed Sep 09, 2020 8:26 pm**

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

Posted: **Mon Jun 14, 2021 6:05 pm**

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

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

Posted: **Fri Jun 18, 2021 10:06 am**

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!

Posted: **Fri Jun 18, 2021 10:16 am**

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...

Posted: **Sat Nov 27, 2021 10:35 am**

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?

Posted: **Sat Nov 27, 2021 11:57 am**

FraterLinux wrote: ↑Sat Nov 27, 2021 10:35 am ...
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.

Posted: **Sat Nov 27, 2021 12:31 pm**

FraterLinux wrote: ↑Sat Nov 27, 2021 10:35 am 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.

Posted: **Sat Nov 27, 2021 12:49 pm**

towwire wrote: ↑Sat Nov 27, 2021 12:31 pm
FraterLinux wrote: ↑Sat Nov 27, 2021 10:35 am 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.

Posted: **Sat Nov 27, 2021 12:53 pm**

oops wrote: ↑Sat Nov 27, 2021 11:57 am
FraterLinux wrote: ↑Sat Nov 27, 2021 10:35 am ...
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.

I appreciate the tip!

Posted: **Tue Nov 30, 2021 3:19 pm**

FraterLinux wrote: ↑Sat Nov 27, 2021 12:53 pm ...
I appreciate the tip!

... You're welcome.

Posted: **Tue Nov 30, 2021 4:39 pm**

Note - slimski is not available on MX

Posted: **Fri Dec 17, 2021 3:24 pm**

In Debian 11 "bullseye" got worse support for non-Systemd Init.
It's not like this?

MX Linux Forum

Booting MX-19 with runit

Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting antiX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit

Re: Booting MX-19 with runit