From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: Re: tidy up requested Date: Wed, 10 Aug 2005 18:14:41 -0500 Message-ID: <42FA8A61.5060905@us.ibm.com> References: <200508102321.49800.mark.williamson@cl.cam.ac.uk> <42FA8777.7000106@lanl.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Andi Kleen Cc: Ian Pratt , xen-devel@lists.xensource.com, Ronald G Minnich List-Id: xen-devel@lists.xenproject.org Andi Kleen wrote: >Ronald G Minnich 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. > > Yeah, I've got a pretty good feel for what needs to change. Not surprisingly, Xend will be the most pain here. I think we can actually be smart though and avoid having to know the prefix at compile time. Regards, Anthony Liguori >-Andi > >_______________________________________________ >Xen-devel mailing list >Xen-devel@lists.xensource.com >http://lists.xensource.com/xen-devel > > >