From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] search -d|--disk
Date: Tue, 23 Jun 2009 23:55:07 +0200 [thread overview]
Message-ID: <20090623215507.GA10614@thorin> (raw)
In-Reply-To: <1245791842.3204.8.camel@mj>
On Tue, Jun 23, 2009 at 05:17:22PM -0400, Pavel Roskin wrote:
> >
> > QEMU has a feature in which you can specify the boot drive from command
> > line (-boot parameter). After i386-qemu port is merged, I plan to add
> > some code to read this from CMOS and export it to some variable.
> >
> > When on GRUB, it is up to the user to decide what "boot this drive" means.
> > An interesting option is to search for a specific file in the disk we're told,
> > and then act upon it (e.g. configfile /grub.cfg, multiboot /grub.elf,
> > linux /vmlinuz, whatever).
>
> I think the convention is to load the first sector of the disk.
That's the BIOS convention, which is useful when there's a BIOS. Otherwise
there isn't much you can do with 512 bytes of code.
> Maybe we could pass
> environment variables using some qemu facility.
Yes, qemu exports -boot parameter to CMOS, just like memory size. GRUB can
read it from there.
> > I implemented it only for files. It's trivial to do it for labels/uuids
> > too, but it's annoying because doing so results in code duplication.
>
> Yes, it's annoying, but partial implementations are annoying to the end users.
>
> Perhaps it should be possible to implement disk filtering using the
> mechanism used to skip floppies.
I'll see what I can do.
--
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."
next prev parent reply other threads:[~2009-06-23 21:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 23:48 [PATCH] search -d|--disk Robert Millan
2009-06-23 1:51 ` Pavel Roskin
2009-06-23 11:50 ` Robert Millan
2009-06-23 21:17 ` Pavel Roskin
2009-06-23 21:55 ` Robert Millan [this message]
2009-06-24 3:03 ` Arthur Marsh
2009-06-24 12: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=20090623215507.GA10614@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.