All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Environment block support for grub2
Date: Sat, 14 Jun 2008 20:32:57 +0200	[thread overview]
Message-ID: <20080614183257.GG5636@thorin> (raw)
In-Reply-To: <ca0f59980806132041v4bd62e6ch9feb69672bcbbe50@mail.gmail.com>

On Sat, Jun 14, 2008 at 11:41:18AM +0800, Bean wrote:
> 
> Hi,
> 
> No problem, I can find another name.

Sorry, my mistake.  I complained about $root being inappropiate for early
stage use, but after that I noticed that $root is used in every stage to
refer to "whatever drive we're currently accessing";  even before $prefix
is initialised!

I'm fine with $root if nobody objects.

> BTW, there are now two schemes for locating device at boot, the
> environment block and robert's uuid device, which one do you favor, or
> is there other scheme you prefer ?

I think there's no problem with having two schemes as long as they don't
take extra core.img space (except for the rare use cases they're intended
to) and don't conflict with each other.

As for the "findroot" approach, I have two comments/ideas:

  - Since findroot.mod is basicaly an heuristic, and it's possible we may
    want different kinds of methods that work similarly, how about
    calling it "findroot_by_file" or something like that?  Then we could
    have a separate module for "findroot_by_uuid", etc.

  - I think your idea has the potential of obsoleting some parts of our
    init routines, maybe (if we're lucky) making kernel.img smaller.  For
    example, we currently make grub_prefix a static length string (could it
    be dynamic? -> less space); then try to extract $root from it, since we
    embedded it in the same place (if we had a scheme to specify it
    separately -> less code to parse it).

-- 
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 /.)



  reply	other threads:[~2008-06-14 18:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-30 20:27 [PATCH] Environment block support for grub2 Bean
2008-05-31 10:10 ` Robert Millan
2008-05-31 10:54   ` Bean
2008-05-31 11:39     ` Robert Millan
2008-05-31 12:09       ` Bean
2008-05-31 15:09         ` Bean
2008-06-03 21:09           ` Robert Millan
2008-06-04  3:49             ` Bean
2008-06-06 16:43               ` UUID-based boot (Re: [PATCH] Environment block support for grub2) Robert Millan
2008-06-06 17:22                 ` Bean
2008-06-06 22:03                   ` Robert Millan
2008-06-07  4:33                     ` Bean
2008-06-08 19:26                       ` Robert Millan
2008-06-07  7:24                     ` Vesa Jääskeläinen
2008-06-06 23:31                   ` [PATCH] ntfs UUIDs (Re: UUID-based boot (Re: [PATCH] Environment block support for grub2)) Robert Millan
2008-06-07  5:44                     ` Tomáš Ebenlendr
2008-06-08  3:34                       ` Pavel Roskin
2008-06-08 19:19                         ` Robert Millan
2008-05-31 15:21         ` [PATCH] Environment block support for grub2 Robert Millan
2008-06-13 22:48           ` Yoshinori K. Okuji
2008-06-14  3:41             ` Bean
2008-06-14 18:32               ` Robert Millan [this message]
2008-06-14 19:22                 ` Bean

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=20080614183257.GG5636@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.