All of lore.kernel.org
 help / color / mirror / Atom feed
From: Drake Wilson <drake@dasyatidae.net>
To: Phillip Susi <psusi@ubuntu.com>
Cc: util-linux@vger.kernel.org
Subject: Re: Bug#770211: LUKS partition types, redux
Date: Sun, 23 Nov 2014 22:45:24 -0600	[thread overview]
Message-ID: <5472B7E4.4040601@dasyatidae.net> (raw)
In-Reply-To: <546E1A16.6050102@ubuntu.com>

Phillip Susi wrote:
[originally re Dale's question]
> Linux doesn't pay any attention to partition type codes anyhow and
> just uses blkid to identify the contents.

So---entirely aside from the _other_ subthread about types _inside_ LUKS---do
you still intend to provide this as a reason for not adding GPT/MBR LUKS
types to fdisk, even in light of the destructive interaction I mentioned in
my first post?  I'm worried that my having said anything else while replying
to Dale may have been a mistake and given the impression that "no types inside
LUKS" answers my original concern, which it doesn't.

As I mentioned, GPT and MBR have significant interop characteristics with
other tools, so I'm not convinced by the "Linux only uses blkid" there.  If
that's what you're truly going with after having seen the practical results,
I won't argue further, but I'd like to know.

   ---> Drake Wilson

  reply	other threads:[~2014-11-24  4:45 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-19 20:59 LUKS partition types, redux Drake Wilson
2014-11-19 22:24 ` Dale R. Worley
2014-11-19 22:37   ` Drake Wilson
2014-11-20 21:33     ` Dale R. Worley
2014-11-21  7:47       ` Milan Broz
2014-11-21  7:54         ` LUKS partition types, redux (wandering into the weeds) Drake Wilson
2014-11-20 16:43   ` Bug#770211: LUKS partition types, redux Phillip Susi
2014-11-24  4:45     ` Drake Wilson [this message]
2014-11-24 14:33       ` Phillip Susi
2014-11-24 14:37         ` Drake Wilson
2014-11-24 14:45           ` Phillip Susi
2014-11-24 14:48           ` Drake Wilson
2014-11-24 14:58             ` Phillip Susi
2014-11-24 15:04               ` Drake Wilson
2014-11-24 15:09                 ` Phillip Susi
2014-11-24 16:10               ` Karel Zak
2014-11-24 16:27                 ` Phillip Susi
2014-11-25 15:18                 ` Dale R. Worley
2014-11-24 11:37 ` Karel Zak
2014-11-24 12:09   ` Drake Wilson
2014-11-24 14:42   ` Phillip Susi
2014-11-24 15:46     ` Karel Zak
2014-11-24 19:56       ` Bruce Dubbs
2014-11-25 11:26         ` Karel Zak
2014-11-25 15:36           ` Bruce Dubbs
2014-11-25 15:20       ` Dale R. Worley
2014-11-24 15:48     ` Dale R. Worley

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=5472B7E4.4040601@dasyatidae.net \
    --to=drake@dasyatidae.net \
    --cc=psusi@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 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.