Re: 2.5.26 hotplug failure

From: Greg KH (
Date: Wed Sep 18 2002 - 11:55:32 EST

On Wed, Sep 18, 2002 at 05:15:50PM +1000, Brad Hards wrote:
> On Wed, 18 Sep 2002 16:52, Greg KH wrote:
> > On Sun, Sep 15, 2002 at 11:53:41PM +0200, Duncan Sands wrote:
> > > A simple fix is to change the test to [ $COUNT -lt 2 ];
> >
> > Good catch, yes the drivers file disappeared, and until now, almost no
> > one noticed it :)
> I assume that /proc/bus/usb/drivers went to driverfs. Everyone likes the new
> guy:)

The functionality went there, not the actual file. The file is obsolete
now :)

> I'd like the file back. We have a lot of debugging advice that asks people to
> send that particular file to us, and it is very useful. Even if you update
> the few places that you can find, then you will still have a lot of confusion
> (well, if you have 2.4, then send this, and if you have 2.6, send this, and
> if that doesn't exist, and you're on 2.4, mount this filesystem, else mount
> this filesystem). Ugly, and increases the support workload.
> A symlink will do, assuming both filesystems are mounted. If we only have
> usbfs, I still want the data.

'ls <wherever_you_mounted_driverfs>/bus/usb/drivers' will now show you
all of the registered USB drivers. As for what the minor numbers are
for the drivers that happened to use the USB major number, I'm working
on that.

> Please fix this before 2.6.

Sorry, but I'm not going to put the file back. I understand your
concerns. We should have some kind of program (lsdev like) that shows
the system information present at that moment in time. It will be able
to provide what the /proc/bus/usb/drivers file showed in the past.


greg k-h
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

This archive was generated by hypermail 2b29 : Mon Sep 23 2002 - 22:00:23 EST