On Wed, Aug 29, 2012 at 3:06 PM, Thierry Vignaud <[email protected]> wrote: > On 29 August 2012 15:46, Colin Guthrie <[email protected]> wrote: >>> Is there any migration to do in drakx and ldetect because of this? >> >> Oh yeah I meant to send a message to the list about this. >> >> Yeah because we're now on kernel 3.5 we can no longer do certain things >> relating to this mount point. >> >> IIRC some ldetect stuff used it and some of the 3G and/or >> printer/scanner stuff might also depend on it and need to be migrated >> too. I don't know that code very well, but I know some folks complained >> when we stopped mounting it by default, so I've no doubt that it's use >> is lurking somewhere! >> >> I would guess that in some cases /dev/bus/usb/ might be sufficient for >> what is needed. > > Humm... > I've still around a patch making ldetect using libusb. > Sadly, we're missing some data... > Basically we would miss the kernel driver name binded with each usb device. > > We cannot workaround it since libusb misses with the ability to either > query the sysfs device path or to got the Port number > ("Port" in /proc/bus/usb/devices). > (I miss the Port number in order to compute the > /sys/bus/devices/usb/foobar path) > > W/o that I cannot retrieve the modalias which would help me to get the kernel > driver name. > > I guess I'll have to resurect that work and try harder to find some > workaround...
Why not using sysfs for everything directly?
