====== OpenRC ======
OpenRC is a init system for Operational Systems GNU/Linux, GNU/Hurd and Unix, compatible with [[https://en.wikipedia.org/wiki/POSIX|Posix]]. Created by the Gentoo GNU/Linux developers team. Its purpose is to turn on/off and manage the services of the Operating System.

OpenRC emerged at the end of 2007 ((for more details go to: [[https://github.com/OpenRC/openrc/blob/master/HISTORY.md#openrc-history|OpenRC History]])), when Roy Marples retired as a Gentoo GNU/Linux developer. However, he wanted to keep the **baselayout-2** project as an independent project. The Gentoo Project Board has allowed it to continue to maintain it, so the project name should be modified, with OpenRC under the BSD license.

In 2010 OpenRC was retained by the developers of Gentoo GNU/Linux, after Roy Marples decided that it would not keep the project. William Hubbs and several other developers took over the OpenRC from this point, with 0.8.x being the first release made by the new team. In 2011 OpenRC returned to stable Gentoo GNU/Linux tree.

In 2013, the OpenRC team became independent from Gentoo GNU/Linux again and changed the primary development to the <color #B90B0B/#FFDDDD>Github</color>.
===== Features =====
OpenRC provides a number of interesting features:
  - Compatible with //UNIX// philosophy
  - Portable for non-GNU/Linux systems
  - Cgroups support
  - Parallel service initialization
  - Dependency based initialization
  - Automatic dependency calculation
  - Enables limiting/unlimited resources for each service
  - Sections of split configurations; **init.d** and **conf.d**
  - Well explained and explanatory configuration files
  - Startup scripts is extensible and customizable
  - Designed to be 100% compatible with virtualization environments
  - Modular architecture suitable and separate optional components; **Cron**, **syslog**...
  - Expressive and flexible network handling, including VPN
  - Verbose mode to debug service activity

===== Configuration =====
Configuring OpenRC is a simple task, this article offers some steps to optimize the use of this initialization system.
==== Boot logs ====
Open the configuration file <color #0B71B9/#DDF1FF>/etc/rc.conf</color> and uncomment the reference line <color #0B71B9/#DDF1FF>rc_logger="YES"</color>. The log files will be stored in <color #0B71B9/#DDF1FF>/var/log/rc.log</color>.
==== Hostname ====
To add or edit a host name, edit or create the file <color #0B71B9/#DDF1FF>/etc/conf.d/hostname</color> and add:
<code bash>
hostname="desired_name"
</code>
==== Keyboard ====
Modify the key map for use in the **console** edit the file <color #0B71B9/#DDF1FF>/etc/conf.d/consolefont</color>. See the full list of all the options available at <color #0B71B9/#DDF1FF>/usr/share/kbd/keymaps</color>
<code bash>
keymap="en_UK"
</code>
To configure the keyboard compatible with a **graphic interface** edit the file <color #0B71B9/#DDF1FF>/etc/conf.d/keymaps</color>. See the full list of all the options available at <color #0B71B9/#DDF1FF>/usr/share/kbd/keymaps</color>.
<code bash>
keymap="en_UK"
</code>
After editing the files, run the command:
<code bash>
# rc-service keymaps restart
</code>
==== Login manager ====
To enable the login manager, edit the <color #0B71B9/#DDF1FF>/etc/conf.d/xdm</color>. In the following example we take the slim as a base.
<code bash>
DISPLAYMANAGER="slim"
</code>
Enable the xdm daemon:
<code bash>
# rc-update add xdm default
</code>
==== Kernel modules ====
For the automatic loading of any module of the <color #0BB928/#DDFFE3>Kernel Linux-Libre</color> edit the file <color #0B71B9/#DDF1FF>/etc/conf.d/modules</color>.
<code bash>
modules="module_name"
</code>
This is only necessary after installation of an application or driver, made by the system administrator, by default all native modules of <color #0BB928/#DDFFE3>Kernel Linux-Libre</color> are loaded automatically.
==== Silent boot ====
To hide OpenRC messages during system startup, edit the file <color #0B71B9/#DDF1FF>/etc/inittab</color> and set the option to the OpenRC command:
<code bash>
--quiet
</code>
For more information:
<code bash>
$ openrc -h
</code>
===== Runlevels =====
OpenRC, as well as sysvinit and init (BSD), has a concept of task execution levels (Runlevels), to define them OpenRC uses names instead of numbers as it is done in the conventional way. This allows, for example, to have a default runlevel with "everything" enabled, and a "powersaving" runlevel where some services are disabled.

The <color #0B71B9/#DDF1FF>rc-status</color> helper will print all currently active runlevels and the state of services in them:

<code bash>
# rc-status
 * Caching service dependencies ... [ ok ]
Runlevel: default
 modules                     [  started  ]
 lvm                         [  started  ]
</code>

All runlevels are represented as folders in <color #0B71B9/#DDF1FF>/etc/runlevels/</color> with symlinks to the actual service scripts.

Calling openrc with an argument (<color #0B71B9/#DDF1FF>openrc default</color>) will switch to that runlevel; this will start and stop services as needed.

Managing runlevels is usually done through the <color #0B71B9/#DDF1FF>rc-update</color> helper, but could of course be done by hand if desired. e.g.
<color #0B71B9/#DDF1FF>rc-update add nginx default</color> - add nginx to the default runlevel with the need of root-privileges.

<note important>The command **rc-update** will not start nginx! You would still have to trigger rc, or run the service script by hand, or start it with **rc-service nginx start**.</note>

The default startup uses the runlevels <color #0B71B9/#DDF1FF>sysinit</color>, <color #0B71B9/#DDF1FF>boot</color>, and <color #0B71B9/#DDF1FF>default</color>, in that order. Shutdown uses the <color #0B71B9/#DDF1FF>shutdown</color> runlevel. The defined runlevel <color #0B71B9/#DDF1FF>nonetwork</color> is used only for non-network services.
====== OpenRC ======

Since Hyperbola has announced the [[https://www.hyperbola.info/news/end-of-systemd-support/|end of systemd support]], OpenRC is our main used init system and with release 0.4 we have also included further support for Runit.

===== What is OpenRC? =====

[[https://wiki.gentoo.org/wiki/OpenRC|OpenRC]] is a dependency based [[https://en.wikipedia.org/wiki/Init|init]] system maintained by the Gentoo developers, that works with the system provided init program, normally SysVinit.

===== Warning =====

<note warning>Please read the whole warning</note>

<color #620BB9/#EEDDFF>netctl</color> works with systemd only, therefore it will not work anymore from Milky Way v0.2 since OpenRC is the main init system of Hyperbola. We will assume you already have an alternative, in our case, it is [[https://www.hyperbola.info/packages/?q=netifrc|netifrc]].

===== Groups =====

Before Arch migrated to systemd, users had to be manually added to some groups in order to be able to access the corresponding devices. Read more about [[https://wiki.archlinux.org/index.php/Users_and_groups#Group_list|here]].

Make sure your user is on the <color #620BB9/#EEDDFF>audio</color> group, you won't have sound otherwise:

<code bash>
# gpasswd -a <your-user> audio
</code>

Same for video, your games might be laggy otherwise:

<code bash>
# gpasswd -a <your-user> video
</code>

For networking:

<code bash>
# gpasswd -a <your-user> network
</code>

For webcam:

<code bash>
# gpasswd -a <your-user> optical
</code>

Also for storage:

<code bash>
# gpasswd -a <your-user> storage
</code>

<code bash>
# gpasswd -a <your-user> disk
</code>

And for CUPS:

<code bash>
# gpasswd -a <your-user> sys
</code>

<note>First try these features before adding your user to these groups, for example, in some cases adding your user to the <color #620BB9/#EEDDFF>optical</color> group may not be necessary.</note>

===== Migration =====

<note important> Be aware that since the release of version 0.4 we do not recommend any kind of migration from another system based onto Arch GNU/Linux. Since Hyperbola has included many changes and therefore differences it would be better to install the system from scratch with all changes you wish.</note>

===== Configuration =====

==== Services often required ====

Once you migrate to OpenRC, you might need to add <color #620BB9/#EEDDFF>lvm2</color> etc.

There is the procedure for [[https://www.hyperbola.info/packages/?q=lvm2|lvm2]]:

<code bash>
# rc-update add lvm boot
</code>

For [[https://www.hyperbola.info/packages/?q=cryptsetup|cryptsetup]]:

<code bash>
# rc-update add dmcrypt boot
</code>

For [[https://www.hyperbola.info/packages/?q=alsa-utils|alsa-utils]]:

<code bash>
# rc-update add alsasound default
</code>

For [[https://www.hyperbola.info/packages/?q=cronie|cronie]]:

<code bash>
# rc-update add cronie default
</code>

On each package containing an OpenRC service, you will have have this message :

<code bash>
      ==> rc 'rc-update add ... default'
</code>
==== Hostname ====

OpenRC has its configuration in <color #0B71B9/#DDF1FF>/etc/conf.d/</color>, in order to have your hostname, edit <color #0B71B9/#DDF1FF>/etc/conf.d/hostname</color>:

<code bash>
# nano -w /etc/conf.d/hostname
</code>

And replace <color #0B71B9/#DDF1FF>localhost</color> with the name that you want:

<code>
# Set to the hostname of this machine
hostname="localhost"
</code>

==== Network settings ====

You need to enable the daemon <color #620BB9/#EEDDFF>dhcpcd</color> at runlevel default:

<code bash>
# rc-update add dhcpcd default
</code>

==== Kepmap ====

As the hostname, you need to setup the keymap in the file <color #0B71B9/#DDF1FF>/etc/conf.d/keymaps</color>: 

<code>
keymap="us"
</code>

If you have an advanced usage of your keymap, you can watch the other functionalities, documented in the comments. You can find all the available keymaps in <color #0B71B9/#DDF1FF>/usr/share/kbd/keymaps</color>. Then run:

<code bash>
# rc-service keymaps restart
</code>

<note>This only applies for CLI, is you are using X11, this won't affect your graphical environment.</note>

==== Login display manager ====

Unlike another distros with OpenRC support, the DM is launched directly.

For example, with <color #620BB9/#EEDDFF>wdm</color>, you just need enable the service.

<code bash>
# rc-update add wdm default
</code>

===== Adaptation between systemctl and rc-update =====

==== Add or delete a service ====

You can add a service using this way:

<code bash>
# rc-update add <service> <runlevel>
</code>

And delete it as follow:

<code bash>
# rc-update del <service> <runlevel>
</code>

==== Services currently running ====

In order to have a summary of all the services running, stopped etc, you can run this command:

<code bash>
# rc-status --all -v
</code>

==== Stop/Start/Restart a service ====

To restart a service, you need to use <color #620BB9/#EEDDFF>rc-service</color>:

<code bash>
# rc-service <service> restart
</code>

===== Troubleshooting =====

==== Consistent network device naming is not disabled ====

To disable consistent network device naming, disable the assignment of fixed names, so that the unpredictable kernel names are used again, by masking <color #0BB928/#DDFFE3>udev</color>'s rule file for the default policy. This **“masking”** can be done by making a symbolic link to <color #0B71B9/#DDF1FF>/dev/null</color>. As root, issue a command as follows:

<code bash>
# ln -s /dev/null /lib/udev/rules.d/80-net-name-slot.rules
</code>

==== Sysctl.conf is missing ====

You can encounter an issue if <color #0B71B9/#DDF1FF>/etc/sysctl.conf</color> is missing. To fix this, you need to create the file:

<code bash>
# touch /etc/sysctl.conf
</code>

==== /usr/libexec/rc/cache doesn't exist ====

If you have this error when you shutdown the computer:

<code bash>
WARNING: /usr/libexec/rc/cache is not writable!
</code>

The solution is to create the folder:

<code bash>
# mkdir /usr/libexec/rc/cache
</code>

==== Swap isn't enabled ====

Systemd used to mount the swap automatically, you need to manually add the swap in <color #0B71B9/#DDF1FF>/etc/fstab</color> as follow:

<code bash>
# /dev/sda2
UUID=0c3e9434-bc5c-461c-a5e4-4e9fe5f9a149	swap	swap	sw	0	0
</code>

==== tmpfs isn't present ====

As the swap, systemd automatically mounts the tmpfs. Add it manually in <color #0B71B9/#DDF1FF>/etc/fstab</color>:

<code bash>
tmpfs		/tmp		tmpfs   nodev,nosuid          	0  	0
</code>

==== The system can't shutdown correctly ====

Begin with OpenRC 0.28 SysVinit is replaced with openrc-init, shutdown is replaced with openrc-shutdown. If you use <color #620BB9/#EEDDFF>startx</color> to start your desktop, you also need to modify <color #0B71B9/#DDF1FF>~/.xinitrc</color> when you have issues with your window-manager starting correctly.

===== Acknowledgement =====

This wiki article is based on **[[https://wiki.parabola.nu/|ParabolaWiki]]**.