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] Re: tidy up requested

To: Ronald G Minnich <rminnich@xxxxxxxx>
Subject: [Xen-devel] Re: tidy up requested
From: Andi Kleen <ak@xxxxxxx>
Date: 11 Aug 2005 01:08:04 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Delivery-date: Wed, 10 Aug 2005 23:06:21 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <42FA8777.7000106@xxxxxxxx>
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>
References: <E1E2tgW-0006vl-00@xxxxxxxxxxxxxxxxx> <200508102321.49800.mark.williamson@xxxxxxxxxxxx> <42FA8777.7000106@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
Ronald G Minnich <rminnich@xxxxxxxx> writes:

> So I can not convince you to allow multiple versions of xen on one machine?
> People who are using 2.0 and porting to 3.0 (like me and newsham and
> ...) could sure use that setup!

The standard way to do that would be to support $(prefix) properly.
So you end up with $(prefix)/lib/xen ..  $(prefix)/sbin $(prefix)/etc ...
Like /opt/xen2/.... /opt/xen3/... etc.

The problem would be to make sure that all tools that read files
or execute programs know about the prefix.


Xen-devel mailing list