All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: "Pali Rohár" <pali.rohar@gmail.com>, dm-crypt@saout.de
Cc: Karel Zak <kzak@redhat.com>
Subject: Re: [dm-crypt] LUKS GPT GUID
Date: Sun, 26 Jan 2014 10:24:39 +0100	[thread overview]
Message-ID: <52E4D457.4030304@gmail.com> (raw)
In-Reply-To: <CAHYPw2GGbcR450hLtJ4ppGjP4N0TdN-LezpfXwd5igD-PWYL_Q@mail.gmail.com>

On 01/26/2014 02:40 AM, Pali Rohár wrote:
> Hello,
> 
> according to wikipedia [1] and other sites (e.g. [2]) MBR partition ID
> for LUKS is E8. I tried to find GPT partition GUID for LUKS, but there
> is nothing on wikipedia [3] nor google... So has LUKS already
> preferred/assigned GUID for GPT partition table? There is already GPT
> GUID for linux data, raid, swap, lvm and home partitions (see [3]), so
> I think that LUKS should have GUID too.

Hi,

this is wonderful... who assigned E8 type? I thought LUKS has no assigned
partition type and also I doubt LVM2 type is properly assigned too
(it is probably form the LVM1 age when it was implemented in-kernel directly
and partition type was important to detect it.) But not sure about this.

Anyway, today partition type is ignored (both in LVM and LUKS), so it is really
just for convenience for other applications.
(Anyway, code should always use (lib)blkid to detect what's really on the device,
not trust partition id.)

For GPT GUID, I would like to know how these GUID codes appeared in libfdisk
and how this was standardized for LVM. LUKS should have GUID too then...
(cc to Karel as util-linux/libfdisk maintainer ;-)

If this is really used, both should be documented in LUKS specification.

Thanks,
Milan

> 
> [1] - http://en.wikipedia.org/wiki/Partition_type
> [2] - http://www.win.tue.nl/~aeb/partitions/partition_types-1.html
> [3] - http://en.wikipedia.org/wiki/GUID_Partition_Table

  reply	other threads:[~2014-01-26  9:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-26  1:40 [dm-crypt] LUKS GPT GUID Pali Rohár
2014-01-26  9:24 ` Milan Broz [this message]
2014-01-26 10:17   ` Pali Rohár
2014-01-26 16:02     ` Rod Smith
2014-01-26 15:55   ` Christoph Anton Mitterer
2014-01-27  9:53   ` Karel Zak
2014-01-27 10:05     ` Pali Rohár
2014-01-27 10:40       ` Karel Zak
2014-01-27 10:49         ` Pali Rohár
2014-01-27 11:47         ` Sven Eschenberg
2014-01-27 15:25     ` Christoph Anton Mitterer
2014-01-27 20:41       ` Milan Broz
2014-01-27 21:12         ` Christoph Anton Mitterer
2014-01-28 16:58           ` Milan Broz
2014-01-29 13:47             ` Christoph Anton Mitterer
2014-01-28  0:04         ` Arno Wagner
2014-01-26 13:18 ` Arno Wagner
2014-01-31 20:56 ` Pali Rohár
2014-01-31 21:32   ` Christoph Anton Mitterer

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=52E4D457.4030304@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=dm-crypt@saout.de \
    --cc=kzak@redhat.com \
    --cc=pali.rohar@gmail.com \
    /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.