> > For discussion I suggest /proc/ata/devices, a single flat file Ahem. /sys please. And do not just limit it to ATA. > matching a name meaningful to open() with a vendor string and > whatever other info is handy, like serial number and the like. If > people are going to use ATA that allows them to generate their own > tools using familiar methods like awk, sed, grep, perl, python or > whatever. Having that information in an inobvious format will really > slow adoption by triggering the "it's hard to use" or "I need to use > all these new tools" responses. > > And those responses are not limited to newbies, experienced users are aware of > the ratio of learning curve to functionality as well. What would the contents of /ata/devices look like, can you give an example? Jan Engelhardt -- - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
