All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: ilf <ilf@zeromail.org>, dm-crypt@saout.de
Subject: Re: [dm-crypt] persistent naming: add ID in addition to UUID
Date: Mon, 27 Jul 2015 21:49:43 +0200	[thread overview]
Message-ID: <55B68B57.5090505@gmail.com> (raw)
In-Reply-To: <20150727192634.GG16353@zeromail.org>

On 07/27/2015 09:26 PM, ilf wrote:
> Sven Eschenberg:
>> Since you want to use crypttab anyway, is there any particular reason not 
>> to use /dev/disk/by-id/<identifier>?
> 
> You are comlpetely right, that works and I should probably use that.
> 
>> As UUID=<uuid> needs proper symlinks anyway, it is rather a handy 
>> shorthand at the commandline.
> 
> Well, the man-page for crypttab(5) in Debian and Derivatives sais, "the 
> UUID is supported as well, using UUID=<luks_uuid>". So adding an ID= 
> option would make this more consistent.

Actually I added UUID=<..> to cryptsetup to mainly easily implement
scripts doing the similar action as fstab/crypttab UUID= mount.
(fstab allows LABEL and UUID but not ID; also LUKS has no label)

Not sure if adding ID is worth to do this, it is really just
shortcut to udev symlink. Note that UUID is read from header and has
always the same format.

ID can be crazy combination of characters, sometimes even dynamic
(not everything is hw-serial based, see DM devices for example).
(I remember several bugs for multipath/SCSI devices where hw-based ID contains
binary data and must be properly escaped for symlink name...)

Milan

  reply	other threads:[~2015-07-27 19:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-26 17:02 [dm-crypt] persistent naming: add ID in addition to UUID ilf
2015-07-26 18:25 ` Sven Eschenberg
2015-07-27 19:26   ` ilf
2015-07-27 19:49     ` Milan Broz [this message]
2015-07-27 21:53       ` Sven Eschenberg
2015-07-27 21:47     ` Sven Eschenberg

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=55B68B57.5090505@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=dm-crypt@saout.de \
    --cc=ilf@zeromail.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.