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] Clean up struct grub_module_header
Date: Mon, 24 Aug 2009 01:11:31 +0200	[thread overview]
Message-ID: <20090823231131.GA26199@thorin> (raw)
In-Reply-To: <d7ead6de0908230408h2c23bb01q83bff9466a96d21a@mail.gmail.com>

On Sun, Aug 23, 2009 at 01:08:05PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> On Sun, Aug 23, 2009 at 12:50 PM, Robert Millan<rmh@aybabtu.com> wrote:
> > On Sat, Aug 22, 2009 at 02:10:12AM -0400, Pavel Roskin wrote:
> >> +enum
> >> +{
> >> +  OBJ_TYPE_ELF,
> >> +  OBJ_TYPE_MEMDISK,
> >> +  OBJ_TYPE_CONFIG
> >> +};
> >
> > Do we actually use OBJ_TYPE_CONFIG ?  I think it's there in the framework,
> > but we don't provide any means to use it.  Instead, grub-mkrescue puts grub.cfg
> > in the memdisk filesystem.
> >
> > Does it even make sense to support this object type?  AFAICT the situation has
> > been like this for a long while and nobody complained.
> >
> Actually OBJ_TYPE_CONFIG is useful and it provides a way to execute a
> file with rescue parser before other parsers are available. It's
> useful to find root in special configurations. One of my TODO items is
> to replace (UUID=...)/ syntax with using search command based on this
> feature

Ok.  I'm not very fond of the (UUID=...) hack either (yeah, I guess I'm the
one to blame for it).

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."



  reply	other threads:[~2009-08-23 23:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-22  6:10 [PATCH] Clean up struct grub_module_header Pavel Roskin
2009-08-23 10:50 ` Robert Millan
2009-08-23 11:08   ` Vladimir 'phcoder' Serbinenko
2009-08-23 23:11     ` Robert Millan [this message]
2009-09-24 13:40 ` 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=20090823231131.GA26199@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.