public inbox for util-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: Karel Zak <kzak@redhat.com>
To: Craig <util-linux_contact@magister.com.au>
Cc: util-linux@vger.kernel.org
Subject: Re: ***Urgent***!  Fdisk: GPT support utterly breaks hybrid MBR; *must* have disable option! :(
Date: Fri, 11 Oct 2013 11:04:42 +0200	[thread overview]
Message-ID: <20131011090442.GE14457@x2.net.home> (raw)
In-Reply-To: <alpine.LFD.2.02.1310111435300.6990@trabz.zntvfgre.pbz.nh>

On Fri, Oct 11, 2013 at 02:45:57PM +1100, Craig wrote:
> On Thu, 10 Oct 2013, Karel Zak <kzak@redhat.com> wrote:
> 
> >Note that in v2.24 the GPT code in fdisk does not allow to write hybrid
> >GPT, the support is read-only.
> 
> Hmm; not good for the long term.  Although a hack and potentially disastrous

 It's temporary solution. 
 
 The long term goal is to support *manual* protective/hybrid MBR
 modification. 
 
 It means that user will be able in expert mode switch to MBR, modify and 
 write MBR to the device and then switch back to GPT. The GPT driver will 
 only print warning, but no overwrite the manually modified MBR.

> if not handled carefully, hybrid MBR really is necessary under certain
> conditions.  Perhaps support should be read-only by default, with a means to
> switch to write, and dire warnings that one is likely severely to break
> things if one isn't careful?  Although it could be argued that those likely
> to be playing with fdisk (rather e.g. than Partid) might be expected to know
> what they're doing. :D To be honest, I'd like to see a means completely to
> separate GPT/MBR changes, so if necessary one could do absolutely anything
> to either without affecting the other.  If somebody is playing around with
> both, then really they should expect to understand what will happen if
> they're careless.

 Yep. I don't want any "smart" solution there. All will be controlled
 by users. 
 
 (Well, in the default mode for non-expert users with standard PMBR we will 
  generate the MBR as expected by UEFI specification of course.)

    Karel

-- 
 Karel Zak  <kzak@redhat.com>
 http://karelzak.blogspot.com

  reply	other threads:[~2013-10-11  9:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-09 11:23 ***Urgent***! Fdisk: GPT support utterly breaks hybrid MBR; *must* have disable option! :( Craig
2013-10-09 14:16 ` Karel Zak
2013-10-10  0:39   ` Craig
2013-10-10 11:10     ` Karel Zak
2013-10-11  3:45       ` Craig
2013-10-11  9:04         ` Karel Zak [this message]
2013-10-11 21:34           ` Craig
2013-11-24 18:18           ` H. Peter Anvin

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=20131011090442.GE14457@x2.net.home \
    --to=kzak@redhat.com \
    --cc=util-linux@vger.kernel.org \
    --cc=util-linux_contact@magister.com.au \
    /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