From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with archive (Exim 4.43)
	id 1GvRhh-0002Ht-P8
	for mharc-grub-devel@gnu.org; Sat, 16 Dec 2006 00:03:21 -0500
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1GvRhg-0002HK-38
	for grub-devel@gnu.org; Sat, 16 Dec 2006 00:03:20 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1GvRhd-0002GX-Kn
	for grub-devel@gnu.org; Sat, 16 Dec 2006 00:03:19 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1GvRhd-0002GQ-Eb
	for grub-devel@gnu.org; Sat, 16 Dec 2006 00:03:17 -0500
Received: from [212.27.42.65] (helo=smtp8-g19.free.fr)
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1GvRhc-0008Ry-Un
	for grub-devel@gnu.org; Sat, 16 Dec 2006 00:03:17 -0500
Received: from saphi (boi78-1-82-232-198-173.fbx.proxad.net [82.232.198.173])
	by smtp8-g19.free.fr (Postfix) with ESMTP id 6BF275410
	for <grub-devel@gnu.org>; Sat, 16 Dec 2006 06:03:16 +0100 (CET)
Received: from gingold by saphi with local (Exim 3.36 #1 (Debian))
	id 1GvRkn-0000ei-00
	for <grub-devel@gnu.org>; Sat, 16 Dec 2006 06:06:33 +0100
Date: Sat, 16 Dec 2006 06:06:33 +0100
To: The development of GRUB 2 <grub-devel@gnu.org>
Message-ID: <20061216050633.GD2482@saphi>
References: <1161892715.17811.33.camel@basalt.austin.ibm.com>
	<20061027040907.GA2485@saphi> <1165622551.23364.66.camel@basalt>
	<1165960114.28426.23.camel@basalt>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1165960114.28426.23.camel@basalt>
User-Agent: Mutt/1.5.9i
From: Tristan Gingold <tgingold@free.fr>
Subject: Re: identifying module types
X-BeenThere: grub-devel@gnu.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: The development of GRUB 2 <grub-devel@gnu.org>
List-Id: The development of GRUB 2 <grub-devel.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/grub-devel>,
	<mailto:grub-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/grub-devel>
List-Post: <mailto:grub-devel@gnu.org>
List-Help: <mailto:grub-devel-request@gnu.org?subject=help>
List-Subscribe: <http://lists.gnu.org/mailman/listinfo/grub-devel>,
	<mailto:grub-devel-request@gnu.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Dec 2006 05:03:20 -0000

On Tue, Dec 12, 2006 at 03:48:34PM -0600, Hollis Blanchard wrote:
> On Fri, 2006-12-08 at 18:02 -0600, Hollis Blanchard wrote:
> > 
> > On the consumer side of multiboot (in this case Xen), we need to loop
> > over the tags, and when we find a module tag, how do we know which it
> > is? The Multiboot2 spec tells us "The order of modules is not
> > guaranteed." (Why not?) 
> 
> Of course, requiring that the order be preserved is the simplest
> solution, so unless there is a compelling reason to avoid that, I think
> we should avoid the UUID complexity.
I don't agree here.  Preserving the order is not enough.  The best example
is Xen: even if we agree that the first module is the dom0 kernel, the second
module may be either the dom0 initrd *or* the acm configuration file.  Both
are optional.

Tristan.