From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Date: Fri, 24 Jun 2005 18:50:00 +0000 Subject: Re: fully udev-based hotplug system Message-Id: <20050624185000.GA32065@kroah.com> List-Id: References: <20050623215418.GA16536@wonderland.linux.it> In-Reply-To: <20050623215418.GA16536@wonderland.linux.it> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Fri, Jun 24, 2005 at 02:33:41PM -0400, Bill Nottingham wrote: > Greg KH (greg@kroah.com) said: > > > > The idea is to use udev as the hotplug multiplexer and totally kill > > > > /sbin/hotplug and /etc/hotplug.d/default/default.hotplug (and hotplug.d/ > > > > too when other packages will stop using it). > > > > > > > > ACTION="add", SUBSYSTEM="pci", MODALIAS="*", \ > > > > RUN+="/sbin/modprobe $modalias" > > > > > > > > ACTION="add", SUBSYSTEM="usb", MODALIAS="*", \ > > > > RUN+="/sbin/modprobe $modalias" > > > > > > How does this handle when multiple modules claim the same alias? > > > (this happens for PCI devices...) > > > > > > One method is to patch the module utilities to just insert all > > > matches, I suppose. > > > > That's exactly what modprobe now does in its latest version. > > So, if udev has come down to just this, why isn't the kernel running > modprobe itself? :) Someone has suggested just this, see the horrible patch in the archives :) thanks, greg k-h ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&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