From: worley@alum.mit.edu (Dale R. Worley)
To: Scott Moser <smoser@ubuntu.com>
Cc: util-linux@vger.kernel.org
Subject: Re: GPT writing of unknown partition uuids
Date: Tue, 14 Jul 2015 20:37:38 -0400 [thread overview]
Message-ID: <87mvyymf1p.fsf@hobgoblin.ariadne.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1507141610310.21273@brickies> (smoser@ubuntu.com)
Scott Moser <smoser@ubuntu.com> writes:
> If sfdisk does not know the uuid provided, it silently falls back to
> 0FC63DAF-8483-4772-8E79-3D69D8477DE4 (Linux filesystem).
>
> It seems like if the user provided you with a GUID, sfdisk should trust
> them, or at very least exit failure if it refuses to use the provided
> GUID.
Ugh, you're right! Silent disobedience is pernicious.
Dale
next prev parent reply other threads:[~2015-07-15 0:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 20:16 GPT writing of unknown partition uuids Scott Moser
2015-07-15 0:37 ` Dale R. Worley [this message]
2015-07-15 13:28 ` Scott Moser
2015-07-15 13:42 ` Karel Zak
2015-07-15 14:56 ` Scott Moser
2015-07-15 15:02 ` Karel Zak
2015-07-15 15:09 ` Vadim Kochan
2015-07-15 15:12 ` Vadim Kochan
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=87mvyymf1p.fsf@hobgoblin.ariadne.com \
--to=worley@alum.mit.edu \
--cc=smoser@ubuntu.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