util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Cordes <peter@cordes.ca>
To: Karel Zak <kzak@redhat.com>
Cc: Bruce Dubbs <bruce.dubbs@gmail.com>,
	Util-Linux <util-linux@vger.kernel.org>
Subject: Re: fdisk request for functionality (or info)
Date: Wed, 04 Oct 2017 05:59:26 -0300	[thread overview]
Message-ID: <20171004085926.GI18363@cordes.ca> (raw)
In-Reply-To: <20171004082728.if274peupxjljbxd@ws.net.home>

On Wed, Oct 04, 2017 at 10:27:28AM +0200, Karel Zak wrote:
> The tricky thing is that fdisks by default see GPT partition, so you
> have to force the tools to ignore GPT and use PMBR.

 Would it be possible to add a more user-friendly way to present this
to the user?

Maybe a special command to toggle the PMBR bootable flag while looking
at the GPT?  That would make the complexity / existence of the PMBR more
discoverable for users, because it would show up in the built-in help
command output while looking at the GPT.  Toggling bootable is just
about the only useful thing you can do with the PMBR on a GPT disk,
and by far the most common, so "hiding" that functionality / status when
looking at the bootability of GPT isn't ideal.

>  3) use sfdisk:
> 
>       sfdisk --label-nested dos --activate /dev/sda 1

That's pretty non-obvious.  I don't think many people would come up
with that on their own if they aren't partitioning / sfdisk experts.
Of course it makes a good recipe, so hopefully people will find it
with google.

-- 
#define X(x,y) x##y
Peter Cordes ;  e-mail: X(peter@cor , des.ca)

"The gods confound the man who first found out how to distinguish the hours!
 Confound him, too, who in this place set up a sundial, to cut and hack
 my day so wretchedly into small pieces!" -- Plautus, 200 BC

  reply	other threads:[~2017-10-04  9:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-03 16:57 fdisk request for functionality (or info) Bruce Dubbs
2017-10-04  8:27 ` Karel Zak
2017-10-04  8:59   ` Peter Cordes [this message]
2017-10-04  9:47     ` Karel Zak
2017-11-02 12:52       ` Karel Zak
2017-10-04 14:41   ` Bruce Dubbs
2017-10-05 10:59     ` Karel Zak
2017-10-05 16:04       ` Bruce Dubbs

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=20171004085926.GI18363@cordes.ca \
    --to=peter@cordes.ca \
    --cc=bruce.dubbs@gmail.com \
    --cc=kzak@redhat.com \
    --cc=util-linux@vger.kernel.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).