From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gary_Lerhaupt@Dell.com Date: Mon, 04 Nov 2002 16:38:58 +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 Are these physically separate USB storage devices made by the same manufacturer? Or is this device more like a USB card reader and you are having problems differentiating between the cards that you put into the reader? I have a feeling its the first case, which is unfortunate because with a bad ID like "1f00" for both, devlabel won't work for you. Or, at least it would work for you if you only plugged in one at a time. If you do go with the one-at-a-time approach, then you could create a symlink name to be shared by both like /dev/neodio_storage and then go about automounting with /etc/fstab, etc. However, this won't work for both at the same time (as you've seen). I'm interested in the usb-serial idea, though. Where are these kept? Even if they aren't implemented on many devices, I'd still like to add any possible identifier to make devlabel work in more scenarios. You also mention a volume label, but with USB storage devices, this isn't likely. Well, at least not on my smart card reader. -Gary -----Original Message----- From: Michael Hamilton [mailto:michael@actrix.gen.nz] Sent: Saturday, November 02, 2002 5:33 PM To: Gary_Lerhaupt@exchange.dell.com; david-b@pacbell.net Cc: Linux-hotplug-devel@lists.sourceforge.net Subject: Re: usb-mount (hotplug + desktop hooks) Hi Gary, 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 I was originally going to used the usb-serial as an id, but this isn't always implemented. And even when it is, the usb-serial may not remain constant for the same device. For example my devices adds the current bus-id to the serial, so it differs every time I plug the device in. So I've moved away from id's or serials. However, I could create generic fstab entries like generic-usb-1, generic-usb-2 - but I can't see any advantage. I guess these devices are similar to floppies, they are generic, if they have any ID it will be in the form of a volume label. In case this needs some context - this is about a solution I'm using to pop usb-devices onto the KDE desktop - you can see the details at: http://users.actrix.co.nz/michael/usbmount.html Michael On Tue, 29 Oct 2002 10:52, Gary_Lerhaupt@Dell.com wrote: > I am especially intrigued by the idea of desktop hooks for when a usb event > (or any hotplug storage event) occurs. I think this could be used in > conjunction with devlabel rather nicely. His original reason for not > touching /etc/fstab is because of the changing /dev/sd names. Devlabel > takes care of this and might also now mitigate his fears for including the > symlink reference in /etc/fstab. > > From there, his scripts could be used to create the desktop hooks. So, > basically, in your agent script you have: > ... > [ -x /usr/sbin/devlabel ] && /sbin/devlabel restart > [ -x usb-mount ] && usb-mount > ... > > Michael, if you're looking for devlabel, it can be found at: > http://domsch.com/linux/devlabel > > Gary Lerhaupt > Linux Development > Dell Computer Corporation ------------------------------------------------------- This SF.net email is sponsored by: ApacheCon, November 18-21 in Las Vegas (supported by COMDEX), the only Apache event to be fully supported by the ASF. http://www.apachecon.com _______________________________________________ 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