From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1KKIr4-0004rT-FI for mharc-grub-devel@gnu.org; Sat, 19 Jul 2008 16:16:34 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KKIr2-0004pl-IT for grub-devel@gnu.org; Sat, 19 Jul 2008 16:16:32 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KKIr0-0004nj-2E for grub-devel@gnu.org; Sat, 19 Jul 2008 16:16:31 -0400 Received: from [199.232.76.173] (port=34267 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KKIqz-0004nX-Ss for grub-devel@gnu.org; Sat, 19 Jul 2008 16:16:29 -0400 Received: from ns39764.ovh.net ([91.121.25.85]:58845 helo=nexedi.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KKIqz-0002PV-NG for grub-devel@gnu.org; Sat, 19 Jul 2008 16:16:29 -0400 Received: from [10.8.0.46] (unknown [10.8.0.46]) by nexedi.com (Postfix) with ESMTP id A30783D991 for ; Sat, 19 Jul 2008 22:22:21 +0200 (CEST) From: "Yoshinori K. Okuji" Organization: enbug.org To: The development of GRUB 2 Date: Sat, 19 Jul 2008 22:16:23 +0200 User-Agent: KMail/1.9.9 References: <1216040584.9995.52.camel@dv> <200807160132.18470.okuji@enbug.org> <20080719150624.GD23778@thorin> In-Reply-To: <20080719150624.GD23778@thorin> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200807192216.23882.okuji@enbug.org> X-detected-kernel: by monty-python.gnu.org: Linux 2.6 (newer, 3) Subject: Re: Next release? 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: Sat, 19 Jul 2008 20:16:32 -0000 On Saturday 19 July 2008 17:06:24 Robert Millan wrote: > On Wed, Jul 16, 2008 at 01:32:18AM +0200, Yoshinori K. Okuji wrote: > > On Wednesday 16 July 2008 01:21:57 Pavel Roskin wrote: > > > On Wed, 2008-07-16 at 01:15 +0200, Yoshinori K. Okuji wrote: > > > > OK. Then how do you install GRUB into (hd1) in a development machine, > > > > which is (hd0) in a booting machine? When GRUB may not correctly > > > > determine BIOS drives, do you want to just give up? > > > > > > The boot drive can be determined at boot. > > > > > > Granted, there are buggy BIOSes, but we handle it already. All we need > > > is to encode into the bootloader that it was installed on a hard drive > > > (actually, not on a floppy, real or emulated), and the bootloader would > > > use 0x80 rather than the value from BIOS. > > > > > > We don't need specific drive numbers like 0x81. We need one bit of > > > information, and we can figure it out at the install time. > > > > If a boot drive is the same as a root drive, you are right. Otherwise we > > need to do so. > > > > I think we have seen tons of examples with GRUB Legacy which may not be > > solved automatically in all cases. If one digs into the archive of > > bug-grub, I guess several cases would be found easily. With GRUB 2, we > > can avoid embedding BIOS drive numbers in many cases, using UUIDs or > > labels or files. But this does not always work, so I am afraid that we > > need to support device.map, even if it is an evil necessity. > > Which cases are there that can't be fixed by using UUIDs? In any case where UUIDs are not used. I am totally against ripping off device.map. Pavel's idea is too idealistic, and that regresses the flexibility. Regards, Okuji