/dev/usbdevX.X?

/dev/usbdevX.X?

[Andreas Jellinghaus]

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

Re: /dev/usbdevX.X?

[Kay Sievers]

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