You are not logged in.

#1 2024-12-31 11:59

globetrotterdk
Member
Registered: 2020-12-23
Posts: 67

Q4OS with runit.

I was motivated to work on this because systemd constantly irritated me with slow boot ups and system shutdowns. There are some issues with this install (note the comments!)

Devuan KDE guided install with separate /home directory and runit:

Comment out CD in /etc/apt/sources.list

If directories are lacking:
$ xdg-user-dirs-update

There were no sub-directories in my /home directory after first boot. My system could not achieve a graphical interface, probably as my computer has an Nvidia card, but I don't believe that the nouveau driver loaded either. So, I downloaded and installed the q4os script:

$ wget q4os.org/downloads/q4os-setup.sh
$ su (or sudo -s)
# sh q4os-setup.sh

Run the following after reboot to confirm running init system:
$ cat /proc/1/comm

runit is currently running on my system.

Current status is that while I have a running runit system, /var/log/boot contains the following error message:
"Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon failed!"
which could be why Discovery doesn't appear to be able to access a wired internet connection. Synaptic works fine.

When trying to install Nvidia drivers on a previous Devuan install (sysv init), dpkg exited with a #1 error. I as of yet have not installed the Nvidia drivers as I am trying to avoid the dpkg error again. It will be interesting to see how long I can do that... As a side note, the q4os system has yet to prompt me to install Nvidia drivers like it usually does... (The computer has an NVIDIA TU116 [GeForce GTX 1660 SUPER] gpu.)

Last edited by globetrotterdk (2024-12-31 12:03)


I’ve had a perfectly wonderful evening, but this wasn’t it. - Groucho Marx

Offline

#2 2024-12-31 15:36

globetrotterdk
Member
Registered: 2020-12-23
Posts: 67

Re: Q4OS with runit.

Here is a more in depth look at the resulting system after running the q4os script on a Devuan KDE runit install:

$ ps ax | grep run
    1 ?        Ss     0:00 runit
 1542 ?        Ss     0:00 runsvdir -P /etc/service log: .....................................................................................................................................................................................................................................................................................................................................check: 3: socklog-check: not found check: 3: socklog-check: not found 
 1593 ?        S      0:00 /usr/sbin/smartd --pidfile /var/run/smartd.pid
 1685 ?        Ss     0:00 runsv getty-tty4
 1686 ?        Ss     0:00 runsv cups
 1687 ?        Ss     0:00 runsv getty-ttyS0
 1688 ?        Ss     0:00 runsv dbus
 1689 ?        Ss     0:00 runsv dhclient
 1690 ?        Ss     0:00 runsv getty-tty3
 1691 ?        Ss     0:00 runsv anacron
 1692 ?        Ss     0:00 runsv cron
 1693 ?        Ss     0:00 runsv sddm
 1694 ?        Ss     0:00 runsv acpid
 1695 ?        Ss     0:00 runsv elogind
 1696 ?        Ss     0:00 runsv getty-tty6
 1697 ?        Ss     0:00 runsv getty-tty5
 1698 ?        Ss     0:00 runsv rsyslog
 1699 ?        Ss     0:00 runsv dbus.dep-fixer
 1700 ?        Ss     0:00 runsv getty-tty2
 1701 ?        Ss     0:00 runsv default-syslog
 1702 ?        Ss     0:00 runsv getty-tty1
 1706 ?        S      0:00 svlogd -tt -b 2048 /var/log/runit/dbus
 1709 ?        S      0:00 svlogd -tt -b 2048 /var/log/runit/sddm
 1712 ?        S      0:00 svlogd -tt -b 2048 /var/log/runit/dhclient
 1716 ?        S      0:00 svlogd -tt -b 2048 /var/log/runit/anacron
 1719 ?        S      0:00 svlogd -tt /var/log/runit/acpid
 1919 ?        S      0:00 avahi-daemon: running [host_computer.local]
 1924 tty7     Ssl+   0:00 /usr/lib/xorg/Xorg -nolisten tcp -auth /var/run/sddm/{5bc3cb32-6e3c-4fe0-ae1b-8f42736e3c47} -background none -noreset -displayfd 17 -seat seat0 vt7
 1980 ?        S      0:00 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant
 2112 ?        S      0:00 /usr/lib/x86_64-linux-gnu/sddm/sddm-helper --socket /tmp/sddm-auth5d07c714-2378-448c-b18f-637ebc26e64d --id 1 --start /usr/lib/x86_64-linux-gnu/libexec/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland --user brian
 2117 tty8     Ss+    0:00 dbus-run-session /usr/bin/startplasma-wayland
 2142 tty8     Sl+    0:03 /usr/bin/kwin_wayland --wayland-fd 7 --socket wayland-0 --xwayland-fd 8 --xwayland-fd 9 --xwayland-display :1 --xwayland-xauthority /run/user/1000/xauth_AViBbU --xwayland
 2163 tty8     Sl+    0:00 /usr/bin/Xwayland :1 -auth /run/user/1000/xauth_AViBbU -listenfd 49 -listenfd 50 -displayfd 41 -rootless -wm 44
 2328 tty8     S+     0:00 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 11 --address=unix:path=/run/user/1000/at-spi/bus_1
 2644 tty8     Sl+    0:00 /usr/lib/x86_64-linux-gnu/libexec/baloorunner
 2782 ?        Ss     0:00 fusermount3 -o rw,nosuid,nodev,fsname=portal,auto_unmount,subtype=portal -- /run/user/1000/doc
 3993 pts/1    S+     0:00 grep run

/etc/runit$ ls -1F runsvdir
current@
default/
default.run/
single/
solo/
svmanaged/

/etc/runit$ ls -1F runsvdir/default
acpid@
anacron@
cron@
cups@
dbus@
dbus.dep-fixer@
default-syslog@
dhclient@
elogind@
getty-tty1@
getty-tty2@
getty-tty3@
getty-tty4@
getty-tty5@
getty-tty6@
getty-ttyS0@
rsyslog@
sddm@

$ ls -F /etc/init.d
acpid*                   cups-browsed*           mountkernfs.sh*               saned*
alsa-utils*              dbus*                   mountnfs-bootclean.sh*        sddm*
anacron*                 elogind*                mountnfs.sh*                  seatd*
apparmor*                eudev*                  networking*                   sendsigs*
avahi-daemon*            gdomap*                 network-manager*              single*
bluetooth*               halt*                   openntpd                      smartmontools*
bootlogd*                hostname.sh*            procps*                       speech-dispatcher
bootlogs*                hwclock.sh*             pulseaudio-enable-autospawn*  stop-bootlogd*
bootmisc.sh*             keyboard-setup.sh*      rc@                           stop-bootlogd-single*
brightness*              killprocs*              rc.local*                     sudo*
checkfs.sh*              kmod*                   rcS@                          umountfs*
checkroot-bootclean.sh*  lm-sensors*             README@                       umountnfs.sh*
checkroot.sh*            mountall-bootclean.sh*  reboot*                       umountroot*
console-setup.sh*        mountall.sh*            rmnologin*                    unattended-upgrades*
cron*                    mount-configfs*         rsync*                        urandom*
cups*                    mountdevsubfs.sh*       rsyslog*                      x11-common*

avahi-daemon is clearly running, so something else must be preventing Discover from accessing the internet...

Last edited by globetrotterdk (2024-12-31 15:38)


I’ve had a perfectly wonderful evening, but this wasn’t it. - Groucho Marx

Offline

Board footer

Powered by FluxBB