From: Martin Wilck <martin.wilck@ts.fujitsu.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: GRUB and the risk of block list corruption in extX
Date: Fri, 08 Feb 2013 18:17:57 +0100 [thread overview]
Message-ID: <51153345.2020509@ts.fujitsu.com> (raw)
In-Reply-To: <CAEaD8JPvEzCy=msDCzezzAn25Nc-n6cLfSTU2Jao1z2MS3UbmA@mail.gmail.com>
> 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.
In my case, the reason is a multiboot setup based on chainloading the
indiviual installed OS's bootloaders from a central, primary bootloader.
This is easily accomplished by installing the individual OS's
bootloaders in their respective "/" or "/boot" partitions. Linux
distributions have encouraged this kind of setup over several years -
"install boot loader in first sector of root/boot partition" used to be
a prominent option somewhere in the installation process (these
distributions were usually GRUB 0.9x based - GRUB 0.9x developers didn't
seem to have a big issue with stage1_5 being loaded via block lists).
Recent GRUB2-based distributions like Fedora have removed this option,
and some users are dissatisfied with that. I would like to understand
what the actual risk is. So I'd appreciate examples for the "pretty
serious problems" you mention.
Regards
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-08 17:18 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 [this message]
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
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=51153345.2020509@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).