From: Oliver Neukum <oliver@neukum.name>
To: James Bottomley <James.Bottomley@steeleye.com>,
David Brownell <david-b@pacbell.net>
Cc: Andries.Brouwer@cwi.nl, garloff@suse.de,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
sancho@dauskardt.de, linux-usb-devel@lists.sourceforge.net,
linux1394-devel@lists.sourceforge.net, dougg@torque.net
Subject: Re: [linux-usb-devel] Re: /proc/scsi/map
Date: Sun, 16 Jun 2002 22:54:42 +0200 [thread overview]
Message-ID: <200206162254.42323.oliver@neukum.name> (raw)
In-Reply-To: <200206161725.g5GHP6S23020@localhost.localdomain>
Am Sonntag, 16. Juni 2002 19:25 schrieb James Bottomley:
> Since we already have a huge long list of different ways to identify
> different devices, I don't think coding any one or even a set of such
> methods into the kernel would satisfy everyone.
>
> What about a different approach:
>
> We already (nearly) have the scsimon patches to do hot plug events on
> SCSI devices incorporated. Any identification could be done from the
> scsi device hotplug script (i.e. if you see it's USB, get the GID, if
> it's enterprise storage get the WWN, try the filesystem UUID etc). Then
> all the hotplug script does is plug this device into some type of volume
> idenfication scheme like /dev/volume/<name>.
How would you find out what a device is ?
If the kernel has to supply the information anyway, you could
just as well pass all information to the script or devfs.
Regards
Oliver
next prev parent reply other threads:[~2002-06-16 20:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3D0CC56D.9050805@pacbell.net>
2002-06-16 17:25 ` [linux-usb-devel] Re: /proc/scsi/map James Bottomley
2002-06-16 20:54 ` Oliver Neukum [this message]
2002-06-16 22:02 ` James Bottomley
2002-06-16 22:38 ` Oliver Neukum
2002-06-16 23:14 ` James Bottomley
2002-06-17 5:19 ` Oliver Neukum
2002-06-17 14:54 ` James Bottomley
2002-06-17 16:09 ` Patrick Mansfield
2002-06-17 16:42 ` James Bottomley
2002-06-17 19:07 ` Patrick Mansfield
2002-06-17 20:25 ` James Bottomley
2002-06-17 16:53 ` David Brownell
2002-06-17 17:15 ` David Brownell
[not found] <UTC200206152154.g5FLsCI23053.aeb@smtp.cwi.nl>
2002-06-16 17:05 ` 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=200206162254.42323.oliver@neukum.name \
--to=oliver@neukum.name \
--cc=Andries.Brouwer@cwi.nl \
--cc=James.Bottomley@steeleye.com \
--cc=david-b@pacbell.net \
--cc=dougg@torque.net \
--cc=garloff@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=sancho@dauskardt.de \
/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