From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gary_Lerhaupt@Dell.com Date: Thu, 07 Nov 2002 16:05:54 +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 Here is my solution. Tell me what you think. I'll add a --usb-guid option to the devlabel add command. When you try to do an add with --usb-guid, it will first grab the SCSI ID and then grab the USB GUID. It will then prompt you to remove your USB device. It will then prompt you to reattach your USB device. At this point it will confirm that the ID it received before is the same ID it is getting now. If both of these match, the add will proceed and from then on it will reference the USB GUID to confirm consistency. Unfortunately, this does little for you as your GUIDs are non-unique. In your scenario, the --usb-guid add would fail and it wouldn't allow you to use the GUID as part of the ID of the device. However, for things like my card-reader and properly spec'd USB devices, this would alleviate dependence on the 1F00 identifier. Hey, maybe someone might even take the initiative to compile a list of USB devices which have true consistent GUIDs. What do you think? -----Original Message----- From: Michael Hamilton [mailto:michael@actrix.gen.nz] Sent: Wednesday, November 06, 2002 11:03 PM To: Gary_Lerhaupt@exchange.dell.com; a_ajay_sr@yahoo.com Cc: Linux-hotplug-devel@lists.sourceforge.net Subject: Re: usb-mount (hotplug + desktop hooks) I've already investigated this path. Here's a summary... I have two identical devices - lets call them A and B to save any confusion. 1) Plug in device A: viking2:~ % cat /proc/scsi/usb-storage-0/0 Host scsi0: usb-storage Vendor: Neodio Technologies Corp. Product: Neodio USB Storage Device Serial Number: 0AEC501000001A002 Protocol: Transparent SCSI Transport: Bulk GUID: 0aec5010aec501000001a002 Attached: Yes 2) Unplug device A and plug it in again - note the serial and GUID are based on the same attributes - the vendor, product and bus location. viking2:~ % cat /proc/scsi/usb-storage-0/0 Host scsi0: usb-storage Vendor: Neodio Technologies Corp. Product: Neodio USB Storage Device Serial Number: 0AEC501000001A003 Protocol: Transparent SCSI Transport: Bulk GUID: 0aec5010aec501000001a003 Attached: Yes 3) Plug in device B - note that it has the Serial and GUID we saw in step (1) above. viking2:~ % cat /proc/scsi/usb-storage-1/0 Host scsi0: usb-storage Vendor: Neodio Technologies Corp. Product: Neodio USB Storage Device Serial Number: 0AEC501000001A002 Protocol: Transparent SCSI Transport: Bulk GUID: 0aec5010aec501000001a002 Attached: Yes 4) Unplug device B and plug it in again- note it now has the same serial and GUID as device A which is still plugged in. viking2:~ % cat /proc/scsi/usb-storage-1/0 Host scsi0: usb-storage Vendor: Neodio Technologies Corp. Product: Neodio USB Storage Device Serial Number: 0AEC501000001A003 Protocol: Transparent SCSI Transport: Bulk GUID: 0aec5010aec501000001a003 Attached: Yes viking2:~ % cat /proc/scsi/usb-storage-0/0 Host scsi0: usb-storage Vendor: Neodio Technologies Corp. Product: Neodio USB Storage Device Serial Number: 0AEC501000001A003 Protocol: Transparent SCSI Transport: Bulk GUID: 0aec5010aec501000001a003 Attached: Yes Not very nice. I guess the scsi device id could be added to the serial or GUID to provide a unique identifier that will last as long as the device is plugged in. Michael ------------------------------------------------------- This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en _______________________________________________ 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