From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Date: Fri, 11 Feb 2005 19:57:27 +0000 Subject: Re: [ANNOUNCE] hotplug-ng 001 release Message-Id: <20050211195727.GA20459@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 08:40:39PM +0100, Marco d'Itri wrote: > On Feb 11, Greg KH wrote: > > > > 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? > Because generic kernel packages are supposed to ship modules for the > different needs of different users. What packages modify the blacklist? Or is that a userconfig type thing? > > > 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. > It would have to enable blacklisting only when called by hotplug. No, it would use blacklisting when called by aliases. That would be easier, right? 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