From: Robert Millan <rmh@aybabtu.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [RFC] Dynamic device.map
Date: Sat, 26 Dec 2009 14:25:51 +0100 [thread overview]
Message-ID: <20091226132551.GA20730@thorin> (raw)
In-Reply-To: <20091224211827.GH12122@thorin>
On Thu, Dec 24, 2009 at 10:18:27PM +0100, Robert Millan wrote:
> > No, I don't think we will. grub-probe is perfectly capable of mapping
> > /dev/sda1 to (hd0,1) even without device.map;
>
> I wasn't very fond of this because it's BIOS-specific. But I guess we can
> live with it.
On second thought, I'm really not convinced we need this kind of logic. It
seems a lot like a workaround.
Just leave it with (/dev/foo). If you remove device.map generation from
grub-install, you can remove the backward compatibility hack while at it.
Then we rely only on UUIDs.
In the future, we can rely on the initial value of $root as well, but this
would require some rework (disk / partition split).
--
Robert Millan
"Be the change you want to see in the world" -- Gandhi
next prev parent reply other threads:[~2009-12-26 13:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 14:28 [RFC] Dynamic device.map Colin Watson
2009-12-07 17:25 ` Colin Watson
2009-12-09 21:49 ` Robert Millan
2009-12-09 23:04 ` Colin Watson
2009-12-10 0:55 ` Robert Millan
2009-12-10 8:12 ` Colin Watson
2009-12-24 21:18 ` Robert Millan
2009-12-26 13:25 ` Robert Millan [this message]
2009-12-26 21:37 ` David Miller
2009-12-26 22:01 ` Robert Millan
2010-01-06 16:00 ` Colin Watson
2010-01-07 21:30 ` Robert Millan
2010-01-07 22:18 ` Bruce Dubbs
2010-01-07 22:33 ` Colin Watson
2010-01-08 5:27 ` Bruce Dubbs
2010-01-08 10:02 ` Felix Zielcke
2010-01-08 16:36 ` Bruce Dubbs
2009-12-10 10:12 ` Felix Zielcke
2009-12-24 21:17 ` Robert Millan
2009-12-25 17:02 ` Felix Zielcke
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=20091226132551.GA20730@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.