From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brian Gerst Date: Wed, 11 May 2005 01:22:43 +0000 Subject: Re: [ANNOUNCE] hotplug-ng 002 release Message-Id: <42815E63.5020508@didntduck.org> List-Id: References: <20050506212227.GA24066@kroah.com> <20050509211323.GB5297@tsiryulnik> <20050510224112.GA4967@kroah.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Per Liden Cc: Greg KH , linux-hotplug-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org Per Liden wrote: > On Tue, 10 May 2005, Greg KH wrote: > > >>On Wed, May 11, 2005 at 12:17:12AM +0200, Per Liden wrote: >> >>>I'd like to get a better understanding of that as well. Why invent a >>>second on demand module loader when we have kmod? The current approach >>>feels like a step back to something very similar to the old kerneld. >> >>kmod is not used at all if you are running udev on your system. > > > Since when does udev load modules for you? And how would it know when to > load "device less" modules such as filesystems? > > >>It's also better to allow userspace to make the decision as to if it >>should load a specific module or not, not the kernel. > > > If you don't want a specific module to be loaded, then don't build it. > You just said that yourself in the blacklisting dicsussion remember? ;) > (hint: "Don't build the OSS modules at all?"). Think about distibution kernels that build everything possible. -- Brian Gerst ------------------------------------------------------- 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