OpenRC

OpenRC is a dependency based init system that works with the system provided init program, normally /sbin/init. It is not a replacement for /sbin/init. OpenRC is 100% compatible with Gentoo init scripts, which means you can probably find one for the daemons you want to start in the Gentoo Portage Tree. OpenRC, however, is not exclusively used by Gentoo Linux and can be used on different Linux and BSD systems.

Features
OpenRC provides a number of features touted as innovative by recent init systems like systemd or upstart, such as hardware initiated initscript run or cgroups support, without requiring large layout changes to accomodate radically different designs and dependencies.

The tabular comparison appears to be biased negatively against sysvinit and upstart. It is copied from the systemd website.

OpenRC bonus features:

Size and complexity
OpenRC (0.9.3): sysvinit + 300 files, ~30k lines, 3.3k posix sh, ~12k C

Upstart (1.5): 285 files, ~185k lines, ~97k C

Debian: sysvinit + 120 files, 5.8k lines

SystemD (v44+): dbus + glib + 900 files, 224k lines, 125k C

sysvinit: 560kB, 75 files, ~15k lines

DBus: 11MB, ~500 files. 300k lines, 120k C

glib: 72MB, ~2500 files, ~1.7M lines, ~430k C

Debian startup is smallest, it's only shell with sysvinit (C) as dependency

Upstart is about 10 times bigger in terms of lines of code/text. Most of the extra complexity size comes from C.

OpenRC is about twice as big as debian startup. The size difference is mostly the OpenRC core written in C, which expands the footprint from ~3k LoC to ~15k LoC compared to shell.

SystemD is about 10 times bigger, like upstart. But with the mandatory deps it blows up to about one hundred times the code footprint! Most of the extra code is in mandatory dependencies, but the systemd core is also bigger than anything else.

OpenRC Busybox Integration
Busybox can be used replace most of the userspace needed by OpenRC (init, shell, awk and other posix tools), by using a complete busybox as shell for openrc all the calls that normally would cause a fork/exec would be spared, improving the overall speed. The process isn't yet streamlined.

Replacing init
The sysvinit inittab provided by Gentoo is not compatible to the busybox init.

In order to set a specific runlevel from the bootloader the variable `softlevel=` should be used.

busybox specific init.d files
TODO: busybox provides a number of applets that could be used to replace third party software like acpid or dhcp/dhcpcd.

Replacing udev with mdev
See Mdev

Using runlevels
OpenRC can be controlled and configured using rc, rc-update and rc-status.

Named runlevels
OpenRC runlevels are directories living in "/etc/runlevels" to create additional runlevels is enough to issue

Stacked runlevels
Is possible manage variants using rc-update -s

Prefix usage
Gentoo Prefix installs Gentoo within an offset, known as a prefix, allowing users to install Gentoo in another location in the filesystem hierarchy, hence avoiding conflicts. Next to this offset, Gentoo Prefix runs unprivileged, meaning no root user or rights are required to use it.

By using an offset (the "prefix" location), it is possible for many "alternative" user groups to benefit from a large part of the packages in the Gentoo Linux Portage tree. Currently users of the following systems successfully run Gentoo Prefix: Mac OS X on PPC and x86, Linux on x86, x86_64 and ia64, Solaris 10 on Sparc, Sparc/64, x86 and x86_64, FreeBSD on x86, AIX on PPC, Interix on x86, Windows on x86 (with the help of Interix), HP-UX on PARISC and ia64.

OpenRC runscript already support prefix-installed daemons, during the SummerOfCode2012 work will be done to implement full secondary/session daemon behaviour to complete the overall featureset provided by Prefix.

OpenRC/Prefix, a tutorial for trying it out.

Other Usages

 * stateful init scripts and automatic respawning (run "rc")