*** Welcome to piglix ***

Systemd

systemd
Debian Unstable Systemd Boot (2015).png
systemd startup on Debian Linux
Original author(s) Lennart Poettering, Kay Sievers, Harald Hoyer, Daniel Mack, Tom Gundersen and David Herrmann
Developer(s) Lennart Poettering, Kay Sievers, Harald Hoyer, Daniel Mack, Tom Gundersen, David Herrmann, and others
Initial release 30 March 2010; 6 years ago (2010-03-30)
Stable release 232 (November 3, 2016; 3 months ago (2016-11-03))
Preview release 230 (May 21, 2016; 9 months ago (2016-05-21))
Repository github.com/systemd/systemd.git
Development status Active
Written in C (executable components)
Proprietary INI-like (service files)
Operating system Linux
Type System software
Process supervisor
License GNU LGPL 2.1+
Website freedesktop.org/.../systemd/

systemd is an init system used in Linux distributions to bootstrap the user space and manage all processes subsequently, instead of the UNIX System V or Berkeley Software Distribution (BSD) init systems. It is published as free and open-source software under the terms of the GNU Lesser General Public License (LGPL) version 2.1 or later. One of systemd's main goals is to unify basic Linux configurations and service behaviors across all distributions.

As of 2015, a large number of Linux distributions have followed their parent Linux distributions such as Red Hat to adopt systemd as their default init system. The increasing adoption of systemd has been controversial, with critics arguing the software has violated the Unix philosophy by becoming increasingly complex, being based more heavily on a programming language that fewer people understand, and that distributions have been forced to adopt it due to the dependency of various other software upon it, including, most notably GNOME 3, a desktop environment.

The name systemd adheres to the Unix convention of naming daemons by appending the letter d.

Lennart Poettering and Kay Sievers, the software engineers working for Red Hat who initially developed systemd, sought to surpass the efficiency of the init daemon in several ways. They wanted to improve the software framework for expressing dependencies, to allow more processing to be done concurrently or in parallel during system booting, and to reduce the computational overhead of the shell.


...
Wikipedia

...