Jump to content

systemd

From Wikipedia, the free encyclopedia
(Redirected from Systemd-nspawn)
For other uses, see System D (disambiguation).
Not to be confused with System D or Systeme D.

systemd
Original author(s)Lennart Poettering[1]
Developer(s)Red Hat (Lennart Poettering, Kay Sievers, Harald Hoyer, Daniel Mack, Tom Gundersen, David Herrmann);[2] 345 different authors in 2018[3] and 2,032 different authors in total [4]
Initial release30 March 2010; 14 years ago (2010-03-30)
Stable release
257.1[5] Edit this on Wikidata / 19 December 2024
Repository
Written inC
Operating systemLinux
Type
LicenseLGPLv2.1+[6]
Websitesystemd.io

systemd is a software suite that provides an array of system components for Linux[7] operating systems. The main aim is to unify service configuration and behavior across Linux distributions.[8] Its primary component is a "system and service manager" — 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.[9] It also plays on the term "System D", which refers to a person's ability to adapt quickly and improvise to solve problems.[10]

Since 2015, the majority of Linux distributions have adopted systemd, having replaced other init systems such as SysV init. 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.[11][12][13] At the time of adoption of systemd on most Linux distributions, it was the only software suite that offered reliable parallelism during boot as well as centralized management of processes, daemons, services and mount points.

Critics of systemd contend that it suffers from mission creep and bloat, the latter affecting other software (such as the GNOME desktop), adding dependencies on systemd, reducing its compatibility with other Unix-like operating systems and making it difficult for sysadmins to integrate alternative solutions. In addition, they contend that the complexity of systemd results in a larger attack surface, reducing the overall security of the platform.[14] Concerns have also been raised about Red Hat and its parent company IBM controlling the scene of init systems on Linux.[15][1] A number of new forked Linux distributions have since been created that use alternative init systems like SysV or OpenRC.[16] Systemd has not been adopted by Unix-like systems outside the Linux space, like FreeBSD, OpenBSD and Solaris.

History

[edit]

Lennart Poettering and Kay Sievers, the software engineers then working for Red Hat who initially developed systemd,[2] started a project to replace Linux's conventional System V init in 2010.[17] An April 2010 blog post from Poettering, titled "Rethinking PID 1", introduced an experimental version of what would later become systemd.[18] 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.[19]

In October 2012, Arch Linux made systemd the default, switching from SysVinit.[20] Developers had debated since August 2012[13] and came to the conclusion that it was faster and had more features than SysVinit, and that maintaining the latter was not worth the effort in patches.[21] Some of them thought that the criticism towards the implementation of systemd was not based on actual shortcomings of the software, rather the disliking of Lennart from a part of the Linux community and the general hesitation for change. Specifically, some of the complaints regarding systemd not being programmed in bash, it being bigger and more extensive than SysVinit, the use of D-bus, and the optional on-disk format of the journal were regarded as advantages by programmers.[22]

Between October 2013 and February 2014, a long debate among the Debian Technical Committee occurred on the Debian mailing list,[23] discussing which init system to use as the default in Debian 8 "jessie", and culminating in a decision in favor of systemd. The debate was widely publicized[24][25] and in the wake of the decision the debate continues on the Debian mailing list. In February 2014, after Debian's decision was made, Mark Shuttleworth announced in his blog that Ubuntu would follow in implementing systemd, discarding its own Upstart.[26][27]

In November 2014, Debian Developer Joey Hess,[28] Debian Technical Committee members Russ Allbery[29] and Ian Jackson,[30] and systemd package-maintainer Tollef Fog Heen[31] resigned from their positions. All four justified their decision on the public Debian mailing list and in personal blogs with their exposure to extraordinary stress-levels related to ongoing disputes on systemd integration within the Debian and FOSS community that rendered regular maintenance virtually impossible.

In August 2015, systemd started providing a login shell, callable via machinectl shell.[32]

In September 2016, a security bug was discovered that allowed any unprivileged user to perform a denial-of-service attack against systemd.[33] Rich Felker, developer of musl, stated that this bug reveals a major "system development design flaw".[34] In 2017 another security bug was discovered in systemd, CVE-2017-9445, which "allows disruption of service" by a "malicious DNS server".[35][36] Later in 2017, the Pwnie Awards gave author Lennart Poettering a "lamest vendor response" award due to his handling of the vulnerabilities.[37]

Design

[edit]
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.[38]
Unified-hierarchy cgroups will be accessible exclusively by systemd through systemd-nspawn[39]

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:[40]

  • 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)

systemd includes features like on-demand starting of daemons, snapshot support, process tracking[41] and Inhibitor Locks.[42] 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 systemd init daemon, includes the daemons journald, logind and networkd, 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.[43] 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, systemd is a daemon that manages other daemons, which, including systemd itself, are background processes. systemd is the first daemon to start during booting and the last daemon to terminate during shutdown. The systemd 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.

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

Core components and libraries

[edit]

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

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

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

Ancillary components

[edit]

Beside its primary purpose of providing a Linux init system, the systemd suite can provide additional functionality, including the following components:

A screenshot of systemd-boot
A screenshot of timedatectl
journald
systemd-journald 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 systemd-journald, syslog-ng or rsyslog. The potential for corruption of the binary format has led to much heated debate.[49]
libudev
libudev is the standard library for utilizing udev, which allows third-party applications to query udev resources.
localed
localed manages the system locale and keyboard layout.
logind
systemd-logind is a daemon that manages user logins and seats in various ways. It is an integrated login manager that offers multiseat improvements[50] and replaces ConsoleKit, which is no longer maintained.[51] For X11 display managers the switch to logind requires a minimal amount of porting.[52] It was integrated in systemd version 30.
hostnamed
hostnamed manages the system hostname.
homed
homed is a daemon that provides portable human-user accounts that are independent of current system configuration. homed moves various pieces of data such as UID/GID from various places across the filesystem into one file, ~/.identity. homed 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.
networkd
networkd 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.[53][54][55][56][57] In July 2014, systemd version 215 was released, adding new features such as a DHCP server for IPv4 hosts, and VXLAN support.[58][59] networkctl may be used to review the state of the network links as seen by systemd-networkd.[60] Configuration of new interfaces has to be added under the /lib/systemd/network/ as a new file ending with .network extension.
resolved
provides network name resolution to local applications
systemd-boot
systemd-boot is a boot manager, formerly known as gummiboot. Kay Sievers merged it into systemd with rev 220.
systemd-bsod
systemd-bsod is an error reporter used to generate Blue Screen of Death.
systemd-nspawn
systemd-nspawn may be used to run a command or OS in a namespace container.
timedated
systemd-timedated 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.[61] It was integrated in systemd version 30.
timesyncd
timesyncd is a client NTP daemon for synchronizing the system clock across the network.
tmpfiles
systemd-tmpfiles 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.
udevd
udev is a device manager for the Linux kernel, which handles the /dev 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.[62][63] In order to match the version number of udev, systemd maintainers bumped the version number directly from 44 to 183.[64]
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.[65]

Configuration of systemd

[edit]
systemd-manager, a tool to configure systemd

systemd is configured exclusively via plain-text files.

systemd 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 .ini files.[66]

Unit-file types[67] include:

  • .service
  • .socket
  • .device (automatically initiated by systemd[68])
  • .mount
  • .automount
  • .swap
  • .target
  • .path
  • .timer (which can be used as a cron-like job scheduler[69])
  • .snapshot
  • .slice (used to group and manage processes and resources[70])
  • .scope (used to group worker processes, not intended to be configured via unit files[71])

Adoption

[edit]
Linux distribution Date added to software repository[a] Enabled by default? Date released as default Runs without?
Alpine Linux N/A (not in repository) No — Yes
Android N/A (not in repository) No — Yes
Arch Linux January 2012[72] Yes October 2012[73] No
antiX Linux N/A (not in repository) No — Yes
Artix Linux N/A (not in repository) No — Yes
CentOS July 2014 Yes July 2014 (v7.0) No
CoreOS July 2013 Yes October 2013 (v94.0.0)[74][75] No
Debian April 2012[76] Yes April 2015 (v8.0)[77] Jessie is the last release supporting installing without systemd.[78] In bullseye, a number of alternative init systems are supported
Devuan N/A (not in repository) No — Yes
Fedora Linux November 2010 (v14)[79] Yes May 2011 (v15) No
Gentoo Linux[b] July 2011[80][82][83] Optional[84] — Yes
GNU Guix System N/A (not in repository) No — Yes
Knoppix — No [85][86] — Yes
Linux Mint June 2016 (v18.0) Yes August 2018 (LMDE 3) No [87]
Mageia January 2011 (v1.0)[88] Yes May 2012 (v2.0)[89] No [90]
Manjaro Linux November 2013 Yes November 2013 No
openSUSE March 2011 (v11.4)[91] Yes September 2012 (v12.2)[92] No
Parabola GNU/Linux-libre January 2012[72] Optional[93] — Yes
Red Hat Enterprise Linux June 2014 (v7.0)[94] Yes June 2014 (v7.0) No
Slackware N/A (not in repository) No — Yes
Solus — Yes — No
Source Mage June 2011[95] No — Yes
SUSE Linux Enterprise Server October 2014 (v12) Yes October 2014 (v12) No
Ubuntu April 2013 (v13.04) Yes April 2015 (v15.04) Upstart option removed in Yaketty (16.10)[96][97][c]
Void Linux June 2011, removed June 2015[98] No — Yes

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[99][100] 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".[101]

Integration with other software

[edit]

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.[102]

In November 2012, the GNOME Project concluded that basic GNOME functionality should not rely on systemd.[103] However, GNOME 3.8 introduced a compile-time choice between the logind and ConsoleKit API, the former being provided at the time only by systemd. Ubuntu provided a separate logind 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 systemd-logind instead.[104] 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.[105][106]

GNOME has further integrated logind.[107] As of Mutter version 3.13.2, logind is a dependency for Wayland sessions.[108]

Reception

[edit]

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.[109][110]

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.[111] As of August 2018, Slackware does not support or use systemd, but Volkerding has not ruled out the possibility of switching to it.[112]

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

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.[113]

In March 2014, Eric S. Raymond commented that systemd's design goals were prone to mission creep and software bloat.[114] 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.[115] In late April 2014, a campaign to boycott systemd was launched, with a website listing various reasons against its adoption.[116][117]

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".[118] 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.[118]

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.[119] On social media, Ts'o also later compared the attitudes of Sievers and his co-developer, Lennart Poettering, to that of GNOME's developers.[120]

Forks and alternative implementations

[edit]

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.[121]

Forks of components

[edit]

eudev

[edit]

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.[122] A stated goal of the project is to keep eudev independent of any Linux distribution or init system.[123] 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.[124]

elogind

[edit]

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 /run/systemd 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.[125]

Alternatives to components

[edit]

ConsoleKit2

[edit]

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.[126]

Abandoned forks

[edit]

Fork of components

[edit]
LoginKit
[edit]

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.[127] The project has been defunct since February 2015.[128]

systembsd
[edit]

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.[129] Project development finished in July 2016.[130]

The systembsd project did not provide an init replacement, but aimed to provide OpenBSD with compatible daemons for hostnamed, timedated, localed, and logind. 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."[129]

notsystemd
[edit]

Notsystemd intends to implement all systemd's features working on any init system.[131] 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.[132]

Fork including init system

[edit]
uselessd
[edit]

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.[133] Project development halted in January 2015.[134]

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.[135]

InitWare
[edit]

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.[136]

See also

[edit]

Notes

[edit]
  1. ^ Dates are for the general availability release.
  2. ^ systemd is supported in Gentoo as an alternative to OpenRC, the default init system[80] for those who "want to use systemd instead, or are planning to use Gnome 3.8 and later (which requires systemd)"[81]
  3. ^ Missing functionality using init systems other than systemd[citation needed]

References

[edit]
  1. ^ a b "Lennart Poettering on systemd's Tumultuous Ascendancy". 26 January 2017. Archived from the original on 8 November 2018. Retrieved 7 November 2018.
  2. ^ a b "systemd README", freedesktop.org, archived from the original on 7 July 2013, retrieved 9 September 2012
  3. ^ "Systemd Hits A High Point For Number Of New Commits & Contributors During 2018 - Phoronix". Archived from the original on 21 September 2009. Retrieved 30 December 2018.
  4. ^ Used the "contributors" statistic from: systemd/systemd, systemd, 3 December 2023, retrieved 3 December 2023
  5. ^ "systemd v257.1". 19 December 2024. Retrieved 20 December 2024.
  6. ^ Poettering, Lennart (21 April 2012), systemd Status Update, archived from the original on 23 April 2012, retrieved 28 April 2012
  7. ^ "Rethinking PID 1". 30 April 2010. Archived from the original on 22 February 2022. Retrieved 20 August 2021. systemd uses many Linux-specific features, and does not limit itself to POSIX. That unlocks a lot of functionality a system that is designed for portability to other operating systems cannot provide.
  8. ^ "InterfaceStabilityPromise". FreeDesktop.org. Archived from the original on 11 December 2017. Retrieved 14 February 2018.
  9. ^ "systemd System and Service Manager". freedesktop.org. Archived from the original on 15 October 2020. Retrieved 19 March 2016. Yes, it is written systemd, not system D or System D, or even SystemD. And it isn't system d either. Why? Because it's a system daemon, and under Unix/Linux those are in lower case, and get suffixed with a lower case d.
  10. ^ Poettering, Lennart; Sievers, Kay; Leemhuis, Thorsten (8 May 2012), Control Centre: The systemd Linux init system, The H, archived from the original on 14 October 2012, retrieved 9 September 2012
  11. ^ "Debate/initsystem/systemd - Debian Wiki". wiki.debian.org. Archived from the original on 7 December 2014. Retrieved 15 November 2021.
  12. ^ "F15 one page release notes - Fedora Project Wiki". fedoraproject.org. Archived from the original on 27 September 2013. Retrieved 15 November 2021.
  13. ^ a b Gaudreault, Stéphane (14 August 2012). "Migration to systemd". arch-dev-public (Mailing list). Archived from the original on 20 October 2020. Retrieved 15 November 2021.
  14. ^ "Freedesktop Systemd : List of security vulnerabilities". CVE Details. Archived from the original on 3 October 2021. Retrieved 3 October 2021.
  15. ^ Saunders, Mike (11 November 2015). "Linux 101: Get the most out of systemd". Linux Voice. Archived from the original on 29 May 2016. Retrieved 28 January 2016.
  16. ^ McKay, Dave (24 February 2021). "The Best Linux Distributions Without systemd". How-To Geek. Retrieved 7 December 2024.
  17. ^ Simmonds, Chris (2015). "9: Starting up - the init Program". Mastering Embedded Linux Programming. Packt Publishing Ltd. p. 239. ISBN 9781784399023. Retrieved 20 June 2016. 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.
  18. ^ Lennart Poettering (30 April 2010). "Rethinking PID 1". Archived from the original on 15 January 2017. Retrieved 28 August 2010.
  19. ^ "F15 one page release notes", fedoraproject.org, 24 May 2001, archived from the original on 27 September 2013, retrieved 24 September 2013
  20. ^ "Arch Linux - News: systemd is now the default on new installations". archlinux.org. Archived from the original on 27 October 2021. Retrieved 11 November 2021.
  21. ^ Groot, Jan de (14 August 2012). "Migration to systemd". arch-dev-public (Mailing list). Archived from the original on 17 January 2022. Retrieved 11 November 2021.
  22. ^ "Archlinux is moving to systemd (Page 2) / Arch Discussion / Arch Linux Forums". bbs.archlinux.org. Archived from the original on 10 November 2012. Retrieved 19 November 2021.
  23. ^ "#727708 - tech-ctte: Decide which init system to default to in Debian". 25 October 2013. Archived from the original on 17 April 2016. Retrieved 14 September 2014.
  24. ^ "Which init system for Debian?". 5 November 2013. Archived from the original on 6 October 2014. Retrieved 14 September 2014.
  25. ^ "Debian Still Debating systemd Vs. Upstart Init System". Phoronix. 30 December 2013. Archived from the original on 23 August 2014. Retrieved 14 September 2014.
  26. ^ "Losing graciously". 14 February 2014. Archived from the original on 8 September 2014. Retrieved 14 September 2014.
  27. ^ "Quantal, raring, saucy..." 18 October 2013. Archived from the original on 28 August 2014. Retrieved 14 September 2014.
  28. ^ Hess, Joey. "on leaving". Archived from the original on 16 July 2015. Retrieved 15 July 2015.
  29. ^ Allbery, Russ (16 November 2014). "Resigning from the Technical Committee". debian-ctte (Mailing list). Archived from the original on 11 June 2015. Retrieved 15 July 2015.
  30. ^ Jackson, Ian (19 November 2014). "Resignation". debian-ctte (Mailing list). Archived from the original on 11 June 2015. Retrieved 15 July 2015.
  31. ^ Heen, Tollef Fog (16 November 2014). "Resignation from the pkg-systemd maintainer team". pkg-systemd-maintainers (Mailing list). Archived from the original on 11 June 2015. Retrieved 15 July 2015.
  32. ^ Carroty, Paul (28 August 2015). "Lennart Poettering merged 'su' command replacement into systemd: Test Drive on Fedora Rawhide". Archived from the original on 4 September 2015.
  33. ^ "Assertion failure when PID 1 receives a zero-length message over notify socket #4234". GitHub. 28 September 2016. Archived from the original on 5 October 2016. Retrieved 6 October 2016.
  34. ^ Felker, Rich (3 October 2016). "Hack Crashes Linux Distros with 48 Characters of Code". Kaspersky Lab. Archived from the original on 6 October 2016. Retrieved 6 October 2016.
  35. ^ "CVE-2017-9445 Details", National Vulnerability Database, National Institute of Standards and Technology (U.S.), 6 July 2017, archived from the original on 6 July 2018, retrieved 6 July 2018
  36. ^ "CVE-2017-9445", The Common Vulnerabilities and Exposures database, The Mitre Corporation, 5 June 2017, archived from the original on 6 July 2018, retrieved 6 July 2018
  37. ^ "Pwnie Awards 2017, Lamest Vendor Response: SystemD bugs". Pwnie Awards. Archived from the original on 10 June 2021. Retrieved 10 June 2021.
  38. ^ Gundersen, Tom E. (25 September 2014). "The End of Linux". Archived from the original on 26 October 2014. Retrieved 25 October 2014. It certainly is not something that comes with systemd from upstream.
  39. ^ "The New Control Group Interfaces". Freedesktop.org. 28 August 2015. Archived from the original on 1 February 2016. Retrieved 6 February 2016.
  40. ^ Poettering, Lennart (May 2014). "A Perspective for systemd: What Has Been Achieved, and What Lies Ahead" (PDF). Archived (PDF) from the original on 8 February 2015. Retrieved 30 November 2014.
  41. ^ "What is systemd?". Linode. 11 September 2019. Archived from the original on 24 January 2020. Retrieved 15 September 2019.
  42. ^ "Inhibitor Locks". freedesktop.org. Archived from the original on 3 May 2020. Retrieved 15 September 2019.
  43. ^ a b Poettering, Lennart (26 January 2013). "The Biggest Myths". Archived from the original on 17 October 2021. Retrieved 20 August 2021.
  44. ^ "Debate/initsystem/systemd – Debian Documentation". Debian. 2 January 2014. Archived from the original on 7 December 2014. Retrieved 4 December 2014.
  45. ^ Edge, Jake (7 November 2013). "Creating containers with systemd-nspawn". LWN.net. Archived from the original on 23 August 2014. Retrieved 30 July 2014.
  46. ^ "ControlGroupInterface". freedesktop.org. Archived from the original on 12 December 2014. Retrieved 9 November 2014.
  47. ^ Heo, Tejun (28 January 2014). "cgroup: convert to kernfs". linux-kernel (Mailing list). Archived from the original on 12 October 2018. Retrieved 24 May 2014.
  48. ^ Heo, Tejun (13 March 2014). "cgroup: prepare for the default unified hierarchy". linux-kernel (Mailing list). Archived from the original on 20 March 2014. Retrieved 24 May 2014.
  49. ^ "systemd's binary logs and corruption". 17 February 2014. Archived from the original on 11 May 2016. Retrieved 21 January 2016.
  50. ^ "systemd-logind.service". freedesktop.org. Archived from the original on 11 April 2014. Retrieved 17 February 2014.
  51. ^ "ConsoleKit official website". freedesktop.org. Archived from the original on 18 October 2014. Retrieved 9 November 2014.
  52. ^ "How to hook up your favorite X11 display manager with systemd". freedesktop.org. Archived from the original on 28 March 2016. Retrieved 19 March 2016.
  53. ^ "Networking in +systemd - 1. Background". 27 November 2013. Archived from the original on 13 March 2014. Retrieved 22 February 2014.
  54. ^ "Networking in +systemd - 2. libsystemd-rtnl". 27 November 2013. Archived from the original on 13 March 2014. Retrieved 22 February 2014.
  55. ^ "Networking in +systemd - 3. udev". 27 November 2013. Archived from the original on 13 March 2014. Retrieved 22 February 2014.
  56. ^ "Networking in +systemd - 4. networkd". 27 November 2013. Archived from the original on 13 March 2014. Retrieved 22 February 2014.
  57. ^ "Networking in +systemd - 5. the immediate future". 27 November 2013. Archived from the original on 13 March 2014. Retrieved 22 February 2014.
  58. ^ Larabel, Michael (4 July 2014). "systemd 215 Works On Factory Reset, DHCPv4 Server Support". Archived from the original on 17 October 2014. Retrieved 8 November 2014.
  59. ^ Šimerda, Pavel (3 February 2013). "Can Linux network configuration suck less?".
  60. ^ networkctl(1) – Linux User Manual – User Commands
  61. ^ "timedated". freedesktop.org. Archived from the original on 11 October 2014. Retrieved 9 November 2014.
  62. ^ Sievers, Kay. "The future of the udev source tree". vger.kernel.org/vger-lists.html#linux-hotplug linux-hotplug (Mailing list). Archived from the original on 16 February 2015. Retrieved 22 May 2013.
  63. ^ Sievers, Kay, "Commit importing udev into systemd", freedesktop.org, archived from the original on 20 April 2013, retrieved 25 May 2012
  64. ^ Proven, Liam. "Version 252 of systemd released". The Register. Archived from the original on 5 November 2022. Retrieved 5 November 2022.
  65. ^ "[PATCH] Drop the udev firmware loader". systemd-devel (Mailing list). 29 May 2014. Archived from the original on 14 August 2020. Retrieved 16 June 2019.
  66. ^ "systemd.syntax". www.freedesktop.org. Archived from the original on 27 July 2021. Retrieved 27 July 2021.
  67. ^ "systemd.unit man page". freedesktop.org. Archived from the original on 28 March 2016. Retrieved 19 March 2016.
  68. ^ "systemd.device". www.freedesktop.org. Archived from the original on 27 July 2021. Retrieved 27 July 2021.
  69. ^ "systemd Dreams Up New Feature, Makes It Like Cron". Phoronix. 28 January 2013. Archived from the original on 3 January 2014. Retrieved 22 January 2014.
  70. ^ "systemd.slice (5) - Linux Man Pages". Archived from the original on 19 February 2023. Retrieved 12 March 2018. ... a slice ... is a concept for hierarchically managing resources of a group of processes.
  71. ^ "systemd.scope". FreeDesktop.org. Archived from the original on 27 July 2021. Retrieved 27 July 2021.
  72. ^ a b "Git clone of the 'packages' repository". Web interface to the Arch Linux git repositories. 12 January 2012. Archived from the original on 16 February 2015. Retrieved 31 August 2014.
  73. ^ "systemd is now the default on new installations". Arch Linux. Archived from the original on 15 October 2012. Retrieved 29 October 2012.
  74. ^ "coreos/manifest: Releases: v94.0.0". github.com. 3 October 2013. Archived from the original on 10 September 2020. Retrieved 22 September 2014.
  75. ^ "CoreOS's init system", coreos.com, archived from the original on 14 February 2014, retrieved 14 February 2014
  76. ^ "systemd". debian.org. Archived from the original on 29 December 2014. Retrieved 19 November 2014.
  77. ^ Garbee, Bdale (11 February 2014). "Bug#727708: call for votes on default Linux init system for jessie". debian-ctte (Mailing list). Archived from the original on 22 February 2014. Retrieved 11 February 2014.
  78. ^ "systemd - system and service manager". Debian Wiki. Installing without systemd. Archived from the original on 4 April 2018. Retrieved 3 April 2018.
  79. ^ "Fedora 14 talking points". Archived from the original on 9 June 2015. Retrieved 28 April 2015.
  80. ^ a b "systemd", wiki.gentoo.org, archived from the original on 12 October 2012, retrieved 26 August 2012
  81. ^ "Installing the Gentoo Base System § Optional: Using systemd". Archived from the original on 14 July 2014. Retrieved 4 July 2014.
  82. ^ "Comment #210 (bug #318365)", gentoo.org, archived from the original on 16 February 2015, retrieved 5 July 2011
  83. ^ "systemd", gentoo.org, archived from the original on 26 June 2011, retrieved 5 July 2011
  84. ^ "Downloads – Gentoo Linux".
  85. ^ "KNOPPIX 7.4.2 Release Notes". Archived from the original on 6 January 2018. Retrieved 26 April 2018. ...script-based KNOPPIX system start with sysvinit
  86. ^ "KNOPPIX 8.0 Die Antwort auf Systemd (German)". Archived from the original on 13 June 2018. Retrieved 13 June 2018. ...Knoppix 'boot process continues to run via Sys-V init with few bash scripts that start the system services efficiently sequentially or in parallel. (The original German text: Knoppix' Startvorgang läuft nach wie vor per Sys-V-Init mit wenigen Bash-Skripten, welche die Systemdienste effizient sequenziell oder parallel starten.)
  87. ^ "LM Blog: both Mint 18 and LMDE 3 will switch to systemd". 10 April 2015. Archived from the original on 27 November 2021. Retrieved 27 November 2021.
  88. ^ ChangeLog of Mageia's systemd package, archived from the original on 28 March 2016, retrieved 19 March 2016
  89. ^ Scherschel, Fabian (23 May 2012), Mageia 2 arrives with GNOME 3 and systemd, The H, archived from the original on 8 December 2013, retrieved 22 August 2012
  90. ^ "Mageia forum • View topic - is it possible to replace systemd?". Archived from the original on 19 February 2023. Retrieved 5 May 2020.
  91. ^ Directory view of the 11.4 i586 installation showing presence of the systemd v18 installables, 23 February 2011, archived from the original on 28 September 2013, retrieved 24 September 2013
  92. ^ "OpenSUSE: Not Everyone Likes systemd". Phoronix. Archived from the original on 15 March 2016. Retrieved 19 March 2016. The recently released openSUSE 12.2 does migrate from SysVinit to systemd
  93. ^ "Parabola ISO Download Page". Archived from the original on 1 July 2016. Retrieved 18 March 2019.
  94. ^ Red Hat Unveils Red Hat Enterprise Linux 7, 10 June 2014, archived from the original on 14 July 2014, retrieved 19 March 2016
  95. ^ "Initial entry of the "systemd" spell". Archived from the original on 23 September 2020. Retrieved 21 May 2019.
  96. ^ "Ubuntu Wiki: Switching init systems". Archived from the original on 3 June 2016. Retrieved 3 July 2016.
  97. ^ "Linked packages : upstart". Launchpad. Archived from the original on 12 May 2021. Retrieved 17 June 2019.
  98. ^ "Void-Package: systemd: removed; no plans to resurrect this". GitHub. Archived from the original on 19 February 2023. Retrieved 24 July 2018.
  99. ^ "Meet Devuan, the Debian fork born from a bitter systemd revolt". Archived from the original on 9 December 2014. Retrieved 24 February 2015.
  100. ^ Sharwood, Simon (5 May 2017). "systemd-free Devuan Linux hits RC2". The Register. Archived from the original on 5 May 2017. Retrieved 5 May 2017.
  101. ^ "Debian Developers Decide On Init System Diversity: "Proposal B" Wins". Phoronix. Archived from the original on 28 December 2019. Retrieved 28 December 2019.
  102. ^ Poettering, Lennart (18 May 2011). "systemd as an external dependency". desktop-devel (Mailing list). GNOME. Archived from the original on 27 May 2011. Retrieved 26 May 2011.
  103. ^ Peters, Frederic (4 November 2011). "20121104 meeting minutes". GNOME release-team (Mailing list). Archived from the original on 7 September 2014. Retrieved 14 January 2013.
  104. ^ "ConsoleKit". Archived from the original on 18 October 2014. Retrieved 15 November 2014. ConsoleKit is currently not actively maintained. The focus has shifted to the built-in seat/user/session management of Software/systemd called systemd-logind!
  105. ^ Vitters, Olav (25 September 2013). "GNOME and logind+systemd thoughts". Archived from the original on 24 April 2014. Retrieved 24 April 2014.
  106. ^ "GNOME 3.10 arrives with experimental Wayland support". ZDNet. Archived from the original on 24 April 2014. Retrieved 24 April 2014.
  107. ^ "GNOME initiatives: systemd". Archived from the original on 2 May 2014. Retrieved 9 May 2018.
  108. ^ "Mutter 3.13.2: launcher: Replace mutter-launch with logind integration". 19 May 2014. Archived from the original on 16 February 2015. Retrieved 28 May 2014.
  109. ^ Vaughan-Nichols, Steven (19 September 2014). "Linus Torvalds and others on Linux's systemd". ZDNet. CBS Interactive. Archived from the original on 25 February 2015. Retrieved 24 February 2015.
  110. ^ "1345661 - PulseAudio requirement breaks Firefox on ALSA-only systems". Bugzilla. Mozilla. 3 September 2021. Archived from the original on 3 October 2021. Retrieved 3 October 2021.
  111. ^ "Interview with Patrick Volkerding of Slackware". linuxquestions.org. 7 June 2012. Archived from the original on 3 May 2013. Retrieved 19 March 2014.
  112. ^ "I'm back after a break from Slackware: sharing thoughts and seeing whats new!". linuxquestions.org. Archived from the original on 13 March 2014. Retrieved 14 March 2014.
  113. ^ Rich Felker (9 February 2014). "Broken by design: systemd". Archived from the original on 23 October 2019.
  114. ^ "Interviews: ESR Answers Your Questions". Slashdot.org. 10 March 2014. Archived from the original on 22 March 2014. Retrieved 19 March 2014.
  115. ^ Torvalds, Linus (2 April 2014). "Re: [RFC PATCH] cmdline: Hide "debug" from /proc/cmdline". linux-kernel (Mailing list). Archived from the original on 22 October 2017. Retrieved 8 July 2014.
  116. ^ "Is systemd as bad as boycott systemd is trying to make it?". LinuxBSDos.com. 3 September 2014. Archived from the original on 24 September 2014. Retrieved 22 September 2014.
  117. ^ "Boycott systemd.org". Archived from the original on 6 May 2014. Retrieved 15 July 2015.
  118. ^ a b Venezia, Paul (18 August 2014). "systemd: Harbinger of the Linux apocalypse". Archived from the original on 26 September 2014. Retrieved 20 September 2014.
  119. ^ "Linus Torvalds and others on Linux's systemd". ZDNet. Archived from the original on 20 November 2014. Retrieved 21 November 2014.
  120. ^ "A realization that I recently came to while discussing the whole systemd..." 31 March 2014. Archived from the original on 17 July 2014. Retrieved 8 July 2014.
  121. ^ "FreeInit.org". www.freeinit.org. Archived from the original on 1 August 2021. Retrieved 1 August 2021.
  122. ^ "eudev/README". GitHub. Archived from the original on 16 February 2015. Retrieved 1 June 2015.
  123. ^ "Gentoo eudev project". Archived from the original on 4 September 2015. Retrieved 1 June 2015.
  124. ^ Basile, Anthony G. (24 August 2021). "eudev retirement on 2022-01-01". Repository news items. Gentoo Linux. Archived from the original on 30 June 2022. Retrieved 14 June 2022.
  125. ^ "elogind/README". GitHub. Archived from the original on 19 February 2023. Retrieved 2 September 2015.
  126. ^ Koegel, Eric (20 October 2014). "ConsoleKit2". Archived from the original on 2 April 2015. Retrieved 7 March 2015.
  127. ^ "loginkit/README". GitHub. Archived from the original on 19 February 2023. Retrieved 4 December 2014.
  128. ^ "dimkr/LoginKit (Github)". GitHub. Archived from the original on 19 February 2023. Retrieved 8 July 2018.
  129. ^ a b "GSoC 2014: systemd replacement utilities (systembsd)". OpenBSD Journal. Archived from the original on 29 November 2014. Retrieved 28 November 2014.
  130. ^ projects / systembsd.git / summary, archived from the original on 9 July 2018, retrieved 8 July 2018
  131. ^ Luke Shumaker (17 June 2017). "notsystemd v232.1 release announcement". Dev@lists.parabola.nu (Mailing list). Archived from the original on 5 August 2017. Retrieved 5 August 2017.
  132. ^ "notsystemd". Parabola GNU/Linux-libre. Archived from the original on 8 December 2023. Retrieved 8 December 2023.
  133. ^ Larabel, Michael (21 September 2014). "Uselessd: A Stripped Down Version Of systemd". Phoronix. Archived from the original on 17 October 2014. Retrieved 26 October 2014.
  134. ^ "Uselessd is dead". Uselessd website. Archived from the original on 16 May 2015. Retrieved 17 February 2017.
  135. ^ "uselessd :: information system". uselessd.darknedgy.net. Archived from the original on 16 May 2015. Retrieved 26 October 2014.
  136. ^ "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". GitHub. 14 November 2021. Archived from the original on 1 August 2021. Retrieved 1 August 2021.
[edit]
Retrieved from "https://en.wikipedia.org/w/index.php?title=Systemd&oldid=1261616627#Core_components_and_libraries"