[prev in list] [next in list] [prev in thread] [next in thread] 

List:       dm-crypt
Subject:    Re: [dm-crypt] persistent naming: add ID in addition to UUID
From:       "Sven Eschenberg" <sven () whgl ! uni-frankfurt ! de>
Date:       2015-07-27 21:53:53
Message-ID: 4af38a65696a2cf71fa03027fbc195d9.squirrel () ssl ! verfeiert ! org
[Download RAW message or body]

On Mon, July 27, 2015 21:49, Milan Broz wrote:
> 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)
>

Sorry to correct you here, but fstab supports all libblkid properties,
which are amongst UUID and LABEL some more (PARTLABEL and PARTUUID for GPT
work quite well ;-) ). And even UUID and LABEL need libblkid support,
otherwise they won't work in fstab.

> Milan
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
>

Regards

-Sven


_______________________________________________
dm-crypt mailing list
dm-crypt@saout.de
http://www.saout.de/mailman/listinfo/dm-crypt
[prev in list] [next in list] [prev in thread] [next in thread]