Systemd

Quality 0.50 · 2 views · Updated 2 months ago

Suite of system components for Linux

title: "Systemd" type: doc version: 1 created: 2026-02-28 author: "Wikipedia contributors" status: active scope: public tags: ["freedesktop.org", "linux-kernel-related-software", "linux-only-free-software", "software-that-uses-meson", "unix-process--and-task-management-related-software", "network-time-related-software"] description: "Suite of system components for Linux" topic_path: "technology/operating-systems" source: "https://en.wikipedia.org/wiki/Systemd" license: "CC BY-SA 4.0" wikipedia_page_id: 0 wikipedia_revision_id: 0

::summary Suite of system components for Linux ::

::data[format=table title="Infobox software"]

FieldValue
namesystemd
logoSystemd-logo.svg
logo_size200px
logo altsystemd logo, showing green circle and reverse symbol enclosed by bracket
screenshotSystemd-on-fedora.svg
screenshot altsystemd on Fedora 17 showing multiple component startups
captionsystemd startup on Fedora 17
authorLennart Poettering
developerRed Hat (Lennart Poettering, Kay Sievers, Harald Hoyer, Daniel Mack, Tom Gundersen, David Herrmann); 345 different authors in 2018{{cite web
titleSystemd Hits A High Point For Number Of New Commits & Contributors During 2018 - Phoronix
urlhttps://www.phoronix.com/scan.php?page=news_item&px=Systemd-EOY2018-Stats
access-date30 December 2018
archive-date21 September 2009
archive-urlhttps://web.archive.org/web/20090921053923/https://www.phoronix.com/scan.php?page=news_item&px=Systemd-EOY2018-Stats
url-statuslive
}} and 2,032 different authors in total Used the "contributors" statistic from: {{Citationtitle
released
latest release version
latest release date
programming languageC
operating systemLinux
genre
licenseLGPLv2.1+
website
::

| name = systemd | logo = Systemd-logo.svg | logo_size = 200px | logo alt = systemd logo, showing green circle and reverse symbol enclosed by bracket | screenshot = Systemd-on-fedora.svg | screenshot alt = systemd on Fedora 17 showing multiple component startups | caption = systemd startup on Fedora 17 | author = Lennart Poettering | developer = Red Hat (Lennart Poettering, Kay Sievers, Harald Hoyer, Daniel Mack, Tom Gundersen, David Herrmann); 345 different authors in 2018{{cite web |title=Systemd Hits A High Point For Number Of New Commits & Contributors During 2018 - Phoronix |url=https://www.phoronix.com/scan.php?page=news_item&px=Systemd-EOY2018-Stats |access-date=30 December 2018 |archive-date=21 September 2009 |archive-url=https://web.archive.org/web/20090921053923/https://www.phoronix.com/scan.php?page=news_item&px=Systemd-EOY2018-Stats |url-status=live | released = | latest release version = | latest release date = | programming language = C | operating system = Linux | platform = | language = | genre = | license = LGPLv2.1+ | website =

systemd is a software suite for system and service management on Linux built to unify service configuration and behavior across Linux distributions. Its main component is an init system used to bootstrap user space and manage user processes. It also provides replacements for various daemons and utilities, including device management, login management, network connection management, and event logging. The name systemd adheres to the Unix convention of naming daemons by appending the letter d, and also plays on the French phrase Système D (a person's ability to quickly adapt and improvise in the face of problems).

Since 2015, nearly all Linux distributions have adopted systemd. It has been praised by developers and users of distributions that adopted it for providing a stable, fast out-of-the-box solution for issues that had existed in the Linux space for years. At the time of its adoption, it was the only parallel boot and init system offering centralized management of processes, daemons, services, and mount points .

Critics of systemd contend it suffers from feature creep and has damaged interoperability across Unix-like operating systems (as it does not run on non-Linux Unix derivatives like BSD or Solaris). In addition, they contend systemd's large feature set creates a larger attack surface. This has led to the development of several minor Linux distributions replacing systemd with other init systems like SysVinit or OpenRC.

History

Lennart Poettering and Kay Sievers, the software engineers then working for Red Hat who initially developed systemd, started a project to replace Linux's conventional System V init in 2010. | last1 = Simmonds | first1 = Chris | chapter = 9: Starting up - the init Program | title = Mastering Embedded Linux Programming | url = https://books.google.com/books?id=_h_lCwAAQBAJ | publisher = Packt Publishing Ltd | date = 2015 | page = 239 | isbn = 9781784399023 | access-date = 20 June 2016 | quote = systemd defines itself as a system and service manager. The project was initiated in 2010 by Lennart Poettering and Kay Sievers to create an integrated set of tools for managing a Linux system including an init daemon. An April 2010 blog post from Poettering, titled "Rethinking PID 1", introduced an experimental version of what would later become systemd. They 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 processes to run concurrently or in parallel during system booting, and to reduce the computational overhead of the shell.

In May 2011, Fedora Linux became the first major Linux distribution to enable systemd by default, replacing Upstart. The reasoning at the time was that systemd provided extensive parallelization during startup, better management of processes and overall a saner, dependency-based approach to control of the system.

In October 2012, Arch Linux made systemd the default, switching from SysVinit. Developers had debated since August 2012 and concluded it was faster and had more features than SysVinit and that maintaining SysVinit was not worth the effort. Some thought the criticism of systemd was not based on actual shortcomings of the software but rather personal dislike of Poettering and a general opposition to change. Several complaints about systemd—including its use of D-bus, C instead of bash, and an optional on-disk journal format—were instead described as advantages by the Arch maintainers.

Between 2013 and 2014, the Debian Technical Committee engaged in a widely publicized debate on the mailing list about which init system to use as the default in Debian 8 before settling on systemd. Soon after, Debian developer Joey Hess, Technical Committee members Russ Allbery and Ian Jackson, and systemd package maintainer Tollef Fog Heen resigned from their positions, citing the extraordinary levels of stress caused by disputes on systemd integration within the Debian and FOSS community that rendered regular maintenance virtually impossible. Mark Shuttleworth announced soon afterwards that the Debian-based Ubuntu would use systemd to replace its old Upstart init system.

In August 2015, systemd started providing a login shell, callable via ****.

In September 2016, a security bug was discovered that allowed any unprivileged user to perform a denial-of-service attack against systemd. Rich Felker, developer of musl, stated that this bug reveals a major "system development design flaw". In 2017 another security bug was discovered in systemd-resolved, , which "allows disruption of service" by a "malicious DNS server".{{Citation |website = National Vulnerability Database |institution = National Institute of Standards and Technology (U.S.) |title = CVE-2017-9445 Details |url = https://nvd.nist.gov/vuln/detail/CVE-2017-9445 |date = 6 July 2017 |access-date = 6 July 2018 |archive-date = 6 July 2018 |archive-url = https://web.archive.org/web/20180706075415/https://nvd.nist.gov/vuln/detail/CVE-2017-9445 |url-status = live |website = The Common Vulnerabilities and Exposures database |date = 5 June 2017 |institution = The Mitre Corporation |title = CVE-2017-9445 |url = https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9445 |access-date = 6 July 2018 |archive-date = 6 July 2018 |archive-url = https://web.archive.org/web/20180706075607/https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9445 |url-status = live

Design

::figure[src="https://upload.wikimedia.org/wikipedia/commons/3/35/Systemd_components.svg" caption="The architecture of systemd as it is used by [[Tizen]]. Several systemd targets, including telephony, bootmode, dlog, and tizen service are from Tizen and are not components of systemd."] ::

::figure[src="https://upload.wikimedia.org/wikipedia/commons/e/e7/Linux_kernel_unified_hierarchy_cgroups_and_systemd.svg" caption="publisher=Freedesktop.org}}"] ::

Poettering describes systemd development as "never finished, never complete, but tracking progress of technology". In May 2014, Poettering further described systemd as unifying "pointless differences between distributions", by providing the following three general functions:

  • A system and service manager (manages both the system, by applying various configurations, and its services)
  • A software platform (serves as a basis for developing other software)
  • The glue between applications and the kernel (provides various interfaces that expose functionalities provided by the kernel)

includes features like on-demand starting of daemons, snapshot support, process tracking and Inhibitor Locks. It is not just the name of the init daemon but also refers to the entire software bundle around it, which, in addition to the init daemon, includes the daemons , and , and many other low-level components. In January 2013, Poettering described systemd not as one program, but rather a large software suite that includes 69 individual binaries. As an integrated software suite, systemd replaces the startup sequences and runlevels controlled by the traditional init daemon, along with the shell scripts executed under its control. systemd also integrates many other services that are common on Linux systems by handling user logins, the system console, device hotplugging (see udev), scheduled execution (replacing cron), logging, hostnames and locales.

Like the init daemon, is a daemon that manages other daemons, which, including itself, are background processes. is the first daemon to start during booting and the last daemon to terminate during shutdown. The daemon serves as the root of the user space's process tree; the first process (PID 1) has a special role on Unix systems, as it replaces the parent of a process when the original parent terminates. Therefore, the first process is particularly well suited for the purpose of monitoring daemons.

executes elements of its startup sequence in parallel, which is theoretically faster than the traditional startup sequence approach. For inter-process communication (IPC), makes Unix domain sockets and D-Bus available to the running daemons. The state of itself can also be preserved in a snapshot for future recall.

Core components and libraries

Following its integrated approach, systemd also provides replacements for various daemons and utilities, including the startup shell scripts, pm-utils, inetd, , syslog, watchdog, cron and . systemd's core components include:

  • is a system and service manager for Linux operating systems.
  • is a command to introspect and control the state of the systemd system and service manager. Not to be confused with sysctl.
  • may be used to determine system boot-up performance statistics and retrieve other state and tracing information from the system and service manager.

NSPAWN tracks processes using the Linux kernel's cgroups subsystem instead of using process identifiers (PIDs); thus, daemons cannot "escape" , not even by double-forking. not only uses cgroups, but also augments them with and , two utility programs that facilitate the creation and management of Linux containers. Since version 205, systemd also offers ControlGroupInterface, which is an API to the Linux kernel cgroups. The Linux kernel cgroups are adapted to support kernfs, and are being modified to support a unified hierarchy.

Ancillary components

Beside its primary purpose of providing a Linux init system, the systemd suite can provide additional functionality, including the following components: Further expansions should include descriptions of hostnamed, localed, machined, resolved, shutdownd, and timesyncd. --[[File:Systemd-boot on Arch Linux.png|thumb|A screenshot of ]] ::figure[src="https://upload.wikimedia.org/wikipedia/commons/4/40/Timedatectl_screenshot.png" caption="timedatectl}}"] ::

; : is a daemon responsible for event logging, with append-only binary files serving as its logfiles. The system administrator may choose whether to log system events with , or . The potential for corruption of the binary format has led to much heated debate. ; : is the standard library for utilizing udev, which allows third-party applications to query udev resources. ; : manages the system locale and keyboard layout. ; CK : is a daemon that manages user logins and seats in various ways. It is an integrated login manager that offers multiseat improvements and replaces ConsoleKit, which is no longer maintained. For X11 display managers the switch to requires a minimal amount of porting. It was integrated in systemd version 30. ; : manages the system hostname. ; : is a daemon that provides portable human-user accounts that are independent of current system configuration. moves various pieces of data such as UID/GID from various places across the filesystem into one file, . manages the user's home directory in various ways such as a plain directory, a btrfs subvolume, a Linux Unified Key Setup volume, an fscrypt directory, or mounted from an SMB server. ; : is a daemon to handle the configuration of the network interfaces; in version 209, when it was first integrated, support was limited to statically assigned addresses and basic support for bridging configuration. In July 2014, systemd version 215 was released, adding new features such as a DHCP server for IPv4 hosts, and VXLAN support. networkctl may be used to review the state of the network links as seen by systemd-networkd. Configuration of new interfaces has to be added under the /lib/systemd/network/ as a new file ending with .network extension. ; : provides network name resolution to local applications ; : is a boot manager, formerly known as gummiboot. Kay Sievers merged it into systemd with rev 220. ; : is an error reporter used to generate Blue Screen of Death. ; : may be used to run a command or OS in a namespace container.

; : is a daemon that can be used to control time-related settings, such as the system time, system time zone, or selection between UTC and local time-zone system clock. It is accessible through D-Bus. It was integrated in systemd version 30. ; : is a client NTP daemon for synchronizing the system clock across the network. ; : is a utility that takes care of creation and clean-up of temporary files and directories. It is normally run once at startup and then in specified intervals. ; : udev is a device manager for the Linux kernel, which handles the directory and all user space actions when adding/removing devices, including firmware loading. In April 2012, the source tree for udev was merged into the systemd source tree. In order to match the version number of udev, systemd maintainers bumped the version number directly from 44 to 183. : On 29 May 2014, support for firmware loading through udev was dropped from systemd, as it was decided that the kernel should be responsible for loading firmware.

Configuration of systemd

::figure[src="https://upload.wikimedia.org/wikipedia/commons/5/5e/Systemd_manager.png" caption="systemd-manager, a tool to configure systemd" alt=""] ::

is configured exclusively via plain-text files although GUI tools such as systemd-manager are also available.

records initialization instructions for each daemon in a configuration file (referred to as a "unit file") that uses a declarative language, replacing the traditionally used per-daemon startup shell scripts. The syntax of the language is inspired by files.

Unit-file types include:

  • (automatically initiated by systemd)
  • (which can be used as a cron-like job scheduler)
  • (used to group and manage processes and resources{{cite web |url= https://www.systutorials.com/docs/linux/man/5-systemd.slice/ |title= systemd.slice (5) - Linux Man Pages |access-date= 12 March 2018 |quote= ... a slice ... is a concept for hierarchically managing resources of a group of processes. |archive-date= 19 February 2023 |archive-url= https://web.archive.org/web/20230219165506/https://www.systutorials.com/docs/linux/man/5-systemd.slice/ |url-status= live
  • (used to group worker processes, not intended to be configured via unit files)

Adoption

::data[format=table]

Linux distributionDate added to software repositoryEnabled by default?Date released as defaultRuns without?
Alpine Linux
Android
Arch Linux
antiX Linux
Artix Linux
CentOS(v7.0)
CoreOS(v94.0.0)
Debian(v8.0). In bullseye, a number of alternative init systems are supported
Devuan
Fedora Linux(v14)(v15)
Gentoo Linux
GNU Guix System
Knoppix
Linux Mint(v18.0)(LMDE 3)
Mageia(v1.0)(v2.0)
Manjaro Linux
openSUSE(v11.4)(v12.2)
Parabola GNU/Linux-libreurl=https://wiki.parabola.nu/Get_Parabolatitle=Parabola ISO Download Pageaccess-date=18 March 2019
Red Hat Enterprise Linux(v7.0)(v7.0)
Slackware
Solus
Source Mage
SUSE Linux Enterprise Server(v12)(v12)
Ubuntu(v13.04)(v15.04)in Yaketty (16.10)
Void Linux, removed
::

While many distributions boot systemd by default, some allow other init systems to be used; in this case switching the init system is possible by installing the appropriate packages. A fork of Debian called Devuan was developed to avoid systemd and has reached version 5.0 for stable usage. In December 2019, the Debian project voted in favour of retaining systemd as the default init system for the distribution, but with support for "exploring alternatives".

Integration with other software

In the interest of enhancing the interoperability between systemd and the GNOME desktop environment, systemd coauthor Lennart Poettering asked the GNOME Project to consider making systemd an external dependency of GNOME 3.2.

In November 2012, the GNOME Project concluded that basic GNOME functionality should not rely on systemd. However, GNOME 3.8 introduced a compile-time choice between the and ConsoleKit API, the former being provided at the time only by systemd. Ubuntu provided a separate binary, but systemd became a de facto dependency of GNOME for most Linux distributions, in particular since ConsoleKit is no longer actively maintained and upstream recommends the use of instead. The developers of Gentoo Linux also attempted to adapt these changes in OpenRC, but the implementation contained too many bugs, causing the distribution to mark systemd as a dependency of GNOME.

GNOME has further integrated . As of Mutter version 3.13.2, is a dependency for Wayland sessions.

Reception

The design of systemd has ignited controversy within the free-software community. Critics regard systemd as overly complex and suffering from continued feature creep, arguing that its architecture violates the Unix philosophy. There is also concern that it forms a system of interlocked dependencies, thereby giving distribution maintainers little choice but to adopt systemd as more user-space software comes to depend on its components, which is similar to the problems created by PulseAudio, another of Lennart Poettering's projects.

In a 2012 interview, Slackware's lead Patrick Volkerding expressed reservations about the systemd architecture, stating his belief that its design was contrary to the Unix philosophy of interconnected utilities with narrowly defined functionalities. , Slackware does not support or use systemd, but Volkerding has not ruled out the possibility of switching to it.

In January 2013, Lennart Poettering attempted to address concerns about systemd in a blog post called The Biggest Myths.

In February 2014, musl's Rich Felker opined that PID 1 is too special to be saddled with additional responsibilities, believing that PID 1 should only be responsible for starting the rest of the init system and reaping zombie processes, and that the additional functionality added by systemd can be provided elsewhere and unnecessarily increases the complexity and attack surface of PID 1.

In March 2014, Eric S. Raymond commented that systemd's design goals were prone to mission creep and software bloat. In April 2014, Linus Torvalds expressed reservations about the attitude of Kay Sievers, a key systemd developer, toward users and bug reports in regard to modifications to the Linux kernel submitted by Sievers. In late April 2014, a campaign to boycott systemd was launched, with a website listing various reasons against its adoption.

In an August 2014 article published in InfoWorld, Paul Venezia wrote about the systemd controversy and attributed the controversy to violation of the Unix philosophy, and to "enormous egos who firmly believe they can do no wrong". The article also characterizes the architecture of systemd as similar to that of svchost.exe, a critical system component in Microsoft Windows with a broad functional scope.

In a September 2014 ZDNet interview, prominent Linux kernel developer Theodore Ts'o expressed his opinion that the dispute over systemd's centralized design philosophy, more than technical concerns, indicates a dangerous general trend toward uniformizing the Linux ecosystem, alienating and marginalizing parts of the open-source community, and leaving little room for alternative projects. He cited similarities with the attitude he found in the GNOME project toward non-standard configurations. On social media, Ts'o also later compared the attitudes of Sievers and his co-developer, Lennart Poettering, to that of GNOME's developers.

Forks and alternative implementations

Forks of systemd are closely tied to critiques of it outlined in the above section. Forks generally try to improve on at least one of portability (to other libcs and Unix-like systems), modularity, or size. A few forks have collaborated under the FreeInit banner.

Forks of components

eudev

In 2012, the Gentoo Linux project created a fork of udev in order to avoid dependency on the systemd architecture. The resulting fork is called eudev and it makes udev functionality available without systemd. A stated goal of the project is to keep eudev independent of any Linux distribution or init system. In 2021, Gentoo announced that support of eudev would cease at the beginning of 2022. An independent group of maintainers have since taken up eudev.

elogind

Elogind is the systemd project's "logind", extracted to be a standalone daemon. It integrates with PAM to know the set of users that are logged into a system and whether they are logged in graphically, on the console, or remotely. Elogind exposes this information via the standard org.freedesktop.login1 D-Bus interface, as well as through the file system using systemd's standard layout. Elogind also provides "libelogind", which is a subset of the facilities offered by "libsystemd". There is a "libelogind.pc" pkg-config file as well.

Alternatives to components

ConsoleKit2

ConsoleKit was forked in October 2014 by Xfce developers wanting its features to still be maintained and available on operating systems other than Linux. While not ruling out the possibility of reviving the original repository in the long term, the main developer considers ConsoleKit2 a temporary necessity until systembsd matures.

Abandoned forks

Fork of components

LoginKit

LoginKit was an attempt to implement a logind (systemd-logind) shim, which would allow packages that depend on systemd-logind to work without dependency on a specific init system. The project has been defunct since February 2015.

systembsd

In 2014, a Google Summer of Code project named "systembsd" was started in order to provide alternative implementations of these APIs for OpenBSD. The original project developer began it in order to ease his transition from Linux to OpenBSD. Project development finished in July 2016.

The systembsd project did not provide an init replacement, but aimed to provide OpenBSD with compatible daemons for , , , and . The project did not create new systemd-like functionality, and was only meant to act as a wrapper over the native OpenBSD system. The developer aimed for systembsd to be installable as part of the ports collection, not as part of a base system, stating that "systemd and *BSD differ fundamentally in terms of philosophy and development practices."

notsystemd

Notsystemd intends to implement all systemd's features working on any init system. It was forked by the Parabola GNU/Linux-libre developers to build packages with their development tools without the necessity of having systemd installed to run systemd-nspawn. Development ceased in July 2018.

Fork including init system

uselessd

In 2014, uselessd was created as a lightweight fork of systemd. The project sought to remove features and programs deemed unnecessary for an init system, as well as address other perceived faults. Project development halted in January 2015.

uselessd supported the musl and μClibc libraries, so it may have been used on embedded systems, whereas systemd only supports glibc. The uselessd project had planned further improvements on cross-platform compatibility, as well as architectural overhauls and refactoring for the Linux build in the future.

InitWare

InitWare is a modular refactor of systemd, porting the system to BSD platforms without glibc or Linux-specific system calls. It is known to work on DragonFly BSD, FreeBSD, NetBSD, and GNU/Linux. Components considered unnecessary are dropped.

All Systems Go!

::figure[src="https://upload.wikimedia.org/wikipedia/commons/7/76/Lennart_Poettering_ASG_2024.jpg" caption="Lennart Poettering speaking at All Systems Go! 2024"] ::

All Systems Go! is the annual systemd conference, which is held in Berlin. The main topic is systemd but other Linux areas are covered as well, like TPM, DBus, desktop environment, containers, eBPF etc.

Video recordings of the talks are usually archived on YouTube and on the Chaos Computer Club site for offline viewing. Event picture are provided as well.

Notes

References

References

  1. (26 January 2017). "Lennart Poettering on systemd's Tumultuous Ascendancy".
  2. (2023-12-03). "systemd/systemd". systemd.
  3. (30 April 2010). "Rethinking PID 1".
  4. "InterfaceStabilityPromise".
  5. "systemd System and Service Manager".
  6. "Debate/initsystem/systemd - Debian Wiki".
  7. "F15 one page release notes - Fedora Project Wiki".
  8. Gaudreault, Stéphane. (14 August 2012). "Migration to systemd".
  9. "Freedesktop Systemd : List of security vulnerabilities". CVE Details.
  10. McKay, Dave. (2021-02-24). "The Best Linux Distributions Without systemd".
  11. Lennart Poettering. (30 April 2010). "Rethinking PID 1".
  12. "Arch Linux - News: systemd is now the default on new installations".
  13. Groot, Jan de. (14 August 2012). "Migration to systemd".
  14. "Archlinux is moving to systemd (Page 2) / Arch Discussion / Arch Linux Forums".
  15. Carroty, Paul. (28 August 2015). "Lennart Poettering merged 'su' command replacement into systemd: Test Drive on Fedora Rawhide".
  16. (28 September 2016). "Assertion failure when PID 1 receives a zero-length message over notify socket #4234".
  17. Felker, Rich. (3 October 2016). "Hack Crashes Linux Distros with 48 Characters of Code". [[Kaspersky Lab]].
  18. "Pwnie Awards 2017, Lamest Vendor Response: SystemD bugs".
  19. (28 August 2015). "The New Control Group Interfaces". Freedesktop.org.
  20. (11 September 2019). "What is systemd?".
  21. "Inhibitor Locks".
  22. (17 February 2014). "systemd's binary logs and corruption".
  23. Šimerda, Pavel. (3 February 2013). "Can Linux network configuration suck less?".
  24. {{man. 1. networkctl. Linux
  25. Proven, Liam. "Version 252 of systemd released".
  26. (29 May 2014). "[PATCH] Drop the udev firmware loader".
  27. "systemd.syntax".
  28. "systemd.device".
  29. "systemd.scope".
  30. "OpenRC - ArchWiki".
  31. "init - ArchWiki".
  32. "systemd - system and service manager".
  33. "Downloads – Gentoo Linux".
  34. "KNOPPIX 7.4.2 Release Notes".
  35. "KNOPPIX 8.0 Die Antwort auf Systemd (German)".
  36. (10 April 2015). "LM Blog: both Mint 18 and LMDE 3 will switch to systemd.".
  37. "Mageia forum • View topic - is it possible to replace systemd?".
  38. "Parabola ISO Download Page".
  39. "Initial entry of the "systemd" spell".
  40. "Void-Package: systemd: removed; no plans to resurrect this.".
  41. "Meet Devuan, the Debian fork born from a bitter systemd revolt".
  42. (5 May 2017). "systemd-free Devuan Linux hits RC2". [[The Register]].
  43. "Debian Developers Decide On Init System Diversity: "Proposal B" Wins".
  44. Vaughan-Nichols, Steven. (19 September 2014). "Linus Torvalds and others on Linux's systemd". CBS Interactive.
  45. (3 September 2021). "1345661 - PulseAudio requirement breaks Firefox on ALSA-only systems". Mozilla.
  46. Rich Felker. (9 February 2014). "Broken by design: systemd".
  47. "FreeInit.org".
  48. (24 August 2021). "eudev retirement on 2022-01-01". Gentoo Linux.
  49. "dimkr/LoginKit (Github)".
  50. "projects / systembsd.git / summary".
  51. Luke Shumaker. (17 June 2017). "notsystemd v232.1 release announcement".
  52. "notsystemd".
  53. "Uselessd is dead".
  54. (14 November 2021). "InitWare/InitWare: The InitWare Suite of Middleware allows you to manage services and system resources as logical entities called units. Its main component is a service management ("init") system.".
  55. Team, All Systems Go!. "All Systems Go!".
  56. "All Systems Go!".
  57. "Browse by category - media.ccc.de".
  58. "All Systems Go!".
  59. "systemd README".
  60. Poettering, Lennart. (21 April 2012). "systemd Status Update".
  61. "systemd.unit man page". freedesktop.org.
  62. (8 May 2012). "Control Centre: The systemd Linux init system". The H.
  63. (2 January 2014). "Debate/initsystem/systemd – Debian Documentation". [[Debian]].
  64. Poettering, Lennart. (26 January 2013). "The Biggest Myths".
  65. Poettering, Lennart. (May 2014). "A Perspective for systemd: What Has Been Achieved, and What Lies Ahead".
  66. Gundersen, Tom E.. (25 September 2014). "The End of Linux".
  67. (28 January 2013). "systemd Dreams Up New Feature, Makes It Like Cron". [[Phoronix]].
  68. Edge, Jake. (7 November 2013). "Creating containers with systemd-nspawn". [[LWN.net]].
  69. "ControlGroupInterface".
  70. Heo, Tejun. (28 January 2014). "cgroup: convert to kernfs".
  71. Heo, Tejun. (13 March 2014). "cgroup: prepare for the default unified hierarchy".
  72. "systemd-logind.service".
  73. "ConsoleKit official website".
  74. "How to hook up your favorite X11 display manager with systemd".
  75. (27 November 2013). "Networking in +systemd - 1. Background".
  76. (27 November 2013). "Networking in +systemd - 2. libsystemd-rtnl".
  77. (27 November 2013). "Networking in +systemd - 3. udev".
  78. (27 November 2013). "Networking in +systemd - 4. networkd".
  79. (27 November 2013). "Networking in +systemd - 5. the immediate future".
  80. Larabel, Michael. (4 July 2014). "systemd 215 Works On Factory Reset, DHCPv4 Server Support".
  81. "timedated".
  82. Sievers, Kay. "The future of the udev source tree".
  83. Sievers, Kay. "Commit importing udev into systemd".
  84. (24 May 2001). "F15 one page release notes". fedoraproject.org.
  85. "I'm back after a break from Slackware: sharing thoughts and seeing whats new!".
  86. (12 January 2012). "Git clone of the 'packages' repository".
  87. "systemd is now the default on new installations". [[Arch Linux]].
  88. "CoreOS's init system".
  89. (3 October 2013). "coreos/manifest: Releases: v94.0.0".
  90. "systemd".
  91. Garbee, Bdale. (11 February 2014). "Bug#727708: call for votes on default Linux init system for jessie".
  92. "Fedora 14 talking points".
  93. "Installing the Gentoo Base System § Optional: Using systemd".
  94. "Comment #210 (bug #318365)".
  95. "systemd".
  96. "systemd".
  97. "ChangeLog of Mageia's systemd package".
  98. Scherschel, Fabian. (23 May 2012). "Mageia 2 arrives with GNOME 3 and systemd". The H.
  99. (23 February 2011). "Directory view of the 11.4 i586 installation showing presence of the systemd v18 installables".
  100. "OpenSUSE: Not Everyone Likes systemd". [[Phoronix]].
  101. (10 June 2014). "Red Hat Unveils Red Hat Enterprise Linux 7".
  102. "systemd — An alternative boot manager".
  103. Shuttleworth, Mark. (14 February 2014). "Blog Archive » Losing graciously".
  104. (25 October 2013). "#727708 - tech-ctte: Decide which init system to default to in Debian.".
  105. (5 November 2013). "Which init system for Debian?".
  106. (30 December 2013). "Debian Still Debating systemd Vs. Upstart Init System". [[Phoronix]].
  107. (14 February 2014). "Losing graciously".
  108. (18 October 2013). "Quantal, raring, saucy...".
  109. Poettering, Lennart. (18 May 2011). "systemd as an external dependency". GNOME.
  110. Peters, Frederic. (4 November 2011). "20121104 meeting minutes".
  111. "ConsoleKit".
  112. Vitters, Olav. (25 September 2013). "GNOME and logind+systemd thoughts".
  113. "GNOME 3.10 arrives with experimental Wayland support". ZDNet.
  114. "GNOME initiatives: systemd".
  115. (19 May 2014). "Mutter 3.13.2: launcher: Replace mutter-launch with logind integration".
  116. (7 June 2012). "Interview with Patrick Volkerding of Slackware".
  117. Venezia, Paul. (18 August 2014). "systemd: Harbinger of the Linux apocalypse".
  118. Allbery, Russ. (16 November 2014). "Resigning from the Technical Committee".
  119. Hess, Joey. "on leaving".
  120. Jackson, Ian. (19 November 2014). "Resignation".
  121. Heen, Tollef Fog. (16 November 2014). "Resignation from the pkg-systemd maintainer team".
  122. Torvalds, Linus. (2 April 2014). "Re: [RFC PATCH] cmdline: Hide "debug" from /proc/cmdline".
  123. (10 March 2014). "Interviews: ESR Answers Your Questions". Slashdot.org.
  124. (2014-03-31). "A realization that I recently came to while discussing the whole systemd...".
  125. "Boycott systemd.org".
  126. (3 September 2014). "Is systemd as bad as boycott systemd is trying to make it?". LinuxBSDos.com.
  127. "eudev/README".
  128. "elogind/README".
  129. "Gentoo eudev project".
  130. Larabel, Michael. (21 September 2014). "Uselessd: A Stripped Down Version Of systemd". [[Phoronix]].
  131. "uselessd :: information system".
  132. "GSoC 2014: systemd replacement utilities (systembsd)". OpenBSD Journal.
  133. Koegel, Eric. (20 October 2014). "ConsoleKit2".
  134. "loginkit/README".
  135. "Linus Torvalds and others on Linux's systemd".
  136. Pitt, Martin. (5 March 2015). "Announce: Vivid will switch to booting with systemd next Monday, brace for impact".
  137. "Ubuntu Wiki: Switching init systems".
  138. "systemd".
  139. "Github systemd/systemd - systemd System and Service Manager".
  140. "Linked packages : upstart".

::callout[type=info title="Wikipedia Source"] This article was imported from Wikipedia and is available under the Creative Commons Attribution-ShareAlike 4.0 License. Content has been adapted to SurfDoc format. Original contributors can be found on the article history page. ::

freedesktop.orglinux-kernel-related-softwarelinux-only-free-softwaresoftware-that-uses-mesonunix-process--and-task-management-related-softwarenetwork-time-related-software