Quoting Daniel Lezcano (daniel.lezc...@free.fr): > The pid namespace is enabled by default in different distros > and the different bugs were fixed when they were reported. > No new bug is reported since some time now, so I guess it's safe to > remove the experimental condition on this subsystem. > > Signed-off-by: Daniel Lezcano <daniel.lezc...@free.fr>
I'd say so. Acked-by: Serge Hallyn <se...@us.ibm.com> > --- > init/Kconfig | 7 ++----- > 1 file changed, 2 insertions(+), 5 deletions(-) > > Index: linux-2.6/init/Kconfig > =================================================================== > --- linux-2.6.orig/init/Kconfig > +++ linux-2.6/init/Kconfig > @@ -690,17 +690,14 @@ config USER_NS > If unsure, say N. > > config PID_NS > - bool "PID Namespaces (EXPERIMENTAL)" > + bool "PID Namespaces" > default n > - depends on NAMESPACES && EXPERIMENTAL > + depends on NAMESPACES > 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 > > _______________________________________________ > Containers mailing list > contain...@lists.linux-foundation.org > https://lists.linux-foundation.org/mailman/listinfo/containers _______________________________________________ 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
