From mboxrd@z Thu Jan 1 00:00:00 1970 From: Roman Kagan Date: Fri, 11 Feb 2005 08:10:44 +0000 Subject: Re: [ANNOUNCE] hotplug-ng 001 release Message-Id: <20050211081043.GA2527@katya> List-Id: References: <20050211004033.GA26624@suse.de> In-Reply-To: <20050211004033.GA26624@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Thu, Feb 10, 2005 at 10:46:57PM -0800, Greg KH wrote: > On Thu, 2005-02-10 at 22:18 -0500, Bill Nottingham wrote: > > How does this interact with current usage of udevsend as the hotplug > > multiplexer? > > [...] > And finally, even if you do use udevstart to manager /sbin/hotplug > events, you still need a module autoloader program. This package > provides executables for that problem, if you don't want to (or you > can't) use the existing linux-hotplug scripts. udev will never do the > module loading logic Why? As a matter of fact I've been meaning to submit a patch to udev, adding the functionaly to generate the fnmatch-able device name in the module-init-utils' style, and propagate it to the hotplug callouts via an environment variable, say DEVALIAS or MODNAME. Then the only thing left to do would be to teach modprobe to read this environment variable when called without arguments, as well as $ACTION, and hook a symlink to /sbin/modprobe in /etc/hotplug.d/default . This would provide a smooth upgrade path and IMHO cause less confusion with multiple hotplug multiplexers. Cheers, Roman. ------------------------------------------------------- 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