-   Slackware (
-   -   ?Odd bug. modprobe.blacklist~ behaves as modprobe.blacklist (

arubin 11-05-2006 09:49 AM

?Odd bug. modprobe.blacklist~ behaves as modprobe.blacklist
Is this a bug.

I edited /etc/modprobe.d/modprobe.blacklist adding the line

blacklist bcm43xx

I typed it wrong and entered

blaclist bcm43xx

So there were a host of message on booting saying blaclist was not recognised.

I edited the file and rebooted and had a host of messages about blaclist in modprobe.blacklist~ not being recognised.

All sorted now but why is modprobe.blacklist~ being examined?

crisostomo_enrico 11-05-2006 07:08 PM

It's behaviour by design. man 5 modprobe.conf says:

All the files under the /etc/modprobe.d directory are used.

Then, those *~ files left behind by your editor will be used, too. File names in modprobe.d is just a convenience.


All times are GMT -5. The time now is 07:53 PM.