From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [RFC] Dynamic device.map
Date: Thu, 07 Jan 2010 23:27:16 -0600 [thread overview]
Message-ID: <4B46C234.2010506@gmail.com> (raw)
In-Reply-To: <20100107223309.GD5847@riva.ucam.org>
Colin Watson wrote:
> On Thu, Jan 07, 2010 at 04:18:37PM -0600, Bruce Dubbs wrote:
>> Robert Millan wrote:
>>> On Wed, Jan 06, 2010 at 04:00:23PM +0000, Colin Watson wrote:
>>>>> Just leave it with (/dev/foo).
>>>> You mean literally with the parentheses? I don't understand, since /dev/
>>>> names will be unintelligible to GRUB when running outside an operating
>>>> system.
>>> Yes. This just means we'd have "set root=(/dev/foo)" statements in grub.cfg,
>>> but those are just meant as a backward compatibility hack for pre-UUID GRUB
>>> installs.
>> Are you are implying that UUID will be the only way? I don't use
>> initrd's on my systems so I need root=(hd0,x) or root=(/dev/foo).
>> AFAIK initrd is the only way to load with UUIDs.
>
> I think you're mixing up two different things. There are two 'root'
> variables involved:
>
> 1) GRUB's 'root' variable, its base for filesystem operations
> 2) The root= parameter passed to the Linux kernel, which identifies
> the desired root filesystem
>
> Robert is talking about 1), but whether you use an initrd/initramfs is
> only relevant to 2).
OK, I didn't realize set root was capable of using UUIDs. I did know
that the two root entries were different. I got that mixed up with the
search command combined with the root=UUID=... which I think needs initrd.
Do I have it right now?
Should 'set root' be renamed to 'set grubroot'? I think something like
that would prevent some confusion.
-- Bruce
next prev parent reply other threads:[~2010-01-08 5:27 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
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 [this message]
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=4B46C234.2010506@gmail.com \
--to=bruce.dubbs@gmail.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.