On Thu, 2009-10-15 at 14:44 +0200, Michael Biebl wrote: > Bastian Blank wrote: > > On Tue, Oct 13, 2009 at 05:45:27PM +0200, Michael Biebl wrote: > >> What we can not remove currently, is the call to devkit-disks-dm-export, > >> as it makes additional information available like (DKM_)DM_TARGET_TYPES, > >> which is used inside the dk-disks code. > > > > Please explain which highlevel information you need. > > > > DM_TARGET_TYPES is only used to find the string "crypt" in it and I > > already explained several times that DM_UUID==CRYPT-* is a quite better > > indicator, completely functional in the near future with cryptsetup 1.1. > > Finally some useful information, thanks. > > Attached is a patch which makes use of DM_UUID making it possible to > completely > remove devkit-disks-dm-export, and it seems to work nicely. > > 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. > If not, since what version of cryptsetup/dmsetup is this naming interface > stable?
Yeah, I'd like to know exactly how much of this can be expected to be in other distros. FWIW, I've been telling the LVM/device-mapper guys for a long time to include udev rules etc. in the stock upstream release. I know they are planning to do that but I'm not sure it's there yet. If there is, please point me to it. Anyway, that's the reason why I have my own prober, udev rules and name-spaced properties. This will have to stay in the upstream distribution of DKD until there's an upstream release of LVM/device-mapper with what I need. Thanks, David -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
