From: "Guo, Min" <min.guo@intel.com>
To: linux-hotplug@vger.kernel.org
Subject: RE: Question about Hot device Identity
Date: Fri, 27 Jun 2003 02:00:55 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-105668208524722@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-105633765700944@msgid-missing>
So do you mean that I can set my DEVPATH to /sys/block/sr0/?
because there is a dev file in the directory. But I wonder why
the there are no dev file in directory /sys/devices/pci0/0000:00:0f.2/usb1/1-1/1-1:0/host2/2:0:0:0/,
Accoring to Flemming's comments,the sysfs will not create a dev file for USB CDROM,
is that right?
I did set the DEBUG = true, but nothing is outputed.
Thanks
Guo Min
-----Original Message-----
From: Greg KH [mailto:greg@kroah.com]
Sent: Friday, June 27, 2003 1:14 AM
To: linux-hotplug-devel@lists.sourceforge.net
Subject: Re: Question about Hot device Identity
On Wed, Jun 25, 2003 at 09:10:29PM -0700, Kevin P. Fleming wrote:
>
> But, this has nothing to do with whether udev can support your device
> or not and create a node in /dev for it. udev should be able to do
> exactly that, but I don't know whether it currently looks only at
> /sys/class (which I think is the case) or whether it also looks at
> /sys/block.
Yes, udev can handle things in /sys/block.
Actually it doesn't care where things are located in sysfs, it only
looks to see if there is a file called "dev" in the directory passed to
it in DEVPATH. If there is, it will then act apon that device.
Hope this helps in clearing up things.
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
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
-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
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:[~2003-06-27 2:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-23 3:04 Question about Hot device Identity Guo, Min
2003-06-23 3:22 ` Greg KH
2003-06-24 7:01 ` Guo, Min
2003-06-24 16:20 ` Greg KH
2003-06-25 2:24 ` Guo, Min
2003-06-25 2:33 ` Greg KH
2003-06-25 9:05 ` Guo, Min
2003-06-25 14:45 ` Kevin P. Fleming
2003-06-25 17:00 ` Greg KH
2003-06-26 2:24 ` Guo, Min
2003-06-26 4:10 ` Kevin P. Fleming
2003-06-26 7:42 ` Guo, Min
2003-06-26 17:13 ` Greg KH
2003-06-26 19:05 ` Greg KH
2003-06-26 19:08 ` Greg KH
2003-06-27 2:00 ` Guo, Min [this message]
2003-06-27 3:18 ` Greg KH
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-105668208524722@msgid-missing \
--to=min.guo@intel.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).