On Wed, Mar 03, 2004 at 04:30:13PM -0500, James H. Cloos Jr. wrote:
> Any idea what might modprobe evbug.ko w/o operator intervention?
... hotplug scripts?
--
Vojtech Pavlik
SuSE Labs, SuSE CR
On Wednesday 03 March 2004 04:30 pm, James H. Cloos Jr. wrote:
> Any idea what might modprobe evbug.ko w/o operator intervention?
>
It's new hotplug scripts. Put modules you do not want to be automatically
loaded even if they think they have hardware/facilities to bind to into
/etc/hotplug/blacklist
I, for example, have evbug, joydev, tsdev and eth1394 there.
Greg, any chance adding evbug to the default version of hotplug package?
--
Dmitry
On Fri, 5 Mar 2004 02:38 pm, Dmitry Torokhov wrote:
> On Wednesday 03 March 2004 04:30 pm, James H. Cloos Jr. wrote:
> > Any idea what might modprobe evbug.ko w/o operator intervention?
>
> It's new hotplug scripts. Put modules you do not want to be automatically
> loaded even if they think they have hardware/facilities to bind to into
> /etc/hotplug/blacklist
>
> I, for example, have evbug, joydev, tsdev and eth1394 there.
>
> Greg, any chance adding evbug to the default version of hotplug package?
Of note: evbug is in /etc/hotplug/blacklist in the Debian hotplug package by
default, with a comment in said file about it being debian specific.
On Thu, Mar 04, 2004 at 10:38:13PM -0500, Dmitry Torokhov wrote:
> On Wednesday 03 March 2004 04:30 pm, James H. Cloos Jr. wrote:
> > Any idea what might modprobe evbug.ko w/o operator intervention?
> >
>
> It's new hotplug scripts. Put modules you do not want to be automatically
> loaded even if they think they have hardware/facilities to bind to into
> /etc/hotplug/blacklist
>
> I, for example, have evbug, joydev, tsdev and eth1394 there.
>
> Greg, any chance adding evbug to the default version of hotplug package?
Care to send me a patch for it?
thanks,
greg k-h
On Monday 08 March 2004 04:32 pm, Greg KH wrote:
> On Thu, Mar 04, 2004 at 10:38:13PM -0500, Dmitry Torokhov wrote:
> > On Wednesday 03 March 2004 04:30 pm, James H. Cloos Jr. wrote:
> > > Any idea what might modprobe evbug.ko w/o operator intervention?
> > >
> >
> > It's new hotplug scripts. Put modules you do not want to be automatically
> > loaded even if they think they have hardware/facilities to bind to into
> > /etc/hotplug/blacklist
> >
> > I, for example, have evbug, joydev, tsdev and eth1394 there.
> >
> > Greg, any chance adding evbug to the default version of hotplug package?
>
> Care to send me a patch for it?
>
> thanks,
>
> greg k-h
>
Ok, here it is, against today's CVS..
--- admin/etc/hotplug/blacklist.orig 2004-03-10 00:51:59.000000000 -0500
+++ admin/etc/hotplug/blacklist 2004-03-10 00:53:30.000000000 -0500
@@ -18,3 +18,6 @@
# At least 2.4.3 and later xircom_tulip doesn't have that conflict
# xircom_tulip_cb
dmfe
+
+#evbug is a debug tool and should be loaded explicitly
+evbug
On Wed, Mar 10, 2004 at 01:38:36AM -0500, Dmitry Torokhov wrote:
> On Monday 08 March 2004 04:32 pm, Greg KH wrote:
> > On Thu, Mar 04, 2004 at 10:38:13PM -0500, Dmitry Torokhov wrote:
> > > On Wednesday 03 March 2004 04:30 pm, James H. Cloos Jr. wrote:
> > > > Any idea what might modprobe evbug.ko w/o operator intervention?
> > > >
> > >
> > > It's new hotplug scripts. Put modules you do not want to be automatically
> > > loaded even if they think they have hardware/facilities to bind to into
> > > /etc/hotplug/blacklist
> > >
> > > I, for example, have evbug, joydev, tsdev and eth1394 there.
> > >
> > > Greg, any chance adding evbug to the default version of hotplug package?
> >
> > Care to send me a patch for it?
> >
> > thanks,
> >
> > greg k-h
> >
>
> Ok, here it is, against today's CVS..
Applied, thanks.
greg k-h