Skip to main content
Unix & Linux

Return to Question

The crux of the linked question seems to be to avoid recompiling.
Source Link
Stephen Kitt
Stephen Kitt
  • 481.3k
  • 60
  • 1.2k
  • 1.4k

I once asked how Linux namespaces could be disabled withwithout recompiling. One of the comments asked if I meant without building with CONFIG_USER_NS=n and the answer my question received said to set to user.max_*_namespaces to 0. I have recently discovered that there is also a CONFIG_NAMESPACES build parameter. Does this mean namespaces are still usable even if user.max_*_namespaces are all 0?

I once asked how Linux namespaces could be disabled with recompiling. One of the comments asked if I meant without building with CONFIG_USER_NS=n and the answer my question received said to set to user.max_*_namespaces to 0. I have recently discovered that there is also a CONFIG_NAMESPACES build parameter. Does this mean namespaces are still usable even if user.max_*_namespaces are all 0?

I once asked how Linux namespaces could be disabled without recompiling. One of the comments asked if I meant without building with CONFIG_USER_NS=n and the answer my question received said to set to user.max_*_namespaces to 0. I have recently discovered that there is also a CONFIG_NAMESPACES build parameter. Does this mean namespaces are still usable even if user.max_*_namespaces are all 0?

Source Link
Melab
Melab
  • 4.4k
  • 10
  • 41
  • 59

CONFIG_NAMESPACES, CONFIG_USER_NS, and user.max_*_namespaces

I once asked how Linux namespaces could be disabled with recompiling. One of the comments asked if I meant without building with CONFIG_USER_NS=n and the answer my question received said to set to user.max_*_namespaces to 0. I have recently discovered that there is also a CONFIG_NAMESPACES build parameter. Does this mean namespaces are still usable even if user.max_*_namespaces are all 0?