In Unix-based computer operating systems, init (short for initialization) is the first process started during booting of the computer system. Init is a daemon process that continues running until the system is shut down. It is the direct or indirect ancestor of all other processes and automatically adopts all orphaned processes. Init is started by the kernel using a hard-coded filename. A kernel panic will occur if the kernel is unable to start it. Init is typically assigned process identifier 1.
The design of init has diverged in Unix systems such as System III and System V, from the functionality provided by the init in Research Unix and its BSD derivatives. The usage on most Linux distributions is somewhat compatible with System V, but some distributions, such as Slackware, use a BSD-style and others, such as Gentoo, have their own customized version.
Several replacement init implementations have been written with attempt to address design limitations in the standard versions. These include launchd, the Service Management Facility, systemd and Upstart, the latter being used by Ubuntu and some other Linux distributions.
Research Unix init ran the initialization shell script located in
/etc/rc, then launched getty on terminals under the control of
/etc/ttys. There are no runlevels; the
/etc/rc file determines what programs are run by init. The advantage of this system is that it is simple and easy to edit manually. However, new software added to the system may require changes to existing files that risk producing an unbootable system.
BSD init was, prior to 4.3BSD, the same as Research UNIX's init; in 4.3BSD, it added support for running a windowing system such as X on graphical terminals under the control of
/etc/ttys. To remove the requirement to edit
/etc/rc, BSD variants have long supported a site-specific
/etc/rc.local file that is run in a sub-shell near the end of the boot sequence.
A fully modular system was introduced with NetBSD 1.5 and ported to FreeBSD 5.0 and successors. This system executes scripts in the
/etc/rc.d directory. Unlike System V's script ordering, which is derived from the filename of each script, this system uses explicit dependency tags placed within each script. The order in which scripts are executed is determined by the rcorder script based on the requirements stated in these tags.
System V init examines the
/etc/inittab file for an
:initdefault: entry, which defines any default runlevel. If there is no default runlevel, then
init dumps the user to a system console for manual entry of a runlevel.
Aside from these, every Unix and Unix-like system treats runlevels a little differently. The common denominator, the
/etc/inittab file, defines what each runlevel does (if they do anything at all) in a given system.
|Operating System||Default runlevel|
|CentOS||3 (console/server) or 5 (graphical/desktop)|
|HP-UX||3 (console/server/multiuser) or 4 (graphical)|
|Mac OS X||3|
|Mandriva Linux||3 (console/server) or 5 (graphical/desktop)|
|Red Hat Enterprise Linux / Fedora||3 (console/server) or 5 (graphical/desktop)|
|SUSE Linux Enterprise/openSUSE Linux||3 (console/server) or 5 (graphical/desktop)|
|Ubuntu (Server and Desktop)||2|
On the Linux distributions defaulting to runlevel 5 in the table above, runlevel 5 invokes a multiuser graphical environment running the X Window System, usually with a display manager like GDM or KDM. However, the Solaris operating system typically reserves runlevel 5 to shut down and automatically power off the machine.
On most systems users can check the current runlevel with either of the following commands:
$ who -r
The root typically changes the current runlevel by running the
init commands. The
/etc/inittab file sets the default runlevel with the
On Unix systems, changing the runlevel is achieved by starting only the missing services (as each level defines only those that are started / stopped). For example, changing a system from runlevel 3 to 4 might only start the local X server. Going back to runlevel 3, it would be stopped again.
Replacements for init
Traditionally, one of the major drawbacks of init is that it starts tasks serially, waiting for each to finish loading before moving on to the next. When startup processes end up I/O blocked, this can result in long delays during boot.
Various efforts have been made to replace the traditional init daemons to address this and other design problems, including:
- BootScripts in GoboLinux
- busybox-init, suited embedded operating systems, employed by OpenWrt before it was replaced with procd
- DEMONS, a modification of the init start process by KahelOS, where daemons are started only when the DE (desktop environment) started
- eINIT, a full replacement of init designed to start processes asynchronously, but with the potential of doing it without shell scripts.
- Initng, a full replacement of init designed to start processes asynchronously
- launchd, a replacement for init introduced in Mac OS X v10.4 (it launches SystemStarter to run old-style 'rc.local' and SystemStarter processes)
- Mudur, an init replacement written in Python and designed to start process asynchronously in use by the Pardus Linux distribution.
- runit, a cross-platform full replacement for init with parallel starting of services
- s6, another cross-platform full replacement for init, similar to runit
- Epoch, a single-threaded Linux init system focused on simplicity and service management
- Service Management Facility, a complete full replacement/redesign of init from the ground up in Solaris starting with Solaris 10
- systemd, a full replacement for init with parallel starting of services and other features, used by many distributions.
- SystemStarter, a process spawner started by the BSD-style init in Mac OS X prior to Mac OS X v10.4
- Upstart, a full replacement of init designed to start processes asynchronously initiated by Ubuntu.
- "Know Thy Ubuntu". Help.ubuntu.com. 2009-08-07. Retrieved 2011-06-13.
- "since we have no /etc/inittab". Linuxquestions.org. 30 November 2006. Retrieved 2011-06-13.
- "Upstart Plans to Ease Linux Management — Streamlining the init Processes". Reports. LinuxPlanet. 2007-03-08. Retrieved 2011-06-13.
- Remnant, Scott James (2006-08-26). "Upstart in Universe". Netsplit.com. Retrieved 2011-06-13.
- Version 7 Unix Programmer's Manual –
- Version 7 Unix Programmer's Manual –
- 4.2BSD System Manager's Manual –
- 4.2BSD File Formats Manual –
- 4.3BSD System Manager's Manual –
- 4.3BSD File Formats Manual –
- Andrew Smallshaw (7 December 2009). "Unix and Linux startup scripts, Part 2".
- "SysV Init Runlevels". Retrieved 22 September 2012.
- "Debian and Ubuntu Linux Run Levels". Debianadmin.com. 2009-04-02. Retrieved 2011-06-13.
- "Initscripts". Gentoo Linux Documentation. Gentoo.org. 2011-03-02. Retrieved 2011-06-13.
- "Oracle Documentation". Docs.sun.com. 2010-09-07. Retrieved 2011-06-13.
- "SUSE Documentation: The init Process". suse.com. 2014-04-25. Retrieved 2014-05-04.
- "UNIX man pages : runlevel (8)". Unixhelp.ed.ac.uk. 1997-05-27. Retrieved 2014-07-12.
- "eINIT git repository XML module directory".
- Gürer Özen, Görkem Çetin. "Speeding Up Linux: One Step Further With Pardus Pardus". Pardus.org.tr. Retrieved 2011-06-13.
- "s6 - skarnet's small supervision suite".
- "Epoch Init System Homepage".