[2024-feb-29] Sad news: Eric Layton aka Nocturnal Slacker aka vtel57 passed away on Feb 26th, shortly after hospitalization. He was one of our Wiki's most prominent admins. He will be missed.

Welcome to the Slackware Documentation Project

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
howtos:slackware_admin:runit [2019/09/17 04:20 (UTC)] – Reorder the headings and remove numbering. Numbering causes issues when reordering so removed. aadityahowtos:slackware_admin:runit [2019/09/17 04:57 (UTC)] – [4. How to replace init with runit] add more info and try to simplify it aaditya
Line 80: Line 80:
  
 ===== How to replace init with runit ===== ===== How to replace init with runit =====
 +
 +runit provides ''runit-init'' which can be used to boot up the system.
  
 If you followed the previous chapter, then stop runsvdir and reverse all the changes that you made on your system. If you followed the previous chapter, then stop runsvdir and reverse all the changes that you made on your system.
Line 188: Line 190:
 ==== Startup and Shutdown ==== ==== Startup and Shutdown ====
  
-The traditional init reads ''/etc/inittab'' file to see how to run the system. It runs the ''/etc/rc.d/rc.S'' script and runs it. If set in the default runlevel 3, it follows it with ''/etc/rc.d/rc.M''. In runit the initialisation script is located in ''/etc/runit/1'' for all runlevels. By default ''/etc/runit/2'' is restricted to the TTY services. +The bsd style init scripts provided by Slackware are used to bring up the system. 
 + 
 +Initially the single user script ''/etc/rc.d/rc.S'' runs. If set in the default runlevel 3, it follows it with ''/etc/rc.d/rc.M''. In runit the initialisation script is located in ''/etc/runit/1'' for all runlevels. By default ''/etc/runit/2'' is restricted to the TTY services. 
  
 The script ''/etc/rc.d/rc.6'' is the rebooting script for the traditional init, while ''/etc/rc.d/rc.0'' (symlinked to the former) is the halting script. In runit, these scripts are called by ''/etc/runit/3'' The script ''/etc/rc.d/rc.6'' is the rebooting script for the traditional init, while ''/etc/rc.d/rc.0'' (symlinked to the former) is the halting script. In runit, these scripts are called by ''/etc/runit/3''
Line 449: Line 453:
  
 Only one executable can be called for a service (the last line) and it must be called by the ''exec'' command. There are some generic runit run scripts on the Internet and on other Linux distributions. Also, other Slackers may post them on publicly available repositories. The author of this article has placed his here: https://gitlab.com/chrisabela/runit_scripts_for_slackware Only one executable can be called for a service (the last line) and it must be called by the ''exec'' command. There are some generic runit run scripts on the Internet and on other Linux distributions. Also, other Slackers may post them on publicly available repositories. The author of this article has placed his here: https://gitlab.com/chrisabela/runit_scripts_for_slackware
 +
 +Another set of installable run scripts are available at [[https://slackbuilds.org/repository/14.2/system/runit-services/|SBo]]. (currently pending)
  
 In direct contrast to Slackware's BSD style service scripts, runit run scripts must not must run in the foreground, otherwise runit would think that they have crashed and restart them. In direct contrast to Slackware's BSD style service scripts, runit run scripts must not must run in the foreground, otherwise runit would think that they have crashed and restart them.
Line 458: Line 464:
 </code> </code>
  
-Or you can use the ''pause'' command to keep the service alive. ''pause'' is a trivial command that will simply not exit, until it is killed (akin to tail -f /dev/null). A SlackBuild for ''pause'' is available at https://slackbuilds.org Then end the run script with:+Or you can use the ''pause'' command to keep the service alive. ''pause'' is a trivial command that will simply not exit, until it is killed (akin to tail -f /dev/null). A SlackBuild for ''pause'' is available at [[https://slackbuilds.org/repository/14.2/system/pause/|SBo]]. Then end the run script with:
  
 <code> <code>
Line 514: Line 520:
  
 It is stuggested to let ''udev'' under runit's stage 2, but you can setup its monitoring for stage 3.  It is stuggested to let ''udev'' under runit's stage 2, but you can setup its monitoring for stage 3. 
 +
 +===== Using runit-init with other init scripts =====
 +
 +==== OpenRC ====
 +
 +Here ''runit-init'' is used for booting, which then transfers control to the OpenRC init services for things like mounting the filesystem, loading modules, running udev, etc.
 +
 +It requires a working OpenRC system. Check the [[howtos:general_admin:openrc]] page on how it can be done.
 +The level 1 runit service uses the OpenRC ''boot'' and ''sysinit'' runlevels.
 +
 +Check the [[https://wiki.gentoo.org/wiki/Runit#Runit_as_the_init_system|gentoo wiki]] for more info, and [[https://gitlab.com/aadityabagga/runit-init-openrc|runit-init-openrc]] on how to install and set it up.
 +
 +==== void-runit ====
 +
 +Here the scripts provided by the [[https://github.com/void-linux/void-runit|void-runit]] project are used to mount the filesystem, load modules, etc.
 +
 +Currently this is the most independent way to setup runit.
  
 ===== Sources ===== ===== Sources =====
Line 534: Line 557:
  
 (9) https://wiki.gentoo.org/wiki/Runit (9) https://wiki.gentoo.org/wiki/Runit
 +
 +(10) https://github.com/void-linux/void-runit
  
   * Written for Slackware 14.2 in December 2018   * Written for Slackware 14.2 in December 2018

Trace:

howtos:slackware_admin:runit ()