DM & udev
Hello,
what's the rationale behind the enum-style naming of DM in /sys/block ? a nasty side effect is that /udev names are not the DM name like devfs did (/dev/mapper/vg01-vol01), but those dm-0, dm-1, ...
One might insert yet another rule in udev to translate, but I wondered if there was a real reason for the dm-* names.
Either way, I can get rid of the mknod code in the multipath tool, and let udev react to /sys/blocl/$any-dm-name spawning. Greg if you confirm that assertion, I'll submit this patch for the next udev release.
regards,
cvaroqui
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
Quoted 6 lines · christophe varoqui
Hello,
what's the rationale behind the enum-style naming of DM in
/sys/block? a nasty side effect is that /udev names are not the DM name like devfs did (/dev/mapper/vg01-vol01), but those dm-0, dm-1, ...
Quoted 6 lines
One might insert yet another rule in udev to translate, but I wondered if there was a real reason for the dm-* names.
Either way, I can get rid of the mknod code in the multipath tool, and let udev react to
/sys/blocl/$any-dm-namespawning. Greg if you confirm that assertion, I'll submit this patch for the next udev release.
udev should be able to handle dm-* names just fine as long as there is a 'dev' file in the directory for them (which I'm pretty sure there is...)
thanks,
greg k-h
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
Quoted 10 lines · Greg KH
Quoted 9 lines · christophe varoqui
Hello,
what's the rationale behind the enum-style naming of DM in
/sys/block? a nasty side effect is that /udev names are not the DM name like devfs did (/dev/mapper/vg01-vol01), but those dm-0, dm-1, ...One might insert yet another rule in udev to translate, but I wondered if there was a real reason for the dm-* names.
Quoted 6 lines
Quoted 3 lines
Either way, I can get rid of the mknod code in the multipath tool, and let udev react to
/sys/blocl/$any-dm-namespawning. Greg if you confirm that assertion, I'll submit this patch for the next udev release.udev should be able to handle dm-* names just fine as long as there is a 'dev' file in the directory for them (which I'm pretty sure there is...)
The dm-* names are due to the separation between the DM core driver and the ioctl interface. Only the ioctl interface knows the name of the device given by the user. But only the core driver has access to the gendisk entry (and hence the sysfs name). So the core assigns the gendisk a simple name based on the minor number of the device.
And yes, there's a "dev" file in the dm-* directories, just as with all other subdirs in /sys/block/.
Signature · 14 lines
Kevin Corry [email protected] ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net [email protected] https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel