From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Date: Fri, 11 Feb 2005 19:33:16 +0000 Subject: Re: [ANNOUNCE] hotplug-ng 001 release Message-Id: <20050211193316.GA20015@suse.de> 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 Fri, Feb 11, 2005 at 07:47:20PM +0100, Marco d'Itri wrote: > On Feb 11, Greg KH wrote: > > > It's not only pci, but all types of busses need this kind of "coldplug" > > functionality. And yes, I have plans to provide that functionality in > > this package too. > Important feature request: some support for a /etc/hotplug/blacklist.d/ > directory is needed before I can use it for the debian package. Why? Why not just not build the blacklisted modules? > I know that with the aliases method hotplug itself does not know the > actual module name, so maybe this should be discussed with Rusty and > added to modprobe. Yes, blacklisting should be a modprobe option, not a hotplug option. thanks, greg k-h ------------------------------------------------------- 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