[ Triming mdadm maintainers from CC. ]
On Thu, Oct 15, 2009 at 02:44:23PM +0200, Michael Biebl wrote:
> Is the DM_UUID=CRYPT-* naming scheme documented somewhere? I'd like to send
> this
> patch upstream and would need to know if it is a Debian specific feature.
I forgot to cite the information I got from the cryptsetup maintainer.
The current state is documented in #548988.
> If not, since what version of cryptsetup/dmsetup is this naming interface
> stable?
1.0.7 have CRYPT-$UUID for luks devices. 1.1, which is supposed to be
released shortly, will have CRYPT-PLAIN-* and CRYPT-LUKS-*.
I'm still not fully aware what you are really trying to detect. The code
is so full of comments in the relevant section, this makes it not easier
to give comments.
I see three possibilities:
- Destinguish between uncrypted and crypted devices (the luks
description would be wrong then).
- Destinguish between plain crypted and luks crypted devices.
- Destinguish between luks crypted and anything else.
The last looks like the correct one according to the names and checks.
The correct check for this one would be:
CRYPT-[0-9a-f]* || CRYPT-LUKS-*
The check for temporary-cryptsetup-* can go then. This will catch
anything from cryptsetup 1.0.7 up.
It makes no sense to comment on the actual check if I don't know what it
should do.
Bastian
--
There is an order of things in this universe.
-- Apollo, "Who Mourns for Adonais?" stardate 3468.1
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
