WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ppc-devel

Re: [Xen-devel] [PATCH 0/6][TOOLS][XM-TEST] [v2] Update xm-test to suppo

To: Dan Smith <danms@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 0/6][TOOLS][XM-TEST] [v2] Update xm-test to support new architectures
From: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Date: Mon, 2 Oct 2006 16:02:34 +0100
Cc: Xen-Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Tony Breeds <tony@xxxxxxxxxxxxxxxxxx>, XenPPC-devel <xen-ppc-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 02 Oct 2006 08:03:04 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <m34pumyfdd.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
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: <patchbomb.1159527414@xxxxxxxxxxxxxxxxxxxxxxxxx> <20061002122304.GC29149@xxxxxxxxxxxxxxxxxxxxxx> <m34pumyfdd.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Mon, Oct 02, 2006 at 07:14:06AM -0700, Dan Smith wrote:

> EM> The last time I built a xm-test ramdisk, the buildroot-snapshot
> EM> was broken, and I had to go back a few days to find a working one.
> EM> I'm wary of using buildroot-snapshot for that reason. 
> 
> Yes, we had this discussion last year sometime and agreed to use a
> known-good daily snapshot for that reason.  I think it's still a good
> idea, as most people are not (or should not be) building ramdisks
> anymore (now that Xensource hosts a binary for download).

Yes, I think that the best thing to do would be as Jimi suggests, and for us
to pick one known-good snapshot, and host it ourselves.  That way, the source
for the XenSource ramdisks will always be available and we don't have to rely
upon the upstream buildroot archive.

The next time I build a ramdisk I'll put the buildroot tar on
xm-test.xensource.com, and change the Makefile to refer to that instead.

Ewan.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>