Re: [ANNOUNCE] hotplug-ng 002 release

["Alexander E. Patrakov" <patrakov@ums.usu.ru>]

Marco d'Itri wrote:

> On May 10, Rusty Russell <rusty@rustcorp.com.au> wrote:
>
>  
>
> > So I rewrote it yesterday, so now it passes the testsuite.  I also added
> > a test.  It's in 3.2-pre4: if there are no more requests/bugs in the
> > next couple of days, I'll make that 3.3.
> >    
> My major request is support for /etc/hotplug/blacklist.d/ in modprobe:
> now that the hotplug subsystem does not know anymore the name of the
> module to be loaded, it's up to modprobe to check the system blacklist.
> IME, without this feature users will not accept hotplug-ng.
>  
Why not this or something similar (e.g. I want to blacklist the xxx and 
yyy modules)? (note, untested)

in /etc/modprobe.d/hotplug_blacklist:

install xxx /sbin/blacklisted xxx
install yyy /sbin/blacklisted yyy

In /sbin/blacklisted:

#!/bin/sh
if [ -z "$SEQNUM" ] ; then
   /sbin/modprobe -i "$@"
else
   exit 1
fi

Any other variable that is certainly present in hotplug events will also 
work instead of $SEQNUM.

--
Alexander E. Patrakov

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/