2N/Asystemd System and Service Manager
2N/A LGPLv2.1+ for all code
2N/A - except sd-daemon.[ch] and sd-readahead.[ch] which are MIT
2N/A Linux kernel >= 2.6.39
2N/A CONFIG_CGROUPS (it's OK to disable all controllers)
2N/A Udev will fail to work with the legacy layout:
2N/A CONFIG_SYSFS_DEPRECATED=n
2N/A Legacy hotplug slows down the system and confuses udev:
2N/A CONFIG_UEVENT_HELPER_PATH=""
2N/A Userspace firmware loading is deprecated, will go away, and
2N/A sometimes causes problems:
2N/A CONFIG_FW_LOADER_USER_HELPER=n
2N/A Some udev rules and virtualization detection relies on it:
2N/A Mount and bind mount handling might require it:
2N/A Optional but strongly recommended:
2N/A CONFIG_TMPFS_POSIX_ACL
For systemd-bootchart a kernel with procfs support and several
proc output options enabled is required:
libblkid >= 2.20 (from util-linux) (optional)
make, gcc, and similar tools
During runtime you need the following additional dependencies:
util-linux >= v2.19 (requires fsck -l, agetty -s)
sulogin (from util-linux >= 2.22 or sysvinit-tools, optional but recommended)
When building from git you need the following additional dependencies:
When systemd-hostnamed is used it is strongly recommended to
install nss-myhostname to ensure that in a world of
dynamically changing hostnames the hostname stays resolvable
under all circumstances. In fact, systemd-hostnamed will warn
if nss-myhostname is not installed.
results in a cyclic build dependency. To accommodate for this
please build D-Bus without systemd first, then build systemd,
then rebuild D-Bus with systemd support.
To build HTML documentation for python-systemd using sphinx,
please first install systemd (using 'make install'), and then
invoke sphinx-build with 'make sphinx-<target>', with <target>
being 'html' or 'latexpdf'. If using DESTDIR for installation,
pass the same DESTDIR to 'make sphinx-html' invocation.
Default udev rules use the following standard system group
names, which need to be resolvable by getgrnam() at any time,
even in the very early boot stages, where no other databases
and network are available:
tty, dialout, kmem, video, audio, lp, floppy, cdrom, tape, disk
During runtime the journal daemon requires the
"systemd-journal" system group to exist. New journal files will
be readable by this group (but not writable) which may be used
to grant specific users read access.
It is also recommended to grant read access to all journal
files to the system groups "wheel" and "adm" with a command
like the following in the post installation script of the
The journal gateway daemon requires the
"systemd-journal-gateway" system user and group to
exist. During execution this network facing service will drop
privileges and assume this
uid/gid for security reasons.
systemd will warn you during boot if
/etc/mtab is not a
systemd will warn you during boot if /usr is on a different
file system than /. While in systemd itself very little will
break if /usr is on a separate partition many of its
dependencies very likely will break sooner or later in one
form or another. For example udev rules tend to refer to
binaries in /usr, binaries that link to libraries in /usr or
binaries that refer to data files in /usr. Since these
breakages are not always directly visible systemd will warn
about this, since this kind of file system setup is not really
supported anymore by the basic set of Linux OS components.
For more information on this issue consult
To run systemd under valgrind, compile with VALGRIND defined
(
e.g. ./configure CPPFLAGS='... -DVALGRIND=1'). Otherwise,
false positives will be triggered by code which violates
some rules but is actually safe.