From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Sat, 03 Dec 2005 23:51:44 +0000 Subject: Re: Blacklistiing modules Message-Id: <20051203235144.GA14451@vrfy.org> List-Id: References: <43914216.2070403@pcuf.fi> In-Reply-To: <43914216.2070403@pcuf.fi> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org 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_id865&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