X-Git-Url: http://git.ipfire.org/?p=thirdparty%2Fsystemd.git;a=blobdiff_plain;f=README;h=fcf20ed9f8c95f73a570453c93704d0c424e88af;hp=b735214e2e319c115c008742ecc48c0373313c18;hb=f789e0b4f891800557c74c385d0f61a0164cb16f;hpb=12777909c9cbf4217aecbbb38de97bac5252fc5b diff --git a/README b/README index b735214e2e3..fcf20ed9f8c 100644 --- a/README +++ b/README @@ -148,20 +148,25 @@ REQUIREMENTS: libacl (optional) libselinux (optional) liblzma (optional) - liblz4 >= 119 (optional) + liblz4 >= 1.3.0 / 130 (optional) libgcrypt (optional) libqrencode (optional) libmicrohttpd (optional) libpython (optional) libidn2 or libidn (optional) + gnutls >= 3.1.4 (optional, >= 3.5.3 is required to support DNS-over-TLS with gnutls) + openssl >= 1.1.0 (optional, required to support DNS-over-TLS with openssl) elfutils >= 158 (optional) polkit (optional) + tzdata >= 2014f (optional) 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 + python >= 3.5 + meson >= 0.46 (>= 0.49 is required to build position-independent executables) + ninja gcc, awk, sed, grep, m4, and similar tools During runtime, you need the following additional @@ -172,12 +177,12 @@ REQUIREMENTS: NOTE: If using dbus < 1.9.18, you should override the default policy directory (--with-dbuspolicydir=/etc/dbus-1/system.d). dracut (optional) - PolicyKit (optional) + polkit (optional) To build in directory build/: meson build/ && ninja -C build - Any configuration options can be specfied as -Darg=value... arguments + Any configuration options can be specified as -Darg=value... arguments to meson. After the build directory is initially configured, meson will refuse to run again, and options must be changed with: mesonconf -Darg=value... @@ -204,10 +209,12 @@ REQUIREMENTS: make use of DynamicUser= now, hence enabling nss-systemd is not optional. - Note that the build prefix for systemd must be /usr. -Dsplit-usr=false - (which is the default and does not need to be specified) is the - recommended setting, and -Dsplit-usr=true should be used on systems - which have /usr on a separate partition. + Note that the build prefix for systemd must be /usr. (Moreover, + packages systemd relies on — such as D-Bus — really should use the same + prefix, otherwise you are on your own.) -Dsplit-usr=false (which is the + default and does not need to be specified) is the recommended setting, + and -Dsplit-usr=true should be used on systems which have /usr on a + separate partition. Additional packages are necessary to run some tests: - busybox (used by test/TEST-13-NSPAWN-SMOKE) @@ -232,14 +239,11 @@ USERS AND GROUPS: groups "wheel" and "adm" will be given read-only access to journal files using systemd-tmpfiles.service. - The journal gateway daemon requires the - "systemd-journal-gateway" system user and group to + The journal remote daemon requires the + "systemd-journal-remote" system user and group to exist. During execution this network facing service will drop privileges and assume this uid/gid for security reasons. - Similarly, the NTP daemon requires the "systemd-timesync" system - user and group to exist. - Similarly, the network management daemon requires the "systemd-network" system user and group to exist. @@ -275,7 +279,7 @@ NSS: passwd: compat mymachines systemd group: compat mymachines systemd - hosts: files mymachines resolve myhostname + hosts: files mymachines resolve [!UNAVAIL=return] dns myhostname SYSV INIT.D SCRIPTS: When calling "systemctl enable/disable/is-enabled" on a unit which is a @@ -306,16 +310,14 @@ WARNINGS: For more information on this issue consult https://www.freedesktop.org/wiki/Software/systemd/separate-usr-is-broken - To run systemd under valgrind, compile with VALGRIND defined - (e.g. CPPFLAGS='... -DVALGRIND=1' meson ) 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. - -STABLE BRANCHES AND BACKPORTS + To run systemd under valgrind, compile with meson option + -Dvalgrind=true 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. +STABLE BRANCHES AND BACKPORTS: Stable branches with backported patches are available in the systemd-stable repo at https://github.com/systemd/systemd-stable.