From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Date: Sat, 26 Feb 2005 00:07:54 +0000 Subject: Re: The Next Generation Message-Id: <20050226000754.GA30105@kroah.com> List-Id: References: <20050217190941.GA1561@vrfy.org> In-Reply-To: <20050217190941.GA1561@vrfy.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Sat, Feb 26, 2005 at 12:59:52AM +0100, Marco d'Itri wrote: > On Feb 26, Greg KH wrote: > > > Now we _can_ build hotplug-ng out of udev pieces and parts, that I don't > > have a problem with. And, if udev is running on a box, have it handle > > the hotplug functionality is also an acceptable thing (as long as > > nothing external to udev has to change, like the scripts in > > /etc/hotplug.d/). But we can't mandate that udev must be used, sorry. > This was my first objection, but what's wrong with disabling the pieces > of udev which deal with devices creation and use the infrastructure for > hotplug? There is nothing wrong with that, and I intend to do that (actually, if you look at the current code, it is just that...) > > - be a drop in replacement (through other helper programs) to > > the existing linux-hotplug module loading scripts. > .oO(no blacklisting support yet... :-) ) Oh, I know :) 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