From mboxrd@z Thu Jan 1 00:00:00 1970 From: Roman Kagan Date: Sat, 12 Feb 2005 00:10:10 +0000 Subject: Re: [ANNOUNCE] hotplug-ng 001 release Message-Id: <20050212001010.GH2568@katya> List-Id: References: <20050211004033.GA26624@suse.de> In-Reply-To: <20050211004033.GA26624@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Sat, Feb 12, 2005 at 12:35:10AM +0100, Marco d'Itri wrote: > On Feb 12, Roman Kagan wrote: > > Besides, if you make sure your modprobe.blacklist is included at the end > > of your modprobe.conf, you can guarantee the blacklisting wins. > I have no modprobe.conf, debian (and I understand SuSE too) uses > /etc/modprobe.d/. Then do use modprobe.conf, reading as include /etc/modprobe.d include /etc/modprobe-blacklist.d Well, there are many possible scenarios, what I'm trying to say is that the current modprobe.conf syntax is sufficient for blacklisting. Roman. ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_ide95&alloc_id396&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