All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: partition numbering
Date: Sun, 17 Apr 2005 20:57:08 +0200	[thread overview]
Message-ID: <871x998c57.fsf@student.han.nl> (raw)
In-Reply-To: <9462cb437966802c2fb51c95b8c0a907@penguinppc.org> (Hollis Blanchard's message of "Sun, 17 Apr 2005 13:23:48 -0500")

Hollis Blanchard <hollis@penguinppc.org> writes:

> On Apr 17, 2005, at 12:44 PM, Marco Gerards wrote:
>
>> Hollis Blanchard <hollis@penguinppc.org> writes:
>>>
>>> If GRUB counts partition numbers different than Open Firmware, I
>>> consider this a bug that must be fixed. 0-based partition numbers are
>>> quite confusing enough.
>>
>> And I do not consider that a bug.  We can not confirm to the way every
>> OS/firmware implementation numbers its partitions.  This is *not*
>> about 0-basic partition numbers, but about how the same things can be
>> handled differently.  We can adapt to the most popular
>> implementations.  But I am sure things will fail someday.
>
> I agree we cannot match OS device names and numbering, though it would
> make users' lives much happier if we did. Actually, to brainstorm for
> a minute, what if we could install GRUB with a different device naming
> scheme per OS? Booting different OSs would then be a problem, but what
> about making each scheme easily distinguishable? For example, use
> "(linux:hda3)" or "(bsd:disk1s2)"?

That is not possible.  You can not say hda is the same as hd0.  In
GRUB on the PC hd0 means the first harddisk as the BIOS sees it AFAIK.
On linux hda means the primary master disk on an IDE controller.

I think it is too much work to do this and not worth the effort.  And
it will cause more problems than convenience.  Of course you can write
a module that makes it possible what you propose...

> Anyways, GRUB, as a bootloader that uses firmware services, surely
> must match firmware names and numbering. For example, on x86 you
> identify disks as "hd0" and "hd1" because this is how the firmware
> enumerates them.

Not for partitions, as I see it.

--
Marco




  reply	other threads:[~2005-04-17 19:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-13 16:54 [patch] set prefix on PPC Hollis Blanchard
2005-02-13 18:35 ` Marco Gerards
2005-02-13 19:52   ` Hollis Blanchard
2005-02-14 19:01     ` Marco Gerards
2005-02-15 16:39       ` Hollis Blanchard
2005-02-15 21:31         ` Marco Gerards
2005-02-20  0:21           ` Hollis Blanchard
2005-02-20 17:50             ` Marco Gerards
2005-02-24  4:44               ` Hollis Blanchard
2005-04-14 16:35                 ` Marco Gerards
2005-02-21 19:01 ` Marco Gerards
2005-02-24  4:40   ` Hollis Blanchard
2005-04-14 17:05     ` Marco Gerards
2005-04-17 17:10       ` partition numbering (was: set prefix on PPC) Hollis Blanchard
2005-04-17 17:44         ` partition numbering Marco Gerards
2005-04-17 18:23           ` Hollis Blanchard
2005-04-17 18:57             ` Marco Gerards [this message]
2005-04-17 19:24             ` Yoshinori K. Okuji
2005-04-17 19:45               ` Marco Gerards

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=871x998c57.fsf@student.han.nl \
    --to=metgerards@student.han.nl \
    --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.