From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Fix when installing on pationless but partionable medium
Date: Wed, 22 Jul 2009 19:16:12 +0200 [thread overview]
Message-ID: <20090722171612.GC8706@thorin> (raw)
In-Reply-To: <20090719100741.GA12723@riva.ucam.org>
On Sun, Jul 19, 2009 at 11:07:41AM +0100, Colin Watson wrote:
> On Sat, Jul 18, 2009 at 09:17:41PM +0200, Robert Millan wrote:
> > On Sat, Jul 18, 2009 at 09:01:38PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> > > On Sat, Jul 18, 2009 at 8:45 PM, Robert Millan<rmh@aybabtu.com> wrote:
> > > > I might be missing something about this check, but GRUB doesn't require that
> > > > the boot flag is present. Therefore, its non presence doesn't imply this is
> > > > not a real msdos label.
> > >
> > > He refers to boot flag as a byte in msdos structure which can only be
> > > 0x00 (not set) or 0x80 (set)
> >
> > Yes. GRUB's boot.img doesn't do anything with it AFAICT.
>
> That's as may be, sure; but checking that that byte is one of the two
> permitted values in all four partitions happens to be a good sanity
> check for whether it's really an MS-DOS label or in fact something else.
As a bootloader, most of the decisions GRUB takes have a critical effect. We
can't make GRUB take those decisions based on heuristic. If we determine
that something ought to be done, and we do it, we're taking responsibility for
it. Bootloader-related breakage tends to be severe, and we can't afford to
be blamed for it just because "our heuristic got it wrong".
Going down this path, if our heuristic is not good enough, we'll have to
improve it. We'd make it more complex and check for more things. But no
matter what we do, it can never be completely reliable.
Similarly, and as I said before (in this thread or another, I'm not sure), the
situation in which someone using a _sane_ MBR label with a sane filesystem in
it is our primary use case, and the ability of GRUB to install in it must not
depend on heuristic.
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
next prev parent reply other threads:[~2009-07-22 17:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-17 16:41 [PATCH] Fix when installing on pationless but partionable medium Vladimir 'phcoder' Serbinenko
2009-07-17 16:51 ` Colin Watson
2009-07-18 18:45 ` Robert Millan
2009-07-18 19:01 ` Vladimir 'phcoder' Serbinenko
2009-07-18 19:17 ` Robert Millan
2009-07-19 10:07 ` Colin Watson
2009-07-22 17:16 ` Robert Millan [this message]
2009-07-22 17:36 ` Pavel Roskin
2009-07-22 17:43 ` Vladimir 'phcoder' Serbinenko
2009-07-22 17:46 ` Pavel Roskin
2009-07-26 12:53 ` Vladimir 'phcoder' Serbinenko
2009-07-18 18:42 ` Robert Millan
2009-07-18 19:00 ` Vladimir 'phcoder' Serbinenko
2009-07-18 19:22 ` Robert Millan
2009-07-18 21:28 ` Vladimir 'phcoder' Serbinenko
2009-07-22 17:22 ` Robert Millan
2009-07-22 17:45 ` Pavel Roskin
2009-07-26 13:54 ` Vladimir 'phcoder' Serbinenko
2009-07-28 17:33 ` Robert Millan
2009-07-28 21:42 ` Vladimir 'phcoder' Serbinenko
2009-07-31 15:43 ` Robert Millan
2009-07-19 10:02 ` Colin Watson
2009-07-22 17:24 ` Robert Millan
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=20090722171612.GC8706@thorin \
--to=rmh@aybabtu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.