On Wed, May 11, 2005 at 12:58:18PM +0200, Marco d'Itri wrote:> On May 11, Rusty Russell <rusty@rustcorp.com.au> wrote:> > > Then perhaps depmod should be the one to read a blacklist file? It> > produces the modules.alias file where these things live.> I think this would be confusing for users.

Second that. Modprobe remains smaller, but we would need some wrapperaround depmod to do the blacklisting, plus the user or packager thatadds an entry to the blacklist has to arrange for depmod to be redoneat the right time. It's so much more convenient if depmod only hasto run at kernel install time.

Here's a second version of the patch, now based on 'blacklist' keyword.