joborun/web
2
1
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Update 'runit-setup.md'

Browse source
This commit is contained in:
joborun linux 2022-04-06 20:30:40 +00:00
parent f9a9241101
commit f307c197fc
1 changed files with 17 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
runit-setup.md
View file

@ -9,12 +9,29 @@
runit is a suite of tools which provides an init (PID 1) as well as daemontools-compatible process supervision framework, along with utilites which modify the organization of services and daemons.
In our implimentation of runit we have made a few different choices to accomodate other needs. One is the aim to make a full runit setup coexist with s6/66. In this respect the 4 power functions (halt, poweroff, reboot, shutdown) have been moved to /usr/bin/run/ while the corresponding 66 functions have moved to /usr/bin/s6. To correct the functionality 4 of our own power scripts have been placed in /usr/local/bin/ with the same names, and independent of what the init is (runit or s6) the system will start the correct process. In addition, runit's pointer /sbin/init has been removed and in either grub or syslinux a parameter (init=/usr/bin/runit-init) will be required to start the system with runit. This is the default configuration in our grub setup. When and if 66/s6 bundle is added the parameter definig the init can be removed as 66 will store its own /usr/bin/init which is the kernel's default.
So one boot entry with init=/usr/bin/runit-init boots the system with runit one without boots s6/66.
Furthermore, as s6/66 respect the sys-admin and allow for custom work to be done within the etc ecosystem, particularly /etc/66, we have decided to leave /etc/runit/sv alone for the sys-admin to be creative. Our bundle of service scripts has been placed in /usr/lib/runit/sv to be either linked directly to /etc/runit/runsvdir/default or copied to /etc/runit/sv where they can be customized. Future packagin changes will not affect the /etc/runit/sv contents. The only exception to the ruls are the tty definitions that are owned by runit and runit-rc and will remain in this default location.
Last, we have made no changes to the stage 1 contents and setup. Just like artix and very similar to void's setup, anything affecting runit's stage 1 can be found in /etc/rc where 1,2,3 are defined.
#### Services and service scripts ####
As we don't promote handholding and system administration from above, the existence of runit service scripts don't come with their corresponding dependencies, with the exception of dhclient, wpa_supplicant, ntp, and dbus, which are part of the base package. For all other services to actually run, not only do you have to link the service file to runsvdir, you must also install the corresponding package that is run by the service manager. In other words, if you want sddm as a display manager, the service script is there and you can enable it, but you must also install sddm itslef.
References:
<a href="https://en.wikipedia.org/wiki/Runit">Wikipedia</a>
<a href="http://smarden.org/runit/">Runit Official Source</a>
<a href="https://wiki.artixlinux.org/Main/Runit">Artix</a>
<a href="https://docs.voidlinux.org/config/services/index.html">Void</a>
<a href="https://wiki.gentoo.org/wiki/Runit">Gentoo</a>
<a href="https://wiki.archlinux.org/title/runit">Arch</a>