From: Lennart Poettering <lennart@poettering.net>
Date: Tue, 5 May 2015 20:41:31 +0000 (-0700)
Subject: man: nspawn is used in production these days, admit that
X-Git-Tag: v220~209
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=7de7ee62c5628a3c9e116f14aca63a35d06f5331;p=thirdparty%2Fsystemd.git

man: nspawn is used in production these days, admit that

Previously, the man page suggested to only use nspawn for testing,
building, and debugging things. However, it is nowadays used in
production and used as building block for rocket, hence let's just admit
that it's pretty much production ready.
---

diff --git a/man/systemd-nspawn.xml b/man/systemd-nspawn.xml
index cae067bcff2..cb96661317c 100644
--- a/man/systemd-nspawn.xml
+++ b/man/systemd-nspawn.xml
@@ -84,13 +84,10 @@
     kernel modules may not be loaded from within the container.</para>
 
     <para>Note that even though these security precautions are taken
-    <command>systemd-nspawn</command> is not suitable for secure
+    <command>systemd-nspawn</command> is not suitable for fully secure
     container setups. Many of the security features may be
     circumvented and are hence primarily useful to avoid accidental
-    changes to the host system from the container. The intended use of
-    this program is debugging and testing as well as building of
-    packages, distributions and software involved with boot and
-    systems management.</para>
+    changes to the host system from the container.</para>
 
     <para>In contrast to
     <citerefentry project='man-pages'><refentrytitle>chroot</refentrytitle><manvolnum>1</manvolnum></citerefentry> <command>systemd-nspawn</command>