1 systemd System and Service Manager
4 http://0pointer.de/blog/projects/systemd.html
7 http://www.freedesktop.org/wiki/Software/systemd
10 git://anongit.freedesktop.org/systemd/systemd
11 ssh://git.freedesktop.org/git/systemd/systemd
14 http://cgit.freedesktop.org/systemd/systemd
17 http://lists.freedesktop.org/mailman/listinfo/systemd-devel
18 http://lists.freedesktop.org/mailman/listinfo/systemd-commits
21 #systemd on irc.freenode.org
24 https://bugs.freedesktop.org/enter_bug.cgi?product=systemd
32 LGPLv2.1+ for all code
33 - except sd-daemon.[ch] and sd-readahead.[ch] which are MIT
34 - except src/udev/ which is (currently still) GPLv2+
37 Linux kernel >= 2.6.39
39 CONFIG_CGROUPS (it's OK to disable all controllers)
47 Linux kernel >= 3.8 for Smack support
49 Udev will fail to work with the legacy layout:
50 CONFIG_SYSFS_DEPRECATED=n
52 Legacy hotplug slows down the system and confuses udev:
53 CONFIG_UEVENT_HELPER_PATH=""
55 Userspace firmware loading is deprecated, will go away, and
56 sometimes causes problems:
57 CONFIG_FW_LOADER_USER_HELPER=n
59 Some udev rules and virtualization detection relies on it:
62 Mount and bind mount handling might require it:
65 Optional but strongly recommended:
68 CONFIG_TMPFS_POSIX_ACL
72 For systemd-bootchart a kernel with procfs support and several
73 proc output options enabled is required:
84 libblkid >= 2.20 (from util-linux) (optional)
85 libkmod >= 5 (optional)
86 PAM >= 1.1.2 (optional)
87 libcryptsetup (optional)
93 tcpwrappers (optional)
95 libqrencode (optional)
96 libmicrohttpd (optional)
98 make, gcc, and similar tools
100 During runtime you need the following additional dependencies:
102 util-linux >= v2.19 (requires fsck -l, agetty -s)
103 sulogin (from util-linux >= 2.22 or sysvinit-tools, optional but recommended)
107 When building from git you need the following additional dependencies:
119 python-lxml (entirely optional)
121 When systemd-hostnamed is used it is strongly recommended to
122 install nss-myhostname to ensure that in a world of
123 dynamically changing hostnames the hostname stays resolvable
124 under all circumstances. In fact, systemd-hostnamed will warn
125 if nss-myhostname is not installed.
127 Note that D-Bus can link against libsystemd-login.so, which
128 results in a cyclic build dependency. To accommodate for this
129 please build D-Bus without systemd first, then build systemd,
130 then rebuild D-Bus with systemd support.
132 To build HTML documentation for python-systemd using sphinx,
133 please first install systemd (using 'make install'), and then
134 invoke sphinx-build with 'make sphinx-<target>', with <target>
135 being 'html' or 'latexpdf'. If using DESTDIR for installation,
136 pass the same DESTDIR to 'make sphinx-html' invocation.
139 Default udev rules use the following standard system group
140 names, which need to be resolvable by getgrnam() at any time,
141 even in the very early boot stages, where no other databases
142 and network are available:
144 tty, dialout, kmem, video, audio, lp, floppy, cdrom, tape, disk
146 During runtime the journal daemon requires the
147 "systemd-journal" system group to exist. New journal files will
148 be readable by this group (but not writable) which may be used
149 to grant specific users read access.
151 It is also recommended to grant read access to all journal
152 files to the system groups "wheel" and "adm" with a command
153 like the following in the post installation script of the
156 # setfacl -nm g:wheel:rx,d:g:wheel:rx,g:adm:rx,d:g:adm:rx /var/log/journal/
158 The journal gateway daemon requires the
159 "systemd-journal-gateway" system user and group to
160 exist. During execution this network facing service will drop
161 privileges and assume this uid/gid for security reasons.
164 systemd will warn you during boot if /etc/mtab is not a
165 symlink to /proc/mounts. Please ensure that /etc/mtab is a
168 systemd will warn you during boot if /usr is on a different
169 file system than /. While in systemd itself very little will
170 break if /usr is on a separate partition many of its
171 dependencies very likely will break sooner or later in one
172 form or another. For example udev rules tend to refer to
173 binaries in /usr, binaries that link to libraries in /usr or
174 binaries that refer to data files in /usr. Since these
175 breakages are not always directly visible systemd will warn
176 about this, since this kind of file system setup is not really
177 supported anymore by the basic set of Linux OS components.
179 For more information on this issue consult
180 http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken
182 To run systemd under valgrind, compile with VALGRIND defined
183 (e.g. ./configure CPPFLAGS='... -DVALGRIND=1'). Otherwise,
184 false positives will be triggered by code which violates
185 some rules but is actually safe.