From: Christoph Anton Mitterer <calestyo@scientia.net>
To: util-linux@vger.kernel.org
Subject: Re: fdisk: add GPT partition types for plain dm-crypt and LUKS
Date: Tue, 28 Jan 2014 22:09:16 +0100 [thread overview]
Message-ID: <1390943356.7021.7.camel@heisenberg.scientia.net> (raw)
In-Reply-To: <52E819BF.4090503@ubuntu.com>
[-- Attachment #1: Type: text/plain, Size: 1049 bytes --]
On Tue, 2014-01-28 at 15:57 -0500, Phillip Susi wrote:
> Why?
Sure... some people (including myself) have pointed out arguments in the
thread over at the dm-crypt mailinglist, like:
- for plain dm-crypt it's a "good" way to make it recognisable
- partitioning tools can use it to hint what a partition contains
- and after all, partition types do exist, whether they make sense and
are used or not... and I think it's better to have some standardised
value which people may set (if they want) even if it's nowhere used,..
instead of having them set something which may actually cause issues
even if only in the future.
> Linux doesn't use partition IDs.
Phew... that's not fully true... not even for the kernel which I think
still contains the code to do MD auto assembly with 0.9 superblocks when
some MBR partition type is set...
And there are probably many tools (fdisk ;-) ) out there which some how
use or at least display the types.
> Also isn't plain dm-crypt
> depreciated?
Why should it be?
Cheers,
Chris.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5165 bytes --]
next prev parent reply other threads:[~2014-01-28 21:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 18:48 fdisk: add GPT partition types for plain dm-crypt and LUKS Christoph Anton Mitterer
2014-01-28 20:57 ` Phillip Susi
2014-01-28 21:09 ` Christoph Anton Mitterer [this message]
2014-01-28 21:28 ` Phillip Susi
2014-01-28 21:41 ` Christoph Anton Mitterer
2014-01-29 0:52 ` Phillip Susi
2014-01-29 1:05 ` Christoph Anton Mitterer
2014-01-28 21:35 ` Davidlohr Bueso
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=1390943356.7021.7.camel@heisenberg.scientia.net \
--to=calestyo@scientia.net \
--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