systemd

From Wikipedia, the free encyclopedia
Jump to: navigation, search
systemd
Systemd-on-fedora.png
Original author(s) Lennart Poettering (Red Hat), Kay Sievers (Red Hat), Harald Hoyer (Red Hat), Daniel Mack (Red Hat), Tom Gundersen (Red Hat), and David Herrmann
Developer(s) Lennart Poettering, Kay Sievers, Harald Hoyer, Daniel Mack, Tom Gundersen, David Herrmann, and others[1]
Initial release 30 March 2010 (2010-03-30)
Stable release 217 (October 28, 2014; 24 days ago (2014-10-28)) [±][2]
Written in C[3]
Operating system Linux
Type Init daemon
License first GPLv2+, currently GNU LGPL 2.1+[4]
Website freedesktop.org/.../systemd/

systemd is a suite of system management daemons, libraries, and utilities designed for Linux and programmed exclusively for the Linux API. Systemd authors characterize the software suite as a "basic building block" for an operating system.[5]

For systems using it, the daemon systemd is the first process that is executed in user space during the Linux startup process. Therefore, systemd serves as the root of the user space's process tree. The name systemd adheres to the Unix convention of making daemons easier to distinguish by having the letter d as the last letter of the filename.[6]

Components[edit]

The architecture of systemd as it is used by Tizen. Several components, including telephony, bootmode, dlog, and tizen service, are from Tizen and are not components of systemd.[7]

Systemd is not just the name of the init daemon but can also refer to the entire software bundle around systemd. This includes the daemons systemd, journald, logind and networkd and many other low-level components such as libraries and utilities. In January 2013, systemd author Lennart Poettering described systemd not as one program, but rather a large software suite that includes 69 individual binaries.[8]

Systemd is published as free and open-source software under the terms of the GNU Lesser General Public License version 2.1 or later.[4]

systemd[edit]

The developers of systemd aimed to replace the Linux init system inherited from UNIX System V and Berkeley Software Distribution (BSD) operating systems. Like init, systemd is a daemon that manages other daemons; all daemons, including systemd, are background processes. Systemd is the first daemon to start during booting and the last daemon to terminate during shutdown. The first process (pid 1) has a special role on Unix systems, as it receives a SIGCHLD signal when a daemon process (which has detached from its parent) terminates. Therefore, the first process is particularly well-suited for the purpose of monitoring daemons; systemd attempts to improve in that particular area over the traditional sysvinit, which would usually not restart daemons automatically but only launch them once without further monitoring.

Lennart Poettering and Kay Sievers, software engineers that initially developed systemd,[1] 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.

Systemd's initialization instructions for each daemon are recorded in a declarative configuration file rather than a shell script. For inter-process communication, systemd makes Unix domain sockets and D-Bus available to the running daemons. Systemd is also capable of parallelization.

Among systemd's auxiliary features is a cron-like job scheduler called systemd Calendar Timers.[9] The state of systemd itself can be preserved in a snapshot for future recall. Following its integrated approach, systemd also provides replacements for various daemons and utilities, including sysvinit, pm-utils, inetd, acpid, syslog, watchdog, cron and atd.

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

cgroups[edit]

Unified-hierarchy cgroups will be accessible exclusively by systemd through systemd-nspawn(1)

systemd tracks processes using the Linux kernel's cgroups subsystem instead of by 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(1) and machinectl(1), two utility programs to facilitate the creation and management of software containers.[10]

Since version 205, systemd offers ControlGroupInterface, an API to the Linux kernel cgroups.[11] The Linux kernel cgroups are adapted to support kernfs,[12] and are being modified to support a unified hierarchy.[13]

consoled[edit]

In October 2014, the beginnings of consoled were integrated, providing a user console daemon, and handling Linux virtual terminal support. Consoled is meant to be included in systemd version 217.[14]

hostnamed[edit]

journald[edit]

systemd-journald is a daemon doing event logging, with binary files serving as its logfiles. The system administrator may choose whether to log system events with systemd-journald, syslog-ng or rsyslog.

  • journalctl(1) may be used to query the contents of the systemd(1) journal as written by systemd-journald.
  • journald.conf(5) – configuration file for various parameters of the systemd journal service.

localed[edit]

logind[edit]

In version 30, systemd-logind was integrated, as a tiny daemon that manages user logins and seats in various ways. systemd-logind is an integrated login manager that offers multiseat improvements[15] and replaces ConsoleKit, which is no longer maintained.[16] For X11 display managers the switch to logind requires a minimal amount of porting.[17]

  • loginctl(1) may be used to introspect and control the state of the login manager systemd-logind.
  • logind.conf(5) – configuration file for various parameters of the systemd login manager.

networkd[edit]

In version 209, networkd was integrated, which provides abilities for systemd to perform various network configurations; as of version 209, support is limited to statically assigned addresses and basic support for bridging configuration.[18][19][20][21][22] In July 2014, systemd version 215 was released, adding new features such as a DHCP server for IPv4 hosts, and VXLAN support.[23]

resolved[edit]

shutdownd[edit]

timedated[edit]

Since version 30, systemd includes systemd-timedated, as 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. systemd-timedated is accessible through D-Bus.[24]

timesyncd[edit]

udevd[edit]

In April 2012, the source tree for udev (a device manager for the Linux kernel, which handles the /dev directory and all user space actions when adding/removing devices, including firmware loading) was merged into the systemd source tree.[25][26]

libudev[edit]

The standard library for utilizing udev is now integrated into the systemd project. By linking against this library, third-party applications may query udev resources.

GNOME integration[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.[27]

In November 2012, the GNOME Project concluded that basic GNOME functionality should not rely on systemd.[28] 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 did provide a logind binary that is separate from the rest of systemd, but this became a de facto dependency of GNOME on systemd for most Linux distributions, in particular since ConsoleKit is not actively maintained anymore and upstream recommends the use of systemd-logind instead.[29] 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.[30][31]

GNOME has further integrated logind.[32] As of Mutter version 3.13.2, logind is a dependency for Wayland sessions.[33] There are plans to replace gnome-session with systemd, but systemd would not be running as PID 1 and gnome-session would remain available on non-Linux systems.

Reception[edit]

Linus Torvalds has expressed reservations about the attitude of a key systemd developer towards users and bug reports.[34] Theodore Ts'o has also had reservations about the systemd philosophy and the attitudes of two key developers.[35]

In a 2012 interview, Slackware's founder Patrick Volkerding also expressed reservations about the systemd architecture:[36]

Concerning systemd, I do like the idea of a faster boot time (obviously), but I also like controlling the startup of the system with shell scripts that are readable, and I'm guessing that's what most Slackware users prefer too. I don't spend all day rebooting my machine, and having looked at systemd config files it seems to me a very foreign way of controlling a system to me, and attempting to control services, sockets, devices, mounts, etc., all within one daemon flies in the face of the UNIX concept of doing one thing and doing it well.

In January 2013, Lennart Poettering attempted to address concerns about systemd in a blog post called The Biggest Myths.[8] After continued controversy over systemd, in October 2014, Poettering complained that the "Open source community is full of assholes, and I probably more than most others am one of their most favourite targets." Poettering went on to blame Linus Torvalds and other kernel developers for the state of the community.[37]

A long debate among the Debian Technical Committee occurred on the Debian mailing list between October 2013 and February 2014[38] concerning what init system to use as the default in Debian 8 "jessie", culminating in a decision in favor of systemd. The debate was widely publicized[39][40] and in the wake of the decision the debate continues on the Debian mailing list.

Shortly after Debian's decision, Mark Shuttleworth announced on his blog that Ubuntu would be following through as well,[41] despite earlier comments describing systemd as "hugely invasive and hardly justified".[42]

Eric S. Raymond declined to comment on systemd at first, but stated, "I'm aware there’s a controversy."[43] Then in a March 2014 interview on Slashdot, he expressed some concerns about the goals and architecture of systemd:[44]

I apologize; I haven't studied systemd in the detail that would be required for me to give a firm answer to this - it's been on my to-do list for a while, but I'm buried in other projects.

I want to study it carefully because I'm a bit troubled by what I hear about the feature set and the goals. From that, I fear it may be one of those projects that is teetering right at the edge of manageable complexity - OK as long as an architect with a strong sense of design discipline is running things, but very prone to mission creep and bloat and likely to turn into a nasty hairball over the longer term.

But this may be me being too pessimistic. I don't actually think I know yet.

In late April, a campaign to boycott systemd was launched;[45] their website http://boycottsystemd.org lists various reasons against its adoption.[46]

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."[47] The article also characterizes the architecture of systemd as more similar to that of Microsoft Windows software:[47]

While systemd has succeeded in its original goals, it's not stopping there. systemd is becoming the Svchost of Linux – which I don't think most Linux folks want. You see, systemd is growing, like wildfire, well outside the bounds of enhancing the Linux boot experience. systemd wants to control most, if not all, of the fundamental functional aspects of a Linux system – from authentication to mounting shares to network configuration to syslog to cron.

Theodore Ts'o expressed his opinion in a ZDNet interview in September 2014, that more than technical concerns the dispute over systemd's centralized design philosophy indicates a dangerous general trend towards uniformizing the Linux ecosystem, alienating and marginalizing parts of the open-source community, leaving little room for alternative projects:[48]

Systemd problems might not have mattered that much, except that GNOME has a similar attitude; they only care for a small subset of the Linux desktop users, and they have historically abandoned some ways of interacting the Desktop in the interest of supporting touchscreen devices and to try to attract less technically sophisticated users. If you don't fall in the demographic of what GNOME supports, you're sadly out of luck. (Or you become a second class citizen, being told that you have to rely on GNOME extensions that may break on every single new version of GNOME.) [...] As a result, many traditional GNOME users have moved over to Cinnamon, XFCE, KDE, etc. But as systemd starts subsuming new functions, components like network-manager will only work on systemd or other components that are forced to be used due to a network of interlocking dependencies; and it may simply not be possible for these alternate desktops to continue to function, because there is [no] viable alternative to systemd supported by more and more distributions.

In November 2014, Debian maintainers and Technical Committee members Joey Hess, Russ Allbery, Ian Jackson and systemd package maintainer Tollef Fog Heen resigned from their positions. All three 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 Open-Source Community that rendered regular maintenance virtually impossible.[49]

Adoption[edit]

In May 2011, Fedora became the first major Linux distribution to enable systemd by default.[50] As of August 2014, Slackware does not support or use systemd, but Slackware's lead Patrick Volkerding has not ruled out the possibility of switching to it.[51] Some distributions allow other init systems to be used; only the default init system (for new installs) was changed to systemd. For such distributions, switching the init system is usually possible by installing the appropriate packages.

Major Linux distributions that adopted systemd
Linux distribution Date added to software repository[a] Enabled by default? Date released as default
Ångström[52] Yes
Arch Linux January 2012[53] Yes October 2012[54]
CoreOS July 2013 Yes[55] October 2013 (v94.0.0)[56]
Debian GNU/Linux April 2012[57] Planned for Debian 8 "Jessie"[b] not yet released
Fedora May 2011 (v15)[59] Yes May 2011 (v15)
Frugalware Linux August 2011 (v1.5)[60] Yes August 2011 (v1.5)
Gentoo Linux[c] 2011[63][64][65] No[d]
Mageia May 2012 (v2.0)[66] Yes May 2012 (v2.0)
NixOS January 2013[67] Yes February 2013 (v1.4)
OpenELEC May 2014 (v4.0)[68] Yes May 2014 (v4.0)
openSUSE March 2011 (v11.4)[69] Yes September 2012 (v12.2)[70]
Red Hat Enterprise Linux June 2014 (v7.0)[71] Yes June 2014 (v7.0)
Sabayon Linux August 2013 (v13.08)[72] Yes August 2013 (v13.08)
Slackware No
SUSE Linux Enterprise Server 2014 (v12) Yes October 2014 (v12)
Tizen 2012[73] Yes 2012
Ubuntu[e] April 2013 (v13.04)[75] Planned[76] not yet released

Graphical frontends[edit]

Apart from the official systemd frontend named systemd-ui, a frontend for KDE is also available.

systemd-ui[edit]

Screenshot of systemd-ui, a GTK+-based frontend for systemd.

Systemd-ui, also known as systemadm, is a simple GTK+-based graphical front-end for systemd.[77] It provides a simple user interface to manage services and a graphical agent to request passwords from the user. As of 2014 the systemadm program has received little development or maintenance in the last few years, because development focus has shifted to command-line tools like systemctl and systemd-analyze.

Kcmsystemd[edit]

Kcmsystemd is a graphical systemd frontend for the KDE desktop environment. It integrates into the KDE's system settings window, allowing monitoring and controlling of systemd services, as well as graphical editing of configuration files.

Forks and alternative implementations[edit]

eudev[edit]

In 2012, the Gentoo Linux project created a fork of systemd-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.[78] The Gentoo project describes eudev as follows:[79]

eudev is a fork of system-udev with the goal of obtaining better compatibility with existing software such as OpenRC and Upstart, older kernels, various toolchains and anything else required by users and various distributions.

uselessd[edit]

In 2014, uselessd, a lightweight fork of systemd was created. The project seeks to remove features and programs deemed unnecessary for an init system, increase implementation modularity, improve portability across platforms, as well as address other perceived faults.[80] uselessd supports the musl and µClibc libraries, so it may be used on embedded systems, whereas systemd only supports glibc. uselessd is attempting initial support for non-Linux platforms (so far only build time being ready), whereas the systemd project does not attempt any compatibility with BSD systems.[80] The uselessd project plans further improvements on cross-platform compatibility, as well as architectural overhauls and refactoring for the Linux build in the future.[81]

systembsd[edit]

An increasing number of projects (in particular GNOME) rely on functionality provided by systemd, for example for multi-seat management (via logind). Since systemd supports only Linux and cannot be easily ported to other operating systems due to the heavy use of Linux kernel APIs, there is a need to offer compatible APIs on other operating systems such as OpenBSD. In 2014, a Google Summer of Code project named "systembsd" was started in order to provide alternative implementations of these APIs for OpenBSD.[82] The project will not provide an init replacement, but aims at providing compatible daemons for hostnamed, timedated, localed, and, in particular, logind which can run on OpenBSD.

See also[edit]

Notes[edit]

  1. ^ Dates are for the general availability release.
  2. ^ The Debian Technical Committee voted to make systemd the default system management daemon for Linux in the "jessie" release.[58]
  3. ^ systemd is supported in Gentoo as an alternative to OpenRC, the default init system[61] for those who "want to use systemd instead, or are planning to use Gnome 3.8 and later (which requires systemd)"[62]
  4. ^ As of 2014, Gentoo requires systemd when selecting the GNOME profile or installing GNOME 3.
  5. ^ Ubuntu's development documentation offers instructions on how to use systemd as an experimental option.[74]

References[edit]

  1. ^ a b README, systemd (freedesktop.org), retrieved 2012-09-09 
  2. ^ "[systemd-devel] [ANNOUNCE] systemd 217". freedesktop.org. 2014-10-28. Retrieved 2014-10-28. 
  3. ^ systemd, Analysis Summary (Ohloh), retrieved 2011-06-16 
  4. ^ a b Lennart Poettering (2012-04-21), systemd Status Update, retrieved 2012-04-28 
  5. ^ Lennart Poettering (September 2010). "Beyond Init: systemd (LinuxKongress 2010)". Retrieved 2014-10-28. 
  6. ^ Lennart Poettering, Kay Sievers, Thorsten Leemhuis (2012-05-08), Control Centre: The systemd Linux init system, The H, archived from the original on 14 October 2012, retrieved 2012-09-09 
  7. ^ Gundersen, Tom E. (2014-09-25). "comment". The End of Linux. Retrieved 2014-10-25. "It certainly is not something that comes with systemd from upstream." 
  8. ^ a b Poettering, Lennart (2013-01-26). "The Biggest Myths". 
  9. ^ "[Phoronix] Systemd Dreams Up New Feature, Makes It Like Cron". Phoronix.com. 2013-01-28. Retrieved 2014-01-22. 
  10. ^ Jake Edge (2013-11-07). "Creating containers with systemd-nspawn". LWN.net. Retrieved 2014-07-30. 
  11. ^ "ControlGroupInterface". Retrieved 9 November 2014. 
  12. ^ "cgroup: convert to kernfs". 2014-01-28. 
  13. ^ "cgroup: prepare for the default unified hierarchy". 2014-03-13. 
  14. ^ Michael Larabel (2014-10-07). "Systemd 217 Will Introduce Its New "Consoled" User Console Daemon". Retrieved 2014-10-27. 
  15. ^ "systemd-logind.service". Freedesktop.org. Retrieved 2014-02-17. 
  16. ^ "ConsoleKit official website". Retrieved 9 November 2014. 
  17. ^ "How to hook up your favorite X11 display manager with systemd". Freedesktop.org. 
  18. ^ "Networking in +systemd - 1. Background". 2013-11-27. Retrieved 2014-02-22. 
  19. ^ "Networking in +systemd - 2. libsystemd-rtnl". 2013-11-27. Retrieved 2014-02-22. 
  20. ^ "Networking in +systemd - 3. udev". 2013-11-27. Retrieved 2014-02-22. 
  21. ^ "Networking in +systemd - 4. networkd". 2013-11-27. Retrieved 2014-02-22. 
  22. ^ "Networking in +systemd - 5. the immediate future". 2013-11-27. Retrieved 2014-02-22. 
  23. ^ Michael Larabel (2014-07-04). "Systemd 215 Works On Factory Reset, DHCPv4 Server Support". Retrieved 2014-11-08. 
  24. ^ "timedated". Retrieved 9 November 2014. 
  25. ^ Sievers, Kay, The future of the udev source tree, linux-hotplug mailing list, retrieved 2013-05-22 
  26. ^ Sievers, Kay, Commit importing udev into systemd, systemd (freedesktop.org), retrieved 25 May 2012 
  27. ^ Lennart Poettering (2011-05-18), systemd as an external dependency, desktop-devel mailing list (GNOME), retrieved 2011-05-26 
  28. ^ Frederic Peters (2011-11-04), 20121104 meeting minutes, GNOME release-team mailing list, retrieved 2013-01-14 
  29. ^ "ConsoleKit". 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!" 
  30. ^ Vitters, Olav. "GNOME and logind+systemd thoughts". Retrieved 24 April 2014. 
  31. ^ "GNOME 3.10 arrives with experimental Wayland support". ZDNet. Retrieved 24 April 2014. 
  32. ^ "GNOME initiatives: systemd". Retrieved 2014-05-01. 
  33. ^ "Mutter 3.13.2: launcher: Replace mutter-launch with logind integration". 2014-05-19. Retrieved 2014-05-28. 
  34. ^ "Linux-Kernel Archive: Re: [RFC PATCH] cmdline: Hide "debug" from /proc/cmdline". 2 April 2014. Retrieved 8 July 2014. 
  35. ^ "A realization that I recently came to while discussing the whole systemd...". 31 March 2014. Retrieved 8 July 2014. 
  36. ^ "Interview with Patrick Volkerding of Slackware". Linuxquestions.org. 2012-06-07. Retrieved 2014-03-19. 
  37. ^ Steven J. Vaughan-Nichols (2014-10-06). "Lennart Poettering's Linus Torvalds rant". ZDNet. Retrieved 2014-10-31. 
  38. ^ "#727708 - tech-ctte: Decide which init system to default to in Debian.". 2013-10-25. Retrieved 2014-09-14. 
  39. ^ "Which init system for Debian?". 2013-11-05. Retrieved 2014-09-14. 
  40. ^ "Debian Still Debating Systemd Vs. Upstart Init System". Phoronix.com. 2013-12-30. Retrieved 2014-09-14. 
  41. ^ "Losing graciously". 2014-02-14. Retrieved 2014-09-14. 
  42. ^ "Quantal, raring, saucy...". 2013-10-18. Retrieved 2014-09-14. 
  43. ^ Eric S. Raymond (2014-02-15). "Namedropping "ESR"". Retrieved 2014-05-19. 
  44. ^ "Interviews: ESR Answers Your Questions". Slashdot.org. 2014-03-10. Retrieved 2014-03-19. 
  45. ^ "Boycott Systemd.org". Retrieved 2014-09-14. 
  46. ^ "Is systemd as bad as boycott systemd is trying to make it?". LinuxToday. Retrieved 2014-09-22. 
  47. ^ a b Paul Venezia (2014-08-18). "Systemd: Harbinger of the Linux apocalypse". Retrieved 2014-09-20. 
  48. ^ "Linus Torvalds and others on Linux's systemd". Retrieved 2014-11-21. 
  49. ^ "Resigning from the Technical Committee". Retrieved 2014-11-19. "on leaving". Retrieved 2014-11-19. "Resignation". Retrieved 2014-11-19. "Resignation from the pkg-systemd maintainer team". Retrieved 2014-11-19. 
  50. ^ F15 one page release notes, fedoraproject.org, 2001-05-24 
  51. ^ "I'm back after a break from Slackware: sharing thoughts and seeing whats new!". Linuxquestions.org. Retrieved 2014-03-14. 
  52. ^ Matt Richardson. "Creating Ångström System Services". 
  53. ^ "svntogit/packages.git - Git clone of the 'packages' repository". Web interface to the Arch Linux git repositories. 2012-01-12. 
  54. ^ "systemd is now the default on new installations". Arch Linux. 
  55. ^ CoreOS's init system, CoreOS Inc, retrieved 2014-02-14 
  56. ^ "Releases: v94.0.0". "coreos/manifest". github.com. October 3, 2013. Retrieved September 22, 2014. 
  57. ^ "systemd". Debian Package Search. Retrieved 2014-11-19. 
  58. ^ Bdale Garbee (2014-02-11). "Bug#727708: call for votes on default Linux init system for jessie". 
  59. ^ D. J. Walker-Morgan (2011-05-24), Fedora 15's Lovelock released, The H, archived from the original on 2 August 2011, retrieved 2012-08-22 
  60. ^ Phayz (2012-01-17), Review of 2011, Frugalware Project, retrieved 2012-08-22 
  61. ^ "systemd". 
  62. ^ "Installing the Gentoo Base System § Optional: Using systemd". 
  63. ^ Comment #210, systemd – bug #318365 (Gentoo's Bugzilla), retrieved 2011-07-05 
  64. ^ systemd, Gentoo's Documentation, retrieved 2011-07-05 
  65. ^ systemd, Gentoo wiki, retrieved 2012-08-26 
  66. ^ Fabian Scherschel (2012-05-23), Mageia 2 arrives with GNOME 3 and systemd, The H, archived from the original on 8 December 2013, retrieved 2012-08-22 
  67. ^ Eelco Dolstra (2013-01-21), [Nix-dev] Systemd branch merged, retrieved 2014-08-20 
  68. ^ OpenELEC 4.0 released, 2014-06-10 
  69. ^ Directory view of the 11.4 i586 installation showing presence of the systemd v18 installables, 2011-02-23, retrieved 2013-09-24 
  70. ^ "OpenSUSE: Not Everyone Likes SystemD". Phoronix. "The recently released openSUSE 12.2 does migrate from SysVinit to systemd" 
  71. ^ Red Hat Unveils Red Hat Enterprise Linux 7, 2014-06-10 
  72. ^ lxnay (2013-08-12). "Press Release: Sabayon 13.08". Sabayon. Retrieved 2014-01-22. 
  73. ^ Mikko Ylinen (2012-05-09). "Tizen IVI Architecture". Retrieved 2014-10-20. 
  74. ^ systemd - An alternative boot manager, Ubuntu Wiki, retrieved 2013-06-24 
  75. ^ "Package Search Results - systemd". ubuntu.com. Retrieved 2014-02-17. 
  76. ^ Mark Shuttleworth (2014-02-14). "Blog Archive » Losing graciously". markshuttleworth.com. Retrieved 2014-02-14. 
  77. ^ "Details of package systemd-ui in Debian "Jessie" 8". Debian. Retrieved 2014-07-31. 
  78. ^ "gentoo/eudev – README". Retrieved 2014-10-28. 
  79. ^ "Gentoo Linux Projects – Gentoo eudev project". Retrieved 2014-10-28. 
  80. ^ a b Michael Larabel (2014-09-21). "Uselessd: A Stripped Down Version Of Systemd". Phoronix. Retrieved 2014-10-26. 
  81. ^ "uselessd :: information system". uselessd.darknedgy.net. Retrieved 2014-10-26. 
  82. ^ "GSoC 2014: Systemd replacement utilities (systembsd)". OpenBSD Journal. Retrieved 15 November 2014. 

External links[edit]