From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with archive (Exim 4.43)
	id 1GvRg5-00017c-LX
	for mharc-grub-devel@gnu.org; Sat, 16 Dec 2006 00:01:41 -0500
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1GvRg3-00015s-Lf
	for grub-devel@gnu.org; Sat, 16 Dec 2006 00:01:39 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1GvRg2-00015T-2p
	for grub-devel@gnu.org; Sat, 16 Dec 2006 00:01:39 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1GvRg1-00015Q-Ro
	for grub-devel@gnu.org; Sat, 16 Dec 2006 00:01:37 -0500
Received: from [212.27.42.28] (helo=smtp2-g19.free.fr)
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1GvRg1-0008IH-9G
	for grub-devel@gnu.org; Sat, 16 Dec 2006 00:01:37 -0500
Received: from saphi (boi78-1-82-232-198-173.fbx.proxad.net [82.232.198.173])
	by smtp2-g19.free.fr (Postfix) with ESMTP id C7EF9778A
	for <grub-devel@gnu.org>; Sat, 16 Dec 2006 06:01:36 +0100 (CET)
Received: from gingold by saphi with local (Exim 3.36 #1 (Debian))
	id 1GvRjB-0000eY-00
	for <grub-devel@gnu.org>; Sat, 16 Dec 2006 06:04:53 +0100
Date: Sat, 16 Dec 2006 06:04:53 +0100
To: The development of GRUB 2 <grub-devel@gnu.org>
Message-ID: <20061216050453.GC2482@saphi>
References: <1161892715.17811.33.camel@basalt.austin.ibm.com>
	<20061027040907.GA2485@saphi> <1165622551.23364.66.camel@basalt>
	<20061209053133.GA2526@saphi> <1165956970.28426.21.camel@basalt>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1165956970.28426.21.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:01:40 -0000

[Sorry for the late reply]
On Tue, Dec 12, 2006 at 02:56:10PM -0600, Hollis Blanchard wrote:
> On Sat, 2006-12-09 at 06:31 +0100, Tristan Gingold wrote:
> > On Fri, Dec 08, 2006 at 06:02:31PM -0600, Hollis Blanchard wrote:
> > > On Fri, 2006-10-27 at 06:09 +0200, Tristan Gingold wrote:
[...]
> > > One option is a fixed-length encoded field, say 32 bytes wide. To avoid
> > > namespace collisions, we could require that projects prefix types with
> > > their project name, which must be at least 4 bytes.
> > Nb: UUID are 16 bytes and collisions are avoided.
> 
> Please detail your proposal.
You have exposed it just below better than I could.
 
> > I prefer the use of a fixed-length field.
> 
> Me too.
> 
> > But that's my own opinion (UUID are
> > easy to generate, to compare and well-known - do not reinvent the wheel).
> 
> UUIDs, e.g.  550e8400-e29b-41d4-a716-446655440000, are also completely
> unintelligible, so they cannot be the only answer.
Sure.
 
> So far you seem to be advocating the following:
>         module [--type TYPE | --uuid UUID] file
>         
> TYPE: an English word that GRUB translates to a UUID. GRUB must therefor
> maintain a table of known types and their associated UUIDs.
> UUID: a 16-byte number which can be represented as 36 ASCII characters
> (including hyphens).
> 
> How should we generate the UUIDs for the table in GRUB? I'll just run
> uuidgen here and create them myself?
Yes.

> Does anybody object to this scheme?
Tristan.