From: phcoder <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Multiple partition maps
Date: Thu, 04 Sep 2008 23:54:43 +0200 [thread overview]
Message-ID: <48C05923.3060001@gmail.com> (raw)
In-Reply-To: <20080904194015.GF9133@thorin>
BTW GPT module checks the protective MBR. In some cases when legay OS
modified the MBR it's no longer "protective MBR". And in theese cases
GRUB will refuse to boot. Isn't the magic number check enough?
Vladimir 'phcoder' Serbinenko
Robert Millan wrote:
> On Wed, Sep 03, 2008 at 08:08:50PM +0200, phcoder wrote:
>> Hello. I was looking at the grub code and seen that if a disk has
>> multiple partition tables (e.g. macintel with bootcamp) then only first
>> one will be detected. In some cases it can lead to unreachable
>> partitions if for some reason partition is present only in one table.
>> Does anyone has an idea how theese cases may be treated compactly and
>> efficiently?
>
> Strictly speaking, GPT+MSDOS hybrid tables are a violation of the GPT
> specification. It's not clear what would be the "correct" way of handling
> them.
>
> Since we're not a legacy program, I suppose the sane thing to do would be
> to abort MSDOS probing if a protective DOS partition (0xee) is found, and
> then only GPT will be used.
>
> Isn't this what GRUB does already? I thought it would be...
>
next prev parent reply other threads:[~2008-09-04 21:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-03 18:08 Multiple partition maps phcoder
2008-09-04 19:40 ` Robert Millan
2008-09-04 21:49 ` phcoder
2008-09-05 10:08 ` Robert Millan
2008-09-04 21:54 ` phcoder [this message]
2008-09-08 13:38 ` Robert Millan
2008-09-08 18:27 ` phcoder
2008-09-08 18:31 ` Robert Millan
2008-09-09 0:08 ` phcoder
2008-09-09 0:47 ` [PATCH] " phcoder
2008-09-09 12:37 ` Robert Millan
2008-09-09 13:16 ` phcoder
2008-09-09 15:01 ` 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=48C05923.3060001@gmail.com \
--to=phcoder@gmail.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.