linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Hamilton <michael@actrix.gen.nz>
To: linux-hotplug@vger.kernel.org
Subject: Re: usb-mount (hotplug + desktop hooks)
Date: Sat, 02 Nov 2002 23:32:38 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-103628126318461@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-103558971618973@msgid-missing>

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: 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

  parent reply	other threads:[~2002-11-02 23:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-25 23:46 usb-mount (hotplug + desktop hooks) David Brownell
2002-10-26  9:35 ` Oliver Neukum
2002-10-28 21:52 ` Gary_Lerhaupt
2002-11-02 23:32 ` Michael Hamilton [this message]
2002-11-04 16:38 ` Gary_Lerhaupt
2002-11-05  9:46 ` Michael Hamilton
2002-11-06  4:23 ` Ajay
2002-11-06  9:21 ` Michael Hamilton
2002-11-06 15:53 ` Gary_Lerhaupt
2002-11-07  5:03 ` Michael Hamilton
2002-11-07 16:05 ` Gary_Lerhaupt
2002-11-11  8:11 ` Michael Hamilton
2002-11-11 15:39 ` Gary_Lerhaupt
2002-11-13  8:55 ` Michael Hamilton
2002-11-21 20:30 ` David Brownell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-linux-hotplug-103628126318461@msgid-missing \
    --to=michael@actrix.gen.nz \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).