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: USB/desktop integration - how to guess /dev/sd* when hotplugging?
Date: Thu, 12 Feb 2004 19:44:30 +0000	[thread overview]
Message-ID: <200402130844.30279.michael@actrix.gen.nz> (raw)

How do I systematically determine /dev/sd[abc] when hotplugging?
Is sg_map from sg3_utils the best/only way?  In more detail...

I've got some scripts that attempt to integrate hotplug and 
the desktop so that icons for each partition pop onto the 
desktop and change state when usb devices are plugged in,
see http:/users.actrix.co.nz/michael .  My scripts were 
an interim measure - pending a universally accepted 
solution from distro or desktop makers - but my scripts
are still in use after  more than a year. I'm trying 
to tidy them up and add firewire support, plus get them
to work for kernel 2.6.

There doesn't seem to be an easy way to figure out the scsi
/dev/sd* from the hotplug device passed in, for example:
from /proc/bus/usb/004/002 to what /dev/sd*?

I was hoping there was a easy way to use /proc or /sys, to 
get this info.  But I can't see anything there solving the
problem.  I'm thinking of using the sg_map utility from 
sg3_utils.  The only problem with sg_map is that it probes
non-existant devices, and the probes produce a lot of 
dmesg chatter which in turn creates a CPU burst from the
syslogd.  Some log chatter can be eliminated by assigning
dummy devices, but I prefer not to have to do that.

If there isn't a way to do this simply and cleanly, could
I suggest that kernel people consider adding something
to the sysfs under 2.6.   

Thanks,
Michael


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&op=click
_______________________________________________
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

             reply	other threads:[~2004-02-12 19:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-12 19:44 Michael Hamilton [this message]
2004-02-12 21:39 ` USB/desktop integration - how to guess /dev/sd* when hotplugging? Marco d'Itri
2004-02-13  1:31 ` Greg KH
2004-02-13 11:01 ` USB/desktop integration - how to guess /dev/sd* when Michael Hamilton
2004-02-15  2:38 ` USB/desktop integration - how to guess /dev/sd* when hotplugging? Michael Hamilton

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=200402130844.30279.michael@actrix.gen.nz \
    --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).