On 6/9/10 12:50 PM, Paul van Genderen wrote:
Is it possible to upgrade an existing vm or container?
If the vm is running a 2.6.18, then the upgrade will fail as it will on
any non-vms. The reason xen was mentioned is that many dom0's run 2.6.18
and many domU's run the dom0's kernel, so this
Any status updates? How quickly might this get into SRU?
Thanks,
D.
--
tar/gnulib bug prevents bootstraping Lucid on Dapper, causes Lucid upgrade to
abort on older linux kernels (e.g. in a chroot or Xen VM)
https://bugs.launchpad.net/bugs/539814
You received this bug notification because you
@Steve: I agree, i think this is the best solution, given how little
time we have before release.
How do distributions upgrades work? I just downloaded upgrade-manager-
core and was greeted by a bunch of python scripts... which means I'm not
gonna look through them. Does anyone know how this
Steve,
If this is the case, one could make the claim, that Dapper servers will
also have this problem as they should be supported until 2011 iirc? The
stable kernel in Dapper is 2.6.15.
On a side note this will affect most Xen and XenServer Server's (which
almost all run 2.6.18) which imho is
Snippet from 2.6.18 kernel ouput with old tar and with the patched
version.
** Attachment added: 2.6.18 tar output
http://launchpadlibrarian.net/45043681/tar.log
--
tar/gnulib bug prevents bootstraping Lucid on Dapper, causes Lucid upgrade to
abort on older linux kernels (e.g. in a chroot
Andrew,
Your patched worked great. I'm running 2.6.18-164.15.1.el5xen
--
tar/gnulib bug prevents bootstraping Lucid on Dapper, causes Lucid upgrade to
abort on older linux kernels (e.g. in a chroot or Xen VM)
https://bugs.launchpad.net/bugs/539814
You received this bug notification because you
Like i said, i'm just sure that I'm not the only planning to use
debootstrap quite extensively, i would go as far as to say that this is
my main install method. If this makes it in shortly after release, then
thats fine as well.
--
FFe: Sync tar 1.23-1 (main) from Debian squeeze (main)
Is there any chance that this will get fixed before the lucid release. I
find this quite annoying as i have server machines running 2.6.18
(mostly rhel/centos) with which i want to use debootstrap to install
lucid for chroot or for virtual machines. I really don't want to have to
hack debootstrap
