From: Andreas Jellinghaus <aj@leogic.com>
To: linux-hotplug@vger.kernel.org
Subject: /dev/usbdevX.X?
Date: Thu, 08 Dec 2005 20:45:00 +0000 [thread overview]
Message-ID: <dna64b$cui$1@sea.gmane.org> (raw)
Hi,
oh, shiny new device files. but why? /proc/bus/usb/00X/00Y
works fine for me. why the changes? will usbfs alias /proc/bus/usb
be obsoleted?
also are there any differences between those two files?
or are they exchangeable?
also what about the hotplug interface and udev?
I hope I can still count on $DEVICE being the
/proc/bus/usb/ device when my hotplug script
is being called?
and I hope libusb will continue to have filename
and dirname as those /proc/bus/usb/<dirname>/<filename>
so I can use it to reconstruct the path, and open the
right file. (I got a real strange bug report by a debian
user with dirname "3" instead of "003" and filename "5"
instead of "005", but he libusb code looks fine).
In short: I'm confused by the change / new device files.
please help.
Regards, Andreas
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&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 reply other threads:[~2005-12-08 20:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 20:45 Andreas Jellinghaus [this message]
2005-12-08 21:06 ` /dev/usbdevX.X? Kay Sievers
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='dna64b$cui$1@sea.gmane.org' \
--to=aj@leogic.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).