From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1DNF0r-0003YO-T0 for mharc-grub-devel@gnu.org; Sun, 17 Apr 2005 15:00:58 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DNEzm-0003Fs-W5 for grub-devel@gnu.org; Sun, 17 Apr 2005 14:59:51 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DNEzR-00034R-4E for grub-devel@gnu.org; Sun, 17 Apr 2005 14:59:37 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DNEzP-00032g-Mm for grub-devel@gnu.org; Sun, 17 Apr 2005 14:59:27 -0400 Received: from [145.74.66.11] (helo=mail-cn.han.nl) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DNEya-00014r-Vp for grub-devel@gnu.org; Sun, 17 Apr 2005 14:58:37 -0400 Received: from vscan-cn.han.nl (venus.han.nl [145.74.65.6]) by mail-cn.han.nl (Postfix) with ESMTP id 813BF9EFB for ; Sun, 17 Apr 2005 20:57:13 +0200 (CEST) Received: from mail-cn.han.nl ([145.74.66.11]) by vscan-cn.han.nl (venus.han.nl [145.74.65.6]) (amavisd-new, port 10024) with ESMTP id 23788-06 for ; Sun, 17 Apr 2005 20:57:10 +0200 (CEST) Received: from mail1.han.nl (mail1.han.nl [145.74.103.11]) by mail-cn.han.nl (Postfix) with ESMTP id 477E99E97 for ; Sun, 17 Apr 2005 20:57:08 +0200 (CEST) Received: from localhost.localdomain (mgerards.xs4all.nl [82.92.27.129]) by mail1.han.nl (Postfix) with ESMTP id 04970C045 for ; Sun, 17 Apr 2005 20:57:08 +0200 (CEST) Mail-Copies-To: metgerards@student.han.nl To: The development of GRUB 2 References: <20050213165452.GA4503@miracle> <874qg5pwju.fsf@student.han.nl> <612fe64ec525dea867c45362eb985354@penguinppc.org> <87br8hffvf.fsf@student.han.nl> <0c5e52fe3d2654cb915852cd96d0d7ca@penguinppc.org> <8764yl8fi6.fsf@student.han.nl> <9462cb437966802c2fb51c95b8c0a907@penguinppc.org> From: Marco Gerards Date: Sun, 17 Apr 2005 20:57:08 +0200 In-Reply-To: <9462cb437966802c2fb51c95b8c0a907@penguinppc.org> (Hollis Blanchard's message of "Sun, 17 Apr 2005 13:23:48 -0500") Message-ID: <871x998c57.fsf@student.han.nl> User-Agent: Gnus/5.1007 (Gnus v5.10.7) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new (2.2.0) at vscan-cn.han.nl Subject: Re: partition numbering X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Apr 2005 19:00:54 -0000 Hollis Blanchard writes: > On Apr 17, 2005, at 12:44 PM, Marco Gerards wrote: > >> Hollis Blanchard 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