sd-dhcp-client: make timeout handling a bit more robust

[elogind.git] / README

diff --git a/README b/README
index bb0fe1d0de0bf3068943d5d0d47c45179ee7cecb..ace13cf07587a63d5f4a55583093c0777180cc36 100644 (file)
--- a/README
+++ b/README
@@ -30,7 +30,7 @@ AUTHOR:
 
 LICENSE:
         LGPLv2.1+ for all code
 
 LICENSE:
         LGPLv2.1+ for all code

-        - except sd-daemon.[ch] and sd-readahead.[ch] which are MIT
+        - except sd-readahead.[ch] which is MIT

         - except src/shared/MurmurHash2.c which is Public Domain
         - except src/shared/siphash24.c which is CC0 Public Domain
         - except src/journal/lookup3.c which is Public Domain
         - except src/shared/MurmurHash2.c which is Public Domain
         - except src/shared/siphash24.c which is CC0 Public Domain
         - except src/journal/lookup3.c which is Public Domain


@@ -89,6 +89,13 @@ REQUIREMENTS:
         runtime using the kernel command line option "audit=0", or
         turn it off at kernel compile time using:
           CONFIG_AUDIT=n
         runtime using the kernel command line option "audit=0", or
         turn it off at kernel compile time using:
           CONFIG_AUDIT=n

+        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
+        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.

 
         glibc >= 2.14
         libcap
 
         glibc >= 2.14
         libcap


@@ -190,6 +197,9 @@ WARNINGS:
         about this, since this kind of file system setup is not really
         supported anymore by the basic set of Linux OS components.
 
         about this, since this kind of file system setup is not really
         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.
+

         For more information on this issue consult
         http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken
 
         For more information on this issue consult
         http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken