From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: GRUB device names wrt. ieee1275
Date: Wed, 18 Mar 2009 11:18:46 +0100 [thread overview]
Message-ID: <20090318101846.GD20072@thorin> (raw)
In-Reply-To: <20090315.154116.198032129.davem@davemloft.net>
On Sun, Mar 15, 2009 at 03:41:16PM -0700, David Miller wrote:
> From: Robert Millan <rmh@aybabtu.com>
> Date: Sun, 15 Mar 2009 16:45:31 +0100
>
> > It's not an absolute must that device names are unique. You can still
> > identify partitions by their filesystem UUID or label, and in fact this
> > is what our default scripts (grub-mkconfig) do anyway.
>
> Things like UUID and labels are not an option for the 512-byte
> boot block where I have to know the exact OBP path of the boot
> device, and this is what the GRUB kernel fetches from the
> 'bootpath' environment variable to compose the root device
> and path.
What 512-byte boot block?
--
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-03-18 10:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-14 22:14 GRUB device names wrt. ieee1275 David Miller
2009-03-14 23:44 ` phcoder
2009-03-15 5:24 ` David Miller
2009-03-15 9:22 ` Vesa Jääskeläinen
2009-03-15 22:52 ` David Miller
2009-03-15 15:45 ` Robert Millan
2009-03-15 22:41 ` David Miller
2009-03-18 10:18 ` Robert Millan [this message]
2009-03-18 20:55 ` David Miller
2009-03-18 21:01 ` David Miller
2009-03-22 0:41 ` phcoder
2009-03-22 0:48 ` phcoder
2009-03-22 1:57 ` David Miller
2009-03-22 1:56 ` David Miller
[not found] ` <49C61E3D.3040901@gmail.com>
[not found] ` <20090322.153022.233646325.davem@davemloft.net>
2009-03-22 22:51 ` phcoder
2009-03-23 1:13 ` David Miller
2009-03-22 12:22 ` Robert Millan
2009-03-23 4:23 ` David Miller
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=20090318101846.GD20072@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.