This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Ubuntu packages

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Ubuntu packages
From: Pete Ryland <pdr@xxxxxx>
Date: Wed, 1 Feb 2006 10:43:05 +0000
Delivery-date: Wed, 01 Feb 2006 10:53:02 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.11

I'm looking into creating .deb packages for Ubuntu's next release which will
be based on a patched 2.6.15 kernel.  I'm kinda wondering what you guys
think the best approach would be?

As I see it, the only way to maintain compatibility with the current Ubuntu
kernel (including all patches and included drivers) is to use Xen unstable
(and 3.0.2 when released) source, with the patched 2.6.15 Ubuntu kernel as
the "pristine" kernel, then apply Xen patches/sparse tree (manually if need
be) and build with Ubuntu's standard kernel config.  This is obviously
fraught with danger due to mutually exclusive patches, and the config
enabling things Xen doesn't like, so is there a better way?

       "If you could do Java over again, what would you change?"
     "I'd leave out classes" - James Gosling, at a Java User Group

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] Ubuntu packages, Pete Ryland <=