Re: usbcore vs. udev

[Greg KH <greg@kroah.com>]

On Tue, Jan 25, 2005 at 08:33:41PM -0500, Bill Nottingham wrote:
> Greg KH (greg@kroah.com) said: 
> > On Tue, Jan 25, 2005 at 01:47:27PM -0500, Bill Nottingham wrote:
> > > usbcore seems to only generate udev events on removal; it never
> > > generates add events. Any particular reason?
> > > 
> > > (2.6.10-acX, if it matters.)
> > 
> > What type of udev events?  Those for the usb major number?  So things
> > like the USB printer driver don't work anymore?
> 
> modprobe usbcore yields no events to udev, as far as I can tell
> by putting a catchall script in /etc/dev.d/default.

Nor should it.  Why would you think it should?  No /dev nodes are
owned by usbcore.

> modprobe -r usbcore yields:
> 
> ACTION=remove
> DEVNAME=/dev/usb
> DEVPATH=/class/usb
> 
> and
> 
> ACTION=remove
> DEVNAME=/dev/usb_host
> DEVPATH=/class/usb_host
> 
> I'd expect to get 'add' for the same devname/devpath on load
> of usbcore, or no events on usbcore removal.

Ah, you mean the class add and remove.  Hm, I think we don't emit those
because those are classes (not class_dev), and at remove time we don't
know to not emit them.  I'm considering always emiting them at add also,
but it might mess up some userspace stuff, so I'm trying to be cautious
and test it out a lot first.

But again, udev doesn't care about these events, nor should it.

thanks,

greg k-h


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
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