From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: /dev/usbdevX.X?
Date: Thu, 08 Dec 2005 21:06:15 +0000 [thread overview]
Message-ID: <20051208210615.GA17109@vrfy.org> (raw)
In-Reply-To: <dna64b$cui$1@sea.gmane.org>
On Thu, Dec 08, 2005 at 09:45:00PM +0100, Andreas Jellinghaus wrote:
> Hi,
>
> oh, shiny new device files. but why? /proc/bus/usb/00X/00Y
> works fine for me. why the changes?
We want ACL support on device nodes.
> will usbfs alias /proc/bus/usb > be obsoleted?
It will stay for a while, no plans for now, but all devfs's are
some sort of deprecated, yes.
> also are there any differences between those two files?
Only the location and the real files can have ACL's and SELinux labels.
> or are they exchangeable?
Yes.
> 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?
No, don't depend on it.
> 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.
Sure.
> (I got a real strange bug report by a debian
> user with dirname "3" instead of "003" and filename "5"
> instead of "005",
That creates the same names:
SUBSYSTEM="usb_device", PROGRAM="/bin/sh -c 'K=%k; K=$${K#usbdev}; printf bus/usb/%%03i/%%03i $${K%%%%.*} $${K#*.}'", NAME="%c", MODE="0644"
> but he libusb code looks fine).
libusb has no issues with the short names.
Kay
-------------------------------------------------------
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
prev parent reply other threads:[~2005-12-08 21:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 20:45 /dev/usbdevX.X? Andreas Jellinghaus
2005-12-08 21:06 ` Kay Sievers [this message]
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=20051208210615.GA17109@vrfy.org \
--to=kay.sievers@vrfy.org \
--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).