From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: OF disk naming scheme (Re: another regression on Efika)
Date: Sun, 22 Jul 2007 22:25:05 +0200 [thread overview]
Message-ID: <20070722202505.GA9408@aragorn> (raw)
In-Reply-To: <87wswscxmy.fsf@xs4all.nl>
On Sun, Jul 22, 2007 at 04:37:41PM +0200, Marco Gerards wrote:
> Robert Millan <rmh@aybabtu.com> writes:
>
> > On Sat, Jul 14, 2007 at 12:16:16AM +0200, Robert Millan wrote:
> >> On Tue, Jul 10, 2007 at 09:26:27PM +0200, Jordi Mallach wrote:
> >> > On Tue, Jul 10, 2007 at 04:10:52PM +0200, Robert Millan wrote:
> >> > > What naming/numbering scheme does this follow when you add more disks?
> >> >
> >> > hd, hd1, hd2. Luckily Mozillion has Firewire disks.
> >>
> >> My Efika counts: hd, hd0 ...
> >>
> >> IEEE 1275 does not seem to cover this. What scheme should we follow when
> >> generating device.map ?
> >
> > Since "hd, hd1, hd2 ..." seems to be much more common, I propose we use that
> > and let user override it via device.map in case of disparity (which may only
> > happen in systems with more than 1 disk).
>
> Can we actually read via /proc or so how this mapping in reality is
> realised?
AFAIK we can only read the full OF path from /proc (with helper tools like
ofpath / ofpathname), but not the short alias which grub uses. These can only
be obtained when grub is running.
If the proposed solution is not good, maybe we could instead remap all disks
to "standard" grub device names (hd0, hd1..), which grub-mkdevicemap already
knows how to guess reasonably well.
--
Robert Millan
My spam trap is honeypot@aybabtu.com. Note: this address is only intended
for spam harvesters. Writing to it will get you added to my black list.
next prev parent reply other threads:[~2007-07-22 20:22 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 18:16 another regression on Efika Robert Millan
2007-07-02 21:14 ` Robert Millan
2007-07-04 16:18 ` Hollis Blanchard
2007-07-10 10:04 ` Jordi Mallach
2007-07-10 14:08 ` memory management issue (Re: another regression on Efika) Robert Millan
2007-07-10 20:32 ` Hollis Blanchard
2007-07-13 22:08 ` Robert Millan
2007-07-24 19:59 ` Robert Millan
2007-07-25 17:51 ` Hollis Blanchard
2007-07-25 20:08 ` Robert Millan
2007-07-25 23:25 ` Hollis Blanchard
2007-07-27 8:05 ` Robert Millan
[not found] ` <20070727103310.GA1539@powerlinux.fr>
2007-07-27 19:15 ` Robert Millan
2007-07-29 19:30 ` Robert Millan
2007-07-30 20:11 ` [PATCH] efika memory issues Robert Millan
2007-07-30 22:35 ` Hollis Blanchard
2007-07-31 14:38 ` Robert Millan
2007-07-31 15:55 ` Hollis Blanchard
2007-07-31 19:42 ` Robert Millan
2007-08-01 17:34 ` Hollis Blanchard
2007-08-01 18:27 ` Robert Millan
2007-09-30 20:10 ` [PATCH] fix memory management on efika/pegasos Robert Millan
2007-10-01 18:18 ` Marcin Kurek
2007-10-01 22:25 ` Marcin Kurek
2007-10-02 19:42 ` Robert Millan
2007-10-03 23:38 ` Marcin Kurek
2007-10-04 20:47 ` Robert Millan
2007-07-10 14:10 ` OF disk naming scheme (Re: another regression on Efika) Robert Millan
2007-07-10 19:26 ` Jordi Mallach
2007-07-13 22:16 ` Robert Millan
2007-07-22 9:33 ` Robert Millan
2007-07-22 14:37 ` Marco Gerards
2007-07-22 20:25 ` Robert Millan [this message]
2007-08-12 14:56 ` proposed solution using "ofpathname -a" (Re: OF disk naming scheme) Robert Millan
2007-08-05 10:03 ` updated regression diff (Re: another regression on Efika) 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=20070722202505.GA9408@aragorn \
--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.