From: Robert Nichols <rnicholsNOSPAM@comcast.net>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Detached headers, multiple drives and UUIDs
Date: Mon, 10 Apr 2017 20:41:27 -0500 [thread overview]
Message-ID: <ochc81$prs$1@blaine.gmane.org> (raw)
In-Reply-To: <489y4b.oo7r4j.1hge16s-qmf@gmx.com>
On 04/10/2017 04:45 PM, 7heo wrote:
> On Mon Apr 10 23:29:20 2017 GMT+0200, Robert Nichols wrote:
>> On 04/10/2017 03:53 PM, 7heo wrote:
>> The UUID reported by "blkid" and "lsblk -f" is _exactly_ the luksUUID. The UUID reported by "dmsetup info" is the luksUUID prefixed by "CRYPT-LUKS1-" and suffixed by "-{mapper_name}". If you leave the UUID the same, the output from "blkid" and "lsblk -f" will be confusing.
>
> Correct me if I'm wrong, but that could be a problem for some scripts, couldn't it?
Of course that all depends on the script. System scripts typically use UUIDs to identify devices to be opened/mounted, and you've already given up that possibility by detaching the header from the device.
--
Bob Nichols "NOSPAM" is really part of my email address.
Do NOT delete it.
next prev parent reply other threads:[~2017-04-11 1:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 13:07 [dm-crypt] Detached headers, multiple drives and UUIDs 7heo
2017-04-10 13:25 ` Milan Broz
2017-04-10 13:45 ` 7heo
2017-04-10 14:09 ` Ondrej Kozina
2017-04-10 14:33 ` 7heo
2017-04-10 15:16 ` Ondrej Kozina
2017-04-10 15:22 ` Ondrej Kozina
2017-04-10 18:28 ` Robert Nichols
2017-04-10 19:10 ` Milan Broz
2017-04-10 20:53 ` 7heo
2017-04-10 21:29 ` Robert Nichols
2017-04-10 21:45 ` 7heo
2017-04-11 1:41 ` Robert Nichols [this message]
2017-04-11 7:38 ` Michael Kjörling
2017-04-11 4:02 ` Diagon
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='ochc81$prs$1@blaine.gmane.org' \
--to=rnicholsnospam@comcast.net \
--cc=dm-crypt@saout.de \
/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.