From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bill Nottingham Date: Wed, 26 Jan 2005 04:12:02 +0000 Subject: Re: usbcore vs. udev Message-Id: <20050126041202.GA17820@nostromo.devel.redhat.com> List-Id: References: <20050125184727.GA13793@nostromo.devel.redhat.com> In-Reply-To: <20050125184727.GA13793@nostromo.devel.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org Greg KH (greg@kroah.com) said: > > 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? Only because it emitted events on remove. :) > 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. Probably not. Perhaps hooking into hotplug for the class is better; what I was originally looking at is hooking into the class/device plug for the mounting of usbfs. Bill ------------------------------------------------------- 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