From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, "James H. Cloos Jr." <cloos@jhcloos.com>
Subject: Re: evbug.ko
Date: Wed, 10 Mar 2004 01:38:36 -0500 [thread overview]
Message-ID: <200403100138.41453.dtor_core@ameritech.net> (raw)
In-Reply-To: <20040308213241.GE16396@kroah.com>
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
next prev parent reply other threads:[~2004-03-10 6:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 21:30 evbug.ko James H. Cloos Jr.
2004-03-04 18:13 ` evbug.ko Vojtech Pavlik
2004-03-05 3:38 ` evbug.ko Dmitry Torokhov
2004-03-05 3:58 ` evbug.ko Stuart Young
2004-03-08 21:32 ` evbug.ko Greg KH
2004-03-10 6:38 ` Dmitry Torokhov [this message]
2004-03-11 23:55 ` evbug.ko Greg KH
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200403100138.41453.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=cloos@jhcloos.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox