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

add note about /sbin/init

This commit is contained in:
joborun linux 2023-09-18 13:20:25 +00:00
parent b8e6165002
commit 4790d9b7cc
1 changed files with 16 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
runit-setup.md
View File

@ -13,14 +13,28 @@
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.
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 rules are the tty definitions that are owned by runit and runit-rc and will remain in this default location /etc/runit/sv/.
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.
## If for some odd reason you make the decision to never use s6 ##
begin note: .... and since linux/unix should be about having choices about all aspects of the system, you can make a hard link to /sbin/init for /usr/bin/runit-init and then edit your boot loader (example grub:/etc/default/grub and remove the extra tag of init=/usr/bin/runit-init )
<pre>
cd /usr/bin
ln -sf /usr/bin/runit-init init
</pre>
In the same respect, if some day in the future you decide to install s6/66 suite, this link will present a conflict, so remove it again. init=/usr/bin/66-boot in boot-loading will be the same as its default link, only it will run in a sh environment and not in its native execlineb
.... end of note
#### To enable and start a service/daemon ####
Let us take dhcpcd as an example:
The service scripts for dhcpcd are stored in /usr/lib/runit/sv
The directory that runit parses to supervise services is /etc/runit/runsvdir/default
@ -59,3 +73,4 @@ References:
<a href="https://wiki.archlinux.org/title/runit">Arch</a>