From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] UUID support
Date: Fri, 30 May 2008 16:07:34 +0200 [thread overview]
Message-ID: <20080530140734.GA3184@thorin> (raw)
In-Reply-To: <ca0f59980805300626o69a58b69y3a74f18947d3a04@mail.gmail.com>
On Fri, May 30, 2008 at 09:26:05PM +0800, Bean wrote:
> >
> > However, a problem with this is that it only works for i386-pc, untill we
> > define a way to store this for each variant.
> >
> > Perhaps we could instead use memdisk to store it? Rather than put a grub.cfg
> > in memdisk, which would require builtin normal.mod, we could put a simpler
> > file (let's call it 'env') with initial environment, in the binary format
> > you describe. Does that work?
> >
> > Then to support it in other platforms, we just need to implement memdisk in
> > them.
>
> We can use some function like grub_machine_get_env to return a pointer
> to the environment block, and parse it in main.c. The env block is
> string base, it can be used in any platform.
Sounds fine.
> BTW, since you have changed the filesystem structure, you need to add
> the uuid member to other fs modules as well, otherwise it will cause
> compile error.
Optional struct members are allowed (at least by gcc). I think we have many
incomplete struct declarations throurough the code.
--
Robert Millan
<GPLv2> I know my rights; I want my phone call!
<DRM> What good is a phone call… if you are unable to speak?
(as seen on /.)
next prev parent reply other threads:[~2008-05-30 14:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-29 15:13 [PATCH] UUID support Robert Millan
2008-05-29 16:50 ` Bean
2008-05-29 18:17 ` Robert Millan
2008-05-29 18:49 ` Bean
2008-05-30 10:41 ` Robert Millan
2008-05-30 13:14 ` Robert Millan
2008-05-30 13:26 ` Bean
2008-05-30 14:07 ` Robert Millan [this message]
2008-05-30 11:04 ` Robert Millan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080530140734.GA3184@thorin \
--to=rmh@aybabtu.com \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.