[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: identifying module types
From: |
Tristan Gingold |
Subject: |
Re: identifying module types |
Date: |
Sat, 16 Dec 2006 06:06:33 +0100 |
User-agent: |
Mutt/1.5.9i |
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.