On Wed, May 11, Erik van Konijnenburg wrote: > > Lets see: > - You want less code (for good reason, it really is a lot more > than the equivalent in perl) > - Marco wants the blacklist only to work when invoked via kernel, > and needs only /etc/hotplug/blacklist.d. On Tue, May 10, Greg KH wrote: > On Wed, May 11, 2005 at 02:05:19AM +0200, Marco d'Itri wrote: > > On May 11, Erik van Konijnenburg wrote: > > > > Thank you for your patch! I have two comments: > > - the blacklist should be used only if modprobe is run by the kernel > > (check $SEQNUM?) > > No, it should be used only if you are running modprobe on an alias. And i second this. It does not matter if modprobe was invoked via kernel or not. The blacklist has to be used if there is a chance that a wrong module could be loaded. And that happens just if you are running modprobe on an alias. => use blacklist if the module name was found in the kernels alias table. -- ciao, christian 睡眠不足はいい仕事の敵だ。 ------------------------------------------------------- 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&opk _______________________________________________ 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