On Mon, Dec 15, 2008 at 07:38:31PM +0100, Kay Sievers wrote: > In fact, it's good that you started shipping these patches, so it > shows how stuff should work. And it hopefully puts some pressure on > the guys who should fix their stuff after all these years. Hint, hint > to someone in the Cc: list. :) Well let's try to summarise how far we got in those discussions: 1) udev able to query device-mapper to determine what the /dev/mapper entry should be called. - udev uses dmsetup. Sorted. 2) udev able to query device-mapper to determine what the link should be called. - udev uses dmsetup, checks for the LVM prefix on the UUID then either splits the name into components (vgname+lvname+layer) itself (remembering to unquote doubled hyphens) or calls out to LVM2 to do that. (There may be some sequencing issues here.) 3) udev able to determine whether a link needs to exist in /dev/<vgname> or not - work on the basis that the requirement is having the LVM uuid prefix and having no 'layer' in the name. (This may change when we support internal stacking better.) 4) lvm2 able to sleep until udev has completed a particular sequence of async operations (without second-guessing udev and looking if the right things have appeared in /dev) - unresolved. Alasdair -- agk@xxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
