I've opened bug 826544 against update-manager to propose that
hardy->lucid updates should currently not happen until this ticket is
properly resolved.

It's great to hear that OpenVZ, LXC, Virtuozzo and whatnot hosts are not
affected (if that is indeed the case).  I don't know what my hoster is
running and I shouldn't have to.  From some of the messages I exchanged
with the owner I'd venture to guess that he is running linux-
vserver.org.  FWIW.  I've had plans to replicate that setup locally, but
never got around to it.

So, where are we?  It seems that Clint's efforts to backport upstart
have lately stalled.  And unless I am mistaken that was about fixing the
host side of things anyhow.  Upstart-dummy was put forward as a possible
workaround.  I've read the page a few times but I'm not yet sure I fully
understand the necessary steps.  I'd actually like to see that script
packaged so that things are easier to replicate on different machines.
I'm not much of a wizzard when it comes to packaging python, so I'd
appreciate some collaboration for further evaluation.

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

Title:
  init: support chroots

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/430224/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to