From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Date: Tue, 09 Mar 2004 08:19:48 +0000 Subject: Re: [ANNOUNCE] udev 021 release Message-Id: <20040309081948.GI22057@kroah.com> List-Id: References: <20040303153403.21649.81059.Mailman@linux.us.dell.com> <4048D503.10808@mail.ru> In-Reply-To: <4048D503.10808@mail.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: rihad Cc: linux-kernel-digest@lists.us.dell.com, linux-kernel@vger.kernel.org, linux-hotplug-devel@lists.sourceforge.net On Fri, Mar 05, 2004 at 11:29:07PM +0400, rihad wrote: > Date: Wed, 3 Mar 2004 07:14:33 -0800 > From: Greg KH > > >Users need to learn that the kernel is changing models from one which > >automatically loaded modules when userspace tried to access the device, > >to one where the proper modules are loaded when the hardware is found. > > Does this mean that I will have modules for all my hardware hanging > around even if I'm not, say, using cdrom at the moment? Yup, why not? > And does it mean that if I rmmod -a the unused cdrom module and later > try to mount /cdrom, the correct module won't be magically insmod'ed? If you don't have the /dev entry there, how would anything know to load the module? > I like the idea of lazy module loading, and it seems that your model > doesn't fit in nicely, I could be wrong. How about "loading the modules for the hardware present"? What's wrong with that? thanks, greg k-h ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70&alloc_id638&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