From: Drake Wilson <drake@dasyatidae.net>
To: Milan Broz <gmazyland@gmail.com>
Cc: util-linux@vger.kernel.org, worley@alum.mit.edu
Subject: Re: LUKS partition types, redux (wandering into the weeds)
Date: Fri, 21 Nov 2014 01:54:00 -0600 [thread overview]
Message-ID: <546EEF98.5010600@dasyatidae.net> (raw)
In-Reply-To: <546EEE1C.102@gmail.com>
Milan Broz wrote:
> If I understand it correctly, you want to duplicate some UUID stored
> in LUKS container payload to LUKS header?
Just to be clear (even though you weren't responding to me), I only said anything
about LUKS extension as an offhand comment in response to Dale. This is not relevant
to my _original_ post, which was about partition type codes as part of GPT and MBR
disklabels for disks that contain LUKS volumes. The latter is the only thing I'm
directly interested in, and I'm not going to participate further in this subthread.
---> Drake Wilson
next prev parent reply other threads:[~2014-11-21 7:54 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 ` Drake Wilson [this message]
2014-11-20 16:43 ` Bug#770211: " Phillip Susi
2014-11-24 4:45 ` Drake Wilson
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=546EEF98.5010600@dasyatidae.net \
--to=drake@dasyatidae.net \
--cc=gmazyland@gmail.com \
--cc=util-linux@vger.kernel.org \
--cc=worley@alum.mit.edu \
/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).