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! Currently,
9 it can reliably bring the system up, bring it down three different ways, and
10 respawn agettys if they die.
12 init-ng can also be extended fairly easily as well; for those who want service
13 supervision or socket activation, these can be fairly easily added. There is
14 already some supervision capability built-in, as init-ng monitors the agettys
15 that it spawns; this can be extended to other services as well.
21 First, run 'make' to create the init-ng binary. Then, there are two main ways
22 to install it. First way:
24 • Move your current init binary out of the way (mv /sbin/init /sbin/init.sysv)
25 • Copy the init-ng binary to /sbin (cp ./init-ng /sbin/init)
30 • Copy the init-ng binary to /sbin (cp ./init-ng /sbin/)
31 • Add a kernel parameter with 'init=/sbin/init-ng' (without the quotes) to
32 your current kernel boot command line
35 Once you have rebooted successfully and logged in as root, typing 'init' (or
36 'init-ng', if you installed the second way) on the command line will display
37 the commands that init-ng understands.
43 init-ng was initially written by James Hammons, who took his inspiration from
44 Felipe Contreras's blog post entitled "Demystifying the init system (PID 1)"
45 (https://felipec.wordpress.com/2013/11/04/init/). Felipe deserves most of the
46 credit for this, as without his article and code we wouldn't have known where