I believe disabling CONFIG_NET_NS was the correct action for Lucid given
its impact on some widely used applications. According to policy
CONFIG_NET_NS should not have been enabled to begin with. Subsequent
config reviews have been more rigorous. If you have a product that is
dependent on this feature then lets figure out _why_ its not working.
CONFIG_NET_NS was officially enabled beginning with Natty (2.6.38).
Unfortunately, CONFIG_NET_NS is still incorrectly enabled in Maverick.
** Changed in: linux (Ubuntu Lucid)
Status: Triaged => Won't Fix
** Changed in: linux (Ubuntu Lucid)
Assignee: Canonical Kernel SRU Team (canonical-kernel-sru-team) => Tim
Gardner (timg-tpi)
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/844185
Title:
Removal of CONFIG_NET_NS from 2.6.32-32 breaks applications
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/844185/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
