X-Git-Url: https://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=README;h=99b66a8396ff21e2aedf6172290970d0f9c8adeb;hp=7fd5c0e5bf4176bb7e1df92a665c742cdb62b6aa;hb=3bfd4e0c6341b0ef946d2198f089743fa99e0a97;hpb=23aedd029452b65c11b6eb838e44f60be1c66814 diff --git a/README b/README index 7fd5c0e5b..99b66a839 100644 --- a/README +++ b/README @@ -37,13 +37,12 @@ LICENSE: - except src/udev/* which is (currently still) GPLv2, GPLv2+ REQUIREMENTS: - Linux kernel >= 3.0 - Linux kernel >= 3.3 for loop device partition support features with nspawn + Linux kernel >= 3.7 Linux kernel >= 3.8 for Smack support Kernel Config Options: CONFIG_DEVTMPFS - CONFIG_CGROUPS (it's OK to disable all controllers) + CONFIG_CGROUPS (it is OK to disable all controllers) CONFIG_INOTIFY_USER CONFIG_SIGNALFD CONFIG_TIMERFD @@ -53,14 +52,14 @@ REQUIREMENTS: CONFIG_PROC_FS CONFIG_FHANDLE (libudev, mount and bind mount handling) - Udev will fail to work with the legacy layout: + udev will fail to work with the legacy sysfs layout: CONFIG_SYSFS_DEPRECATED=n Legacy hotplug slows down the system and confuses udev: CONFIG_UEVENT_HELPER_PATH="" - Userspace firmware loading is deprecated, will go away, and - sometimes causes problems: + Userspace firmware loading is not supported and should + be disabled in the kernel: CONFIG_FW_LOADER_USER_HELPER=n Some udev rules and virtualization detection relies on it: @@ -70,6 +69,9 @@ REQUIREMENTS: create additional symlinks in /dev/disk/ and /dev/tape: CONFIG_BLK_DEV_BSG + Required for PrivateNetwork in service units: + CONFIG_NET_NS + Optional but strongly recommended: CONFIG_IPV6 CONFIG_AUTOFS4_FS @@ -77,6 +79,10 @@ REQUIREMENTS: CONFIG_TMPFS_XATTR CONFIG_SECCOMP + Required for CPUShares in resource control unit settings + CONFIG_CGROUP_SCHED + CONFIG_FAIR_GROUP_SCHED + For systemd-bootchart, several proc debug interfaces are required: CONFIG_SCHEDSTATS CONFIG_SCHED_DEBUG @@ -94,7 +100,7 @@ REQUIREMENTS: If systemd is compiled with libseccomp support on architectures which do not use socketcall() and where seccomp is supported (this effectively means x86-64 and ARM, but - excludes 32bit x86!), then nspawn will now install a + excludes 32-bit x86!), then nspawn will now install a work-around seccomp filter that makes containers boot even with audit being enabled. This works correctly only on kernels 3.14 and newer though. TL;DR: turn audit off, still. @@ -108,24 +114,23 @@ REQUIREMENTS: libcryptsetup (optional) libaudit (optional) libacl (optional) - libattr (optional) libselinux (optional) liblzma (optional) - tcpwrappers (optional) + liblz4 >= 119 (optional) libgcrypt (optional) libqrencode (optional) libmicrohttpd (optional) libpython (optional) + libidn (optional) + gobject-introspection > 1.40.0 (optional) + elfutils >= 158 (optional) make, gcc, and similar tools During runtime, you need the following additional dependencies: - util-linux >= v2.19 (requires fsck -l, agetty -s), - v2.21 required for tests in test/ + util-linux >= v2.25 required dbus >= 1.4.0 (strictly speaking optional, but recommended) - sulogin (from util-linux >= 2.22 or sysvinit-tools, optional but recommended, - required for tests in test/) dracut (optional) PolicyKit (optional) @@ -162,7 +167,7 @@ USERS AND GROUPS: 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 + audio, cdrom, dialout, disk, input, kmem, lp, tape, tty, video During runtime, the journal daemon requires the "systemd-journal" system group to exist. New journal files will @@ -181,6 +186,39 @@ USERS AND GROUPS: 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. + + Similarly, the name resolution daemon requires the + "systemd-resolve" system user and group to exist. + + Similarly, the kdbus dbus1 proxy daemon requires the + "systemd-bus-proxy" system user and group to exist. + +NSS: + systemd ships with three NSS modules: + + nss-myhostname resolves the local hostname to locally + configured IP addresses, as well as "localhost" to + 127.0.0.1/::1. + + nss-resolve enables DNS resolution via the systemd-resolved + DNS/LLMNR caching stub resolver "systemd-resolved". + + nss-mymachines enables resolution of all local containers + registered with machined to their respective IP addresses. + + To make use of these NSS modules, please add them to the + "hosts: " line in /etc/nsswitch.conf. The "resolve" module + should replace the glibc "dns" module in this file. + + The three modules should be used in the following order: + + hosts: files mymachines resolve myhostname + WARNINGS: systemd will warn you during boot if /etc/mtab is not a symlink to /proc/mounts. Please ensure that /etc/mtab is a @@ -198,7 +236,7 @@ WARNINGS: supported anymore by the basic set of Linux OS components. systemd requires that the /run mount point exists. systemd also - requires that /var/run is a a symlink → /run. + requires that /var/run is a a symlink to /run. For more information on this issue consult http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken