RE: Udev support for EDD

>How about "by-firmware-id" to match the kernel sysfs name?
>Or putting the links just in /dev/disk/by-id/* with an edd- prefix?

I don't have any particular preference on what to name the directory;
"by-bios-id", "by-firmware-id", or "by-edd-id" are all fine by me. Ild
rather do that, though, than put the links in /dev/disk/by-id.

> To match the int13_dev8* device to the kernel block device, the 
> "mbr_signature" for the device exposed by EDD must be matched to the 
> disk signature read directly from the device by a user-space program 
> (signature is 4-bytes long starting at offset 0x1B8 on the disk). To 
> ensure that each disk can be matched to the corresponding BIOS disk, 
> each disk should have a unique disk signature. In my current 
> implementation with udev, I pass the kernel device (hd* or sd*) to a 
> bash script which reads its signature and then tries to match it to a 
> corresponding mbr_signature in the int13_dev* directories. If there is

> a unique match, it returns this directory to udev, and returns nothing

> otherwise.
> 
> I have placed a rules file and the script that it calls here:
> http://linux.dell.com/files/edd/udev/, as well as a Python module that

> can be used to read and write the signatures. Please review my 
> approach and let me know how I can improve this for eventual inclusion
with udev.

>The edd_id.sh should not check for a loaded module, otherwise it will