From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Blacklistiing modules
Date: Sat, 03 Dec 2005 23:51:44 +0000 [thread overview]
Message-ID: <20051203235144.GA14451@vrfy.org> (raw)
In-Reply-To: <43914216.2070403@pcuf.fi>
On Sat, Dec 03, 2005 at 08:58:30AM +0200, Jar wrote:
> Finally I have to delete orinoco_pci to get rid of it. That is not
> elegant way to handle this. Is there some other method than the delete
> method to handle this? Why the blacklisting doesn't work any more?
>
> Is some feture missing from udev/hotplug that should handle this kind of
> "many drivers to same hardware" dilemma?
My box has this:
$ grep "blacklist orinoco" /etc/modprobe.d/*
/etc/modprobe.d/prism2:blacklist orinoco_cs
/etc/modprobe.d/prism2:blacklist orinoco_pci
/etc/modprobe.d/prism2:blacklist orinoco_plx
The blacklist is a native feature of module-init-tools now.
Kay
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&op=click
_______________________________________________
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
next prev parent reply other threads:[~2005-12-03 23:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-03 6:58 Blacklistiing modules Jar
2005-12-03 23:51 ` Kay Sievers [this message]
2005-12-04 10:38 ` Jar
2005-12-04 12:21 ` Kay Sievers
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=20051203235144.GA14451@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).