namespaces: default all the namespaces to 'yes' when CONFIG_NAMESPACES is selected

[pandora-kernel.git] / init / Kconfig

diff --git a/init/Kconfig b/init/Kconfig
index 3ae8ffe..239fae4 100644 (file)
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -746,6 +746,7 @@ config NAMESPACES
 config UTS_NS
        bool "UTS namespace"
        depends on NAMESPACES
+       default y
        help
          In this namespace tasks see different info provided with the
          uname() system call
@@ -753,6 +754,7 @@ config UTS_NS
 config IPC_NS
        bool "IPC namespace"
        depends on NAMESPACES && (SYSVIPC || POSIX_MQUEUE)
+       default y
        help
          In this namespace tasks work with IPC ids which correspond to
          different IPC objects in different namespaces.
@@ -760,27 +762,25 @@ config IPC_NS
 config USER_NS
        bool "User namespace (EXPERIMENTAL)"
        depends on NAMESPACES && EXPERIMENTAL
+       default y
        help
          This allows containers, i.e. vservers, to use user namespaces
          to provide different user info for different servers.
          If unsure, say N.
 
 config PID_NS
-       bool "PID Namespaces (EXPERIMENTAL)"
-       default n
-       depends on NAMESPACES && EXPERIMENTAL
+       bool "PID Namespaces"
+       depends on NAMESPACES
+       default y
        help
          Support process id namespaces.  This allows having multiple
          processes with the same pid as long as they are in different
          pid namespaces.  This is a building block of containers.
 
-         Unless you want to work with an experimental feature
-         say N here.
-
 config NET_NS
        bool "Network namespace"
-       default n
-       depends on NAMESPACES && EXPERIMENTAL && NET
+       depends on NAMESPACES && NET
+       default y
        help
          Allow user space to create what appear to be multiple instances
          of the network stack.