Grub Development Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Multiple partition maps
Date: Fri, 5 Sep 2008 12:08:51 +0200	[thread overview]
Message-ID: <20080905100851.GD5220@thorin> (raw)
In-Reply-To: <48C057E1.6050401@gmail.com>

On Thu, Sep 04, 2008 at 11:49:21PM +0200, phcoder wrote:
> 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.
> 
> We're not a legacy application but some OS and partition tools are and
> we have to work with them. I think just some maintenance tools included
> in GRUB should be enough. I'll write them soon. (perhaps even tomorrow)

I don't understand.  Which kind of maintenance do you mean?  GRUB isn't
designed to modify partition maps, only read them.  Perhaps what you want
is more related to Parted?

> > Isn't this what GRUB does already?  I thought it would be...
> > 
> It does. But I don't know if there are other cases similar to this one.

There's also grub-setup.  On an hybrid map the only option is to follow the
GPT install path and search for a BIOS boot partition (or otherwise use
blocklists).  Does it DTRT already?

I don't know of any other similar situation.

-- 
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."



  reply	other threads:[~2008-09-05 10:10 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 [this message]
2008-09-04 21:54   ` phcoder
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=20080905100851.GD5220@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox