On Mon, 2009-08-10 at 22:36 +0300, Roman Kyrylych wrote:
On Mon, Aug 10, 2009 at 22:33, Aaron Griffin<aaronmgriffin@gmail.com> wrote:
On Mon, Aug 10, 2009 at 2:31 PM, Pierre Schmitz<pierre@archlinux.de> wrote:
Am Montag 10 August 2009 21:04:10 schrieb Tobias Powalowski:
Due to the slicehost issue, shall we wait until they react on this? I'm don't like to depend on others for our package upgrades. Any other opinions?
We cannot wait for every single provider to catch up; so why do this with this one here? We don't support keeping old versions of packages while updating all others; and that's what we have here in the end.
I agree with Pierre here. Even though I do have a slice, management of that slice is _my_ job. I've already attempted (and failed) the upgrade, so am aware of the problem. Adding udev to IgnorePkg isn't too hard, and that's kinda what it's made for
BTW, can anyone explain why it is not possible to use newer kernel compiled with support for running under Xen instead of provided? I thought that only OpenVZ and similar stuff requires the same kernel as on host.
The kernel has to match the interface and architecture of the hypervisor. Besides that, the kernel usually doesn't get booted from your installation, but from the host installation. You can't just replace a xen kernel from the domU side, it has to happen from dom0.