From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: USB/desktop integration - how to guess /dev/sd* when hotplugging?
Date: Fri, 13 Feb 2004 01:31:16 +0000 [thread overview]
Message-ID: <20040213013116.GF5351@kroah.com> (raw)
In-Reply-To: <200402130844.30279.michael@actrix.gen.nz>
On Fri, Feb 13, 2004 at 08:44:30AM +1300, Michael Hamilton wrote:
> How do I systematically determine /dev/sd[abc] when hotplugging?
> Is sg_map from sg3_utils the best/only way? In more detail...
Looked at devlabel?
> 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*?
Why not just catch either the block hotplug events, or the scsi hotplug
events? And why would you ever want to map usb-storage devices to their
usbfs entry?
> I was hoping there was a easy way to use /proc or /sys, to
> get this info.
Look at /sys/block/{block_device}/device
That's the symlink I think you want, right?
thanks,
greg k-h
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-02-13 1:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 19:44 USB/desktop integration - how to guess /dev/sd* when hotplugging? Michael Hamilton
2004-02-12 21:39 ` Marco d'Itri
2004-02-13 1:31 ` Greg KH [this message]
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=20040213013116.GF5351@kroah.com \
--to=greg@kroah.com \
--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).