Booting MX-19 with runit

Here is where you can post tips and tricks to share with other users of MX. Do not ask for help in this Forum.
Message
Author
User avatar
Head_on_a_Stick
Posts: 919
Joined: Sun Mar 17, 2019 3:37 pm

Re: Booting MX-19 with runit

#31 Post by Head_on_a_Stick »

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

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.
mod note: Signature removed, please read the forum rules

User avatar
Buck Fankers
Posts: 767
Joined: Sat Mar 10, 2018 8:06 pm

Re: Booting MX-19 with runit

#32 Post by Buck Fankers »

Cool, this is going to my testing partition, many thanks!!! :winner:
Last edited by Buck Fankers on Wed Dec 11, 2019 9:17 am, edited 1 time in total.

User avatar
oops
Posts: 1885
Joined: Tue Apr 10, 2018 5:07 pm

Re: Booting MX-19 with runit

#33 Post by oops »

... 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)
Pour les nouveaux utilisateurs: Alt+F1 pour le manuel, ou FAQS, MX MANUEL, et Conseils Debian - Info. système “quick-system-info-mx” (QSI) ... Ici: System: MX-19_x64 & antiX19_x32

User avatar
Buck Fankers
Posts: 767
Joined: Sat Mar 10, 2018 8:06 pm

Re: Booting MX-19 with runit

#34 Post by Buck Fankers »

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!

User avatar
Richard
Posts: 1590
Joined: Fri Dec 12, 2008 9:31 am

Re: Booting MX-19 with runit

#35 Post by Richard »

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.
Thinkpad T430 & Dell Latitude E7450, both with MX-21.3.1
__kernal 5.10.0-26-amd64 x86_64; Xfce-4.18.0; 8 GB RAM
__Intel Core i5-3380M, Graphics, Audio, Video; & SSDs.
HP Ryzen 5 17-cp3xxx with MX23.4 AHS & Liquorix 6.10-12~mx23ahs amd64

User avatar
Head_on_a_Stick
Posts: 919
Joined: Sun Mar 17, 2019 3:37 pm

Re: Booting MX-19 with runit

#36 Post by Head_on_a_Stick »

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 :-)
mod note: Signature removed, please read the forum rules

User avatar
oops
Posts: 1885
Joined: Tue Apr 10, 2018 5:07 pm

Re: Booting MX-19 with runit

#37 Post by oops »

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)
Pour les nouveaux utilisateurs: Alt+F1 pour le manuel, ou FAQS, MX MANUEL, et Conseils Debian - Info. système “quick-system-info-mx” (QSI) ... Ici: System: MX-19_x64 & antiX19_x32

User avatar
Head_on_a_Stick
Posts: 919
Joined: Sun Mar 17, 2019 3:37 pm

Re: Booting MX-19 with runit

#38 Post by Head_on_a_Stick »

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 :confused:

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.
mod note: Signature removed, please read the forum rules

User avatar
oops
Posts: 1885
Joined: Tue Apr 10, 2018 5:07 pm

Re: Booting MX-19 with runit

#39 Post by oops »

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)
Pour les nouveaux utilisateurs: Alt+F1 pour le manuel, ou FAQS, MX MANUEL, et Conseils Debian - Info. système “quick-system-info-mx” (QSI) ... Ici: System: MX-19_x64 & antiX19_x32

Huckleberry Finn

Re: Booting MX-19 with runit

#40 Post by Huckleberry Finn »

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

Post Reply

Return to “Tips & Tricks by users”