As the different namespaces depend on 'CONFIG_NAMESPACES', it is
logical to enable all the namespaces when we enable NAMESPACES.
Signed-off-by: Daniel Lezcano <daniel.lezc...@free.fr>
---
init/Kconfig | 7 +++++--
1 files changed, 5 insertions(+), 2 deletions(-)
diff --git a/init/Kconfig b/init/Kconfig
index a52124e..a7fe61e 100644
--- a/init/Kconfig
+++ b/init/Kconfig
@@ -739,6 +739,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
@@ -746,6 +747,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.
@@ -753,6 +755,7 @@ 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.
@@ -760,8 +763,8 @@ config USER_NS
config PID_NS
bool "PID Namespaces"
- default n
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
@@ -769,8 +772,8 @@ config PID_NS
config NET_NS
bool "Network namespace"
- default n
depends on NAMESPACES && NET
+ default y
help
Allow user space to create what appear to be multiple instances
of the network stack.
--
1.7.0.4
_______________________________________________
Containers mailing list
contain...@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/containers
_______________________________________________
Devel mailing list
Devel@openvz.org
https://openvz.org/mailman/listinfo/devel
