From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1U43pk-0005pF-J5 for mharc-grub-devel@gnu.org; Sat, 09 Feb 2013 01:22:44 -0500 Received: from eggs.gnu.org ([208.118.235.92]:51844) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U43ph-0005nF-CZ for grub-devel@gnu.org; Sat, 09 Feb 2013 01:22:42 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1U43pe-0002Sc-G1 for grub-devel@gnu.org; Sat, 09 Feb 2013 01:22:41 -0500 Received: from [50.115.112.57] (port=36009 helo=slmp-550-94.slc.westdc.net) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U43pe-0002Ro-7W for grub-devel@gnu.org; Sat, 09 Feb 2013 01:22:38 -0500 Received: from c-24-9-205-42.hsd1.co.comcast.net ([24.9.205.42]:58559 helo=mingisapsycho.hsd1.co.comcast.net) by slmp-550-94.slc.westdc.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.80) (envelope-from ) id 1U43pW-002JQW-Hl; Fri, 08 Feb 2013 23:22:32 -0700 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: GRUB and the risk of block list corruption in extX From: Chris Murphy In-Reply-To: <51153345.2020509@ts.fujitsu.com> Date: Fri, 8 Feb 2013 23:22:29 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <0088990F-66E5-4F51-A9C4-3BD8963A6DA0@colorremedies.com> References: <51138645.4050405@ts.fujitsu.com> <51153345.2020509@ts.fujitsu.com> To: The development of GNU GRUB , Martin Wilck X-Mailer: Apple Mail (2.1499) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - slmp-550-94.slc.westdc.net X-AntiAbuse: Original Domain - gnu.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - colorremedies.com X-Get-Message-Sender-Via: slmp-550-94.slc.westdc.net: authenticated_id: whatever@colorremedies.com X-Source: X-Source-Args: X-Source-Dir: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 50.115.112.57 X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: The development of GNU GRUB List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Feb 2013 06:22:42 -0000 On Feb 8, 2013, at 10:17 AM, Martin Wilck = wrote: >> This is not a complete answer but one of my problems is that such >> requests don't even suply any kind of reason to go into such = installs. >> We nerd to consider usecases before even considering using an = approach >> which is known for some pretty serious problems. Will answer in more >> details later. >=20 > In my case, the reason is a multiboot setup based on chainloading the > indiviual installed OS's bootloaders from a central, primary = bootloader. Why do you specifically want a blocklist method of getting the primary = bootloader to load the second? What is your primary bootloader and = version? The only reason I can think of that you would need a blocklist, = is if your primary bootloader is so old that it doesn't understand the = file system the 2nd bootloader is installed on. In the case of Fedora = 18, default is /boot on it's own partition, on ext4; so if your primary = bootloader understands ext4, it doesn't need a blocklist to load GRUB2. = It can directly find and load /boot/grub2/i-386-pc/core.img. If the primary boot loader is GRUB2, it's capable of reading many file = systems, and then finding a distribution specific grub configuration = file and consuming it. Even legacy formats. > Recent GRUB2-based distributions like Fedora have removed this option, > and some users are dissatisfied with that.=20 If the enhancement in bug 886502 were to happen, would this enable your = primary boot loader to find either Fedora's grub.cfg, or core.img = instead of depending on a blocklist? https://bugzilla.redhat.com/show_bug.cgi?id=3D886502 Chris Murphy=