Date: Tue, 10 May 2005 13:13:55 -0700
From: Greg KH <gregkh@suse.de>
To: "Alexander E. Patrakov" <patrakov@ums.usu.ru>,
       Rusty Russell <rusty@rustcorp.com.au>,
       linux-hotplug-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] hotplug-ng 002 release
Message-ID: <20050510201355.GB3226@suse.de>
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>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20050510172447.GA11263@wonderland.linux.it>
User-Agent: Mutt/1.5.8i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1011
Lines: 29

On Tue, May 10, 2005 at 07:24:47PM +0200, Marco d'Itri wrote:
> On May 10, "Alexander E. Patrakov" <patrakov@ums.usu.ru> 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/