From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Brownell Date: Mon, 25 Nov 2002 23:12:15 +0000 Subject: Re: should the module script be invoked every time? Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org Pedro Lopez-Cabanillas wrote: > ... >> >>This is a bug that's been hanging around for a while. The fix should >>finally be in current CVS, along with a few other updates mostly for >>a bit more intelligence about how hotplug changed in 2.5 ... > > > That's good, but IMHO there are several situations for hotplug to give some > kind of support. There are always new features that _could_ be added... > 1. Scripts that need to run once, before or after modprobe. This is usually > done with modules.conf (pre-install/post-install), but i would like to do > that with hotplug also... Why have two ways to do the same thing? Hotplug deals with devices, modutils deal with modules. Having two ways to do something means twice the testing, and exponential growth in the number of failure modes as you keep adding other ways... > 2. Scripts that need to run every time the device is plugged or unplugged, > even if the driver is already loaded or not. That is the case of our ezusbmidi > firmware loader. As I said, the fact that it _hasn't_ been happening that way is just a bug ... which should now be fixed. - Dave ------------------------------------------------------- This SF.net email is sponsored by: Get the new Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en _______________________________________________ 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