7 init-ng is meant to be a drop-in replacement for Sys V init. It leverages the
8 mighty power of OpenRC to do only what's needed, and nothing more! It is still
9 somewhat experimental (hence written in Ruby) but works well. Currently, it
10 can reliably bring the system up, bring it down, and respawn agettys if they
13 init-ng can also be extended fairly easily as well; for those who want service
14 supervision or socket activation, these can be fairly easily added. There is
15 already some supervision capability built-in, as init-ng monitors the agettys
16 that it spawns; this can be extended to other services as well.
18 Note that while this init is written in Ruby, init-ng will eventually be
19 written in C. It's being developed in Ruby in order to make development and
26 • Make sure you have Ruby 2.1.x installed.
27 • Move your current init binary out of the way (mv /sbin/init /sbin/init.sysv)
28 • Copy the init script to /sbin (cp ./init /sbin/)
29 • Make sure /sbin/init is marked executable (chmod ugo+x /sbin/init)
32 Once you have rebooted successfully and logged in as root, typing 'init' on the
33 command line will display the commands that init-ng understands.
39 init-ng was initially written by James Hammons, who took his inspiration from
40 Felipe Contreras's blog post entitled "Demystifying the init system (PID 1)"
41 (https://felipec.wordpress.com/2013/11/04/init/). Felipe deserves most of the
42 credit for this, as without his article and code we wouldn't have known where