Re: [PATCH] apply blacklist to builtin aliases only

[Anssi Hannula <anssi@xxxxxxxxxxxx>]

Kay Sievers kirjoitti torstai, 6. toukokuuta 2010 13:13:21:
> On Wed, May 5, 2010 at 20:22, Anssi Hannula <anssi@xxxxxxxxxxxx> wrote:
> > modprobe.conf(5) says:
> > "the blacklist keyword indicates that all of that particular module's
> > internal aliases are to be ignored"
> > 
> > However, currently the keyword causes even manually defined aliases to be
> > ignored.
> 
> Yes, and it is doing this on purpose. It does not matter where an
> alias is coming from, a blacklist entry should prevent the loading of
> a module in all cases.
> 
> The man page should be corrected, we seem to have missed that.

Ah, we were hoping to use it like follows:
Four modules foo1, foo2, foo3, foo4 match the same hardware.

All of them are blacklisted, and to select the used driver an alias is used:
alias foo foo3

and then when a program (X server) runs "modprobe foo" the aliased one will be 
loaded.

Is there a suggested simple way to do that?

If not, I'm sure we'll find another solution :)

-- 
Anssi Hannula
--
To unsubscribe from this list: send the line "unsubscribe linux-modules" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html