From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Brownell Date: Thu, 21 Nov 2002 20:30:57 +0000 Subject: Re: usb-mount (hotplug + desktop hooks) Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org Michael Hamilton wrote: > > I tried two of the same device, devlabel's scsi_unique_id utility returns > the same ID for both: > > model: Neodio TNeodio/Leadtek W > page83: No page83 information found. > page80: 1f00 Yeah, there are a whole bunch more IDs that ought to be available when making such decisions. USB serial numbers for one, and also "physical" IDs that don't change until you physically re-cable the device or subsystem. (And there are other labels ...) 2.5 has a kind of physical device ID available: the sysfs path of the device. (It's less stable than it should be ... but that can be improved.) Bus or class level hotplug agents can use /sys/$DEVPATH to see more info about the devices ... which I'll suspect doesn't cover much of the data that'd be important to user mode tools like devlabel or usb-mount. I'm not sure what's up with "disk hotplug" (wasn't there a disk "class" a while back?) or how it might relate to the /sys/block stuff that I see lately. Would someone working in that area have any insights to share -- Pat, Greg? :) - Dave ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel