GIT:
git@github.com:systemd/systemd.git
- https://github.com/systemd/systemd.git
-
-GITWEB:
https://github.com/systemd/systemd
MAILING LIST:
fixed, and it's best to disable group scheduling hence.
CONFIG_RT_GROUP_SCHED=n
+ It's a good idea to disable the implicit creation of networking bonding
+ devices by the kernel networking bonding module, so that the
+ automatically created "bond0" interface doesn't conflict with any such
+ device created by systemd-networkd (or other tools). Ideally there
+ would be a kernel compile-time option for this, but there currently
+ isn't. The next best thing is to make this change through a modprobe.d
+ drop-in. This is shipped by default, see modprobe.d/systemd.conf.
+
Note that kernel auditing is broken when used with systemd's
container code. When using systemd in conjunction with
containers, please make sure to either turn off auditing at
glibc >= 2.16
libcap
- libmount >= 2.27.1 (from util-linux)
- (util-linux < 2.29 *must* be built with --enable-libmount-force-mountinfo,
- and later versions without --enable-libmount-support-mtab.)
+ libmount >= 2.30 (from util-linux)
+ (util-linux *must* be built without --enable-libmount-support-mtab)
libseccomp >= 2.3.1 (optional)
libblkid >= 2.24 (from util-linux) (optional)
libkmod >= 15 (optional)
libpython (optional)
libidn2 or libidn (optional)
elfutils >= 158 (optional)
- make, gcc, and similar tools
+ pkg-config
+ gperf
+ docbook-xsl (optional, required for documentation)
+ xsltproc (optional, required for documentation)
+ python-lxml (optional, required to build the indices)
+ python, meson, ninja
+ gcc, awk, sed, grep, m4, and similar tools
During runtime, you need the following additional
dependencies:
dracut (optional)
PolicyKit (optional)
- Two build systems are supported: meson + ninja-build and autools + make.
-
- The following tools are needed with both systems:
-
- pkg-config
- gperf >= 3.1
- docbook-xsl (optional, required for documentation)
- xsltproc (optional, required for documentation)
- python-lxml (optional, required to build the indices)
-
- When building with meson, python and ninja-build are required.
-
To build in directory build/:
meson build/ && ninja -C build
sudo ninja install
DESTDIR=... ninja install
- When building with autotools, the following tools are needed:
-
- automake
- autoconf
- libtool
- intltool
- python (optional)
-
- The build system is initialized with ./autogen.sh and the usual
- ./configure && make
- should be used.
-
- A tar ball can be created with:
+ A tarball can be created with:
git archive --format=tar --prefix=systemd-222/ v222 | xz > systemd-222.tar.xz
When systemd-hostnamed is used, it is strongly recommended to
https://www.freedesktop.org/wiki/Software/systemd/separate-usr-is-broken
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.
+ (e.g. CPPFLAGS='... -DVALGRIND=1' meson <options>) and have valgrind
+ development headers installed (i.e. valgrind-devel or
+ equivalent). Otherwise, false positives will be triggered by code which
+ violates some rules but is actually safe. Note that valgrind generates
+ nice output only on exit(), hence on shutdown we don't execve()
+ systemd-shutdown.
ENGINEERING AND CONSULTING SERVICES:
Kinvolk (https://kinvolk.io) offers professional engineering