From: Martin Wilck <martin.wilck@ts.fujitsu.com>
To: grub-devel@gnu.org
Subject: Re: GRUB and the risk of block list corruption in extX
Date: Mon, 18 Feb 2013 18:16:46 +0100 [thread overview]
Message-ID: <512261FE.2090604@ts.fujitsu.com> (raw)
In-Reply-To: <0088990F-66E5-4F51-A9C4-3BD8963A6DA0@colorremedies.com>
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
next prev parent reply other threads:[~2013-02-18 18:06 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 10:47 GRUB and the risk of block list corruption in extX Martin Wilck
2013-02-08 11:44 ` Martin Wilck
2013-02-08 16:57 ` Vladimir 'phcoder' Serbinenko
2013-02-08 17:17 ` Vladimir 'phcoder' Serbinenko
2013-02-08 17:17 ` Martin Wilck
2013-02-08 18:42 ` Lennart Sorensen
2013-02-08 18:56 ` Bruce Dubbs
2013-02-08 18:58 ` Lennart Sorensen
2013-02-08 19:11 ` Andrey Borzenkov
2013-02-18 15:42 ` Martin Wilck
2013-02-09 6:22 ` Chris Murphy
2013-02-18 17:16 ` Martin Wilck [this message]
2013-02-18 21:07 ` Chris Murphy
2013-02-19 5:02 ` Andrey Borzenkov
2013-02-19 6:24 ` Chris Murphy
2013-02-19 8:43 ` Michael Chang
2013-02-19 9:06 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-02-19 18:54 ` Chris Murphy
2013-02-19 8:47 ` Martin Wilck
2013-02-19 18:56 ` Chris Murphy
2013-02-19 19:46 ` Martin Wilck
2013-02-19 9:37 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-02-19 12:58 ` Martin Wilck
2013-02-19 15:48 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-02-19 17:17 ` Martin Wilck
2013-02-19 5:26 ` Andrey Borzenkov
2013-02-19 10:54 ` Martin Wilck
2013-05-03 5:01 ` Andrey Borzenkov
2013-05-03 8:21 ` Martin Wilck
2013-05-03 19:21 ` Dr. Tilmann Bubeck
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=512261FE.2090604@ts.fujitsu.com \
--to=martin.wilck@ts.fujitsu.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).