Serge Hallyn wrote:
> @Joseph,
> 
> re-enabling CONFIG_NET_NS has been rejected.  As I understand it,
> because backport kernels are supported on LTS releases, that is seen as
> the right path for those requiring network namespaces.

At least one other person on this ticket asserted that the backport
kernels are too unreliable for their taste.  Bringing in a whole new
kernel to reenable one option sounds like lunacy to me.

I am not enthusiastic about this solution -- I would rather reroll the
LTS 2.6.32 kernels (as they appear on lucid-security) with a trivial
in-house patch that reenables cgroups, than to run a completely new
kernel from backports.

And indeed, as soon as I see a kernel USN that worries me
sufficiently, that is exactly what I will do.  Until then I have
simply pinned the kernel at 2.6.32-31.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/790863

Title:
  Unable to start lxc container after update to 2.6.32-32

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/790863/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to