With reference to older discussions about blacklisting methods -
modprobe supports -b (or in long form --use-blacklist) that will also
block explicit loading by standard module name. Thus you could nicely
avoid shell wrapper on fb stuff.
The switch won't block implicit dependencies though (so if A requires B,
B is blacklisted, then modprobe -b A will still load A and B). That
shouldn't be a problem from udev's perspective though.
Stock udev rules will use -b by default from the next release, peeking
at the mailing list.
FYI.
