On Thu, Jun 05, 2008 at 12:27:54AM -0600, Andreas Dilger wrote: > To be honest, however, having the information exported only via sysfs > is a bit ugly IMHO. I've had all sorts of grief with settings there > because there isn't always a match between the device that is being > specified by the user and what appears in sysfs (e.g. /dev/disk/by-id/foo > doesn't match /sys/block/sda) and hoops have to be jumped through to > find this mapping, before parsing a text value in C. readlink() is too hard? $ readlink /dev/disk/by-id/ata-FUJITSU_MHV2080AH_NT61T6325UGM ../../hda > Having an ioctl() that can be called on the block device (getting > the right device regardless of its name) seems a lot more useful to > applications in my experience, unless you are using a script. It's certainly easier. -- Intel are signing my paycheques ... these opinions are still mine "Bill, look, we understand that you're interested in selling us this operating system, but compare it to ours. We can't possibly take such a retrograde step." -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
