[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] Re: debian

  • To: <brianw@xxxxxxxxxxxx>
  • From: "James Harper" <JamesH@xxxxxxxxxxxxxxxx>
  • Date: Tue, 14 Dec 2004 10:29:38 +1100
  • Cc: "Xen Devel Mailing List" <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Mon, 13 Dec 2004 23:24:41 +0000
  • List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
  • Thread-index: AcThJxxS4Dzq/zY9RBOL0nkOVARFqwARD94Q
  • Thread-topic: [Xen-devel] Re: debian

> This is why I use kver-extraver-privmode as the uname -r in
> xenlinuxbuilder. You can specify extraversion in make-kpkg and avoid
> this kind of conflict in most things.
> > I would say this is a bug - the Xen postinst scripts are not those
> > normal i386 kernels I believe, so they need fixing. I have never
> > initrd kernels with Xen.
> Probably because the initrd creation scripts for i386-xen don't exist
> yet. Probably just a symlink to the normal i386 in debian would do the
> trick. :)

I can test that pretty easy if you tell me how to do it.

One other thing I noticed was that a second make-kpkg produced a kernel
package with almost no modules, and a third make-kpkg had even less
modules and didn't actually do any building. I may have done something
wrong to trigger this but it also may be a bug.



SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.