From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Date: Tue, 10 May 2005 20:13:55 +0000 Subject: Re: [ANNOUNCE] hotplug-ng 002 release Message-Id: <20050510201355.GB3226@suse.de> List-Id: References: <20050506212227.GA24066@kroah.com> <1115611034.14447.11.camel@localhost.localdomain> <20050509232103.GA24238@suse.de> <1115717357.10222.1.camel@localhost.localdomain> <20050510094339.GC6346@wonderland.linux.it> <4280AFF4.6080108@ums.usu.ru> <20050510172447.GA11263@wonderland.linux.it> In-Reply-To: <20050510172447.GA11263@wonderland.linux.it> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: "Alexander E. Patrakov" , Rusty Russell , linux-hotplug-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org On Tue, May 10, 2005 at 07:24:47PM +0200, Marco d'Itri wrote: > On May 10, "Alexander E. Patrakov" wrote: > > > Why not this or something similar (e.g. I want to blacklist the xxx and > > yyy modules)? (note, untested) Nice, I like it. > Because it's impossible to predict how it will interact with other > install and alias commands. Then we will just have to find out :) > A less fundamental but still major problem is that this would be a > different API, and both users and packages have been aware of > /etc/hotplug/blacklist* for a long time now. And as /etc/hotplug/* is going away for hotplug-ng, I don't think this is going to be an issue. Also, the blacklisting stuff should not be that prevelant anymore... thanks, greg k-h ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_ids93&alloc_id281&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