From: Greg KH <greg@kroah.com>
To: "Jonathan A. George" <JAGeorge@greshamstorage.com>,
linux-kernel@vger.kernel.org
Cc: viro@parcelfarce.linux.theplanet.co.uk
Subject: Re: Linux 2.6 udev capability question
Date: Tue, 7 Oct 2003 12:05:31 -0700 [thread overview]
Message-ID: <20031007190531.GM1956@kroah.com> (raw)
In-Reply-To: <3F830C49.5070103@greshamstorage.com>
On Tue, Oct 07, 2003 at 01:56:09PM -0500, Jonathan A. George wrote:
> Greg & Al,
>
> Will the udev model somehow support the ability to associate a device
> node with a specific device?
>
> For example in a Fibre Channel, SCSI, iSCSI (SAN) date network
> environment it would be nice to associate a specific device driver
> handle per (WorldWideName and/or Type+Vendor+Model+Serial#).
>
> It would also be nice to be able to associate via the LUN target path.
>
> Obviously the same basic problem space applies to USB devices, and I
> have admittedly not reviewed the specs for sysfs and udev in 2.6. If
> the answer to all of these questions is Yes+RTFM that would make me very
> happy. Otherwise I would be interested in knowing whether or not it is
> even possible in the udev model, and if it is what would be the
> recommended approach to implementation.
Yes, RTFM :)
> P.S. Feel free to forward your response to LKML since there are no doubt
> others with the same question in mind.
Will do. Why did you not ask this there in the first place? Sending
email directly to developers isn't the nicest thing to do:
http://www.arm.linux.org.uk/news/?newsitem=11
thanks,
greg k-h
next parent reply other threads:[~2003-10-07 19:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3F830C49.5070103@greshamstorage.com>
2003-10-07 19:05 ` Greg KH [this message]
[not found] ` <3F831AAB.9040000@greshamstorage.com>
2003-10-07 20:24 ` Linux 2.6 udev capability question Greg KH
2003-10-07 20:34 ` Acknowledgement Jonathan A. George
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=20031007190531.GM1956@kroah.com \
--to=greg@kroah.com \
--cc=JAGeorge@greshamstorage.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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