From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1U7V6L-0000hr-Cd for mharc-grub-devel@gnu.org; Mon, 18 Feb 2013 13:06:05 -0500 Received: from eggs.gnu.org ([208.118.235.92]:59656) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U7UKj-0002LJ-Co for grub-devel@gnu.org; Mon, 18 Feb 2013 12:16:58 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1U7UKf-0005m2-PP for grub-devel@gnu.org; Mon, 18 Feb 2013 12:16:53 -0500 Received: from dgate10.ts.fujitsu.com ([80.70.172.49]:48773) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U7UKf-0005lW-Fa for grub-devel@gnu.org; Mon, 18 Feb 2013 12:16:49 -0500 DomainKey-Signature: s=s1536a; d=ts.fujitsu.com; c=nofws; q=dns; h=X-SBRSScore:X-IronPort-AV:Received:X-IronPort-AV: Received:Message-ID:Date:From:Organization:User-Agent: MIME-Version:To:Subject:References:In-Reply-To: X-Enigmail-Version:Content-Type:Content-Transfer-Encoding; b=gwcRB2VaAO1N8EVKwcOF02StK7pbVC9dKhkCxHSfOjHJq98OIp8HN1va OKL3dyrizMiiDh648swS8oz/D93U+unCWaMiR33jF1bvzzDC5FoszdpG2 nu40TOSUqoUDHL4GBsOptRfu3uwiKC39URH6DOXLkoPykRsD5F4yS5Sxa 6I9xKQo2aneM35m6bWqm1UyTNkM6gUrOl+wi1c98Ngj/HW0F7BQ/klNW/ euodnAhQJ5imdqp7NJrieGn7HkBtq; DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ts.fujitsu.com; i=@ts.fujitsu.com; q=dns/txt; s=s1536b; t=1361207810; x=1392743810; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=WXoQenWAqCUGvXwLplbR0aaFdBIx3EVXZimvFwR26wg=; b=DTLdaTzL3/4oDqfx47MxDUptb9YvorDQrvJwSDyZCgcz/94NHg4iFggU j5GXzOHlpIAvCXiiof/8IfppH3vyidqqyxeJf1Ws/ky/veY1r8oT01MU1 76A6w9szRw1eJdwp/4Zpo0BHHdx8p78pe0xAaG+L92y0Wp9xo5HyLndj8 r4+thSY/ODf0E9cqL3guFmprdeqH0qVLmTao1o5ODTAR0KRJe7N5ak0HK oPOTCuQsSKFaf2M8qDFD+qXPf9qqE; X-SBRSScore: None X-IronPort-AV: E=Sophos;i="4.84,688,1355094000"; d="scan'208";a="137282032" Received: from unknown (HELO abgdgate60u.abg.fsc.net) ([172.25.138.90]) by dgate10u.abg.fsc.net with ESMTP; 18 Feb 2013 18:16:47 +0100 X-IronPort-AV: E=Sophos;i="4.84,688,1355094000"; d="scan'208";a="54942421" Received: from unknown (HELO cooper.psw.pdbps.fsc.net) ([172.25.253.64]) by abgdgate60u.abg.fsc.net with ESMTP; 18 Feb 2013 18:16:47 +0100 Message-ID: <512261FE.2090604@ts.fujitsu.com> Date: Mon, 18 Feb 2013 18:16:46 +0100 From: Martin Wilck Organization: Fujitsu Technology Solutions User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130110 Thunderbird/17.0.2 MIME-Version: 1.0 To: grub-devel@gnu.org Subject: Re: GRUB and the risk of block list corruption in extX References: <51138645.4050405@ts.fujitsu.com> <51153345.2020509@ts.fujitsu.com> <0088990F-66E5-4F51-A9C4-3BD8963A6DA0@colorremedies.com> In-Reply-To: <0088990F-66E5-4F51-A9C4-3BD8963A6DA0@colorremedies.com> X-Enigmail-Version: 1.5.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.70.172.49 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: Mon, 18 Feb 2013 18:06:03 -0000 Chris, > Why do you specifically want a blocklist method of getting the primary bootloader to load the second? I may have expressed myself unclearly. What I want is the *secondary* boot loader to be able to load *its own code* from a partition header (e.g. ext4) using block lists. The primary boot loader in the setup I prefer is actually embedded in the MBR and thus doesn't use block lists. It will use "chainloader" command to access the boot sector of the secondary boot loader (well I guess that's also a primitve "block list" if you want to see it that way). > 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. Using chainloading has the advantage that the primary bootloader (it's indeed GRUB 0.9x in my case) doesn't have to understand the more advanced filesystems of newer distros. It's no problem to boot a btrfs distro in this way, and when Fedora 31 comes out with KlingonFS as default filesystem, my stupid Grub 0.9X will still be able to chainload it, as long as KlingonFS supports embedding a boot loader in its partition header. Fedora 18's GRUB2 will not be able to do that using a secondary "grub.cfg", unless someone backports a KlingonFS module for it (fortunately, GRUB2 would be able to chainload, too). I like the fact that GRUB2 is able to detect foreign installations and offer auto-generated boot menu entries for them. But there are some scenarios for which the primitive chainloading mechanism is better suited. > 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=886502 As long as I install F18 on extX, yes. But as explained above, it wouldn't be my preferred solution. Martin -- Dr. Martin Wilck PRIMERGY System Software Engineer x86 Server Engineering FUJITSU Fujitsu Technology Solutions GmbH Heinz-Nixdorf-Ring 1 33106 Paderborn, Germany Phone: ++49 5251 525 2796 Fax: ++49 5251 525 2820 Email: martin.wilck@ts.fujitsu.com Internet: http://ts.fujitsu.com Company Details: http://ts.fujitsu.com/imprint