Description of problem: module-init-tools and hwdata packages contain the files blacklist and blacklist-compat in /etc/modprobe.d/. Difference in these files seems to be only in one also blacklisting matrxfb_base. Can one of these files be removed and the data on be maintained in one package? regards, Florian La Roche Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I wonder if this belongs in the hwdata package. Shall I kill it from m-i-t? Jon.
adding Harald to CC: Harald: can you remember why you have added blacklist-compat to module-init-tools ??
was it me? only remember to have added various framebuffer modules..
yes, framebuffer modules, which were autoloaded by udev have been added by me.
If it needs editing more often, then hwdata is anyway changed in most update releases and might make more sense. For /etc/modprobe.d/ it would also be good if only files with a certain ending would be used like *.conf as then backup files would not accidentially be read in etc. greetings, Florian La Roche
blacklist-compat can be removed, if the modules in it are mentioned in another place. framebuffer modules must _not_ be loaded automatically by udev.
Harald: I've added 'blacklist matrxfb_base' to hwdata's blacklist (Rawhide). JCM: Please remove the file blacklist-compat from module-init-tools as it is obsolete now. comment #5 still needs to be solved. At least hwdata would require some minor changes to use blacklist.conf instead of 'blacklist'. Maybe it would suffice to exclude files ending with '~' from being read ? Atm modprobe reads every file in that directory without exception.
I've opened up another bz for comment #5. Seems also the kernel now starts shipping blacklist files, so the number of dependencies is growing. ;-( regards, Florian La Roche
Karsten, I do not own module-init-tools anymore.
Ok. I will remove the obsolete file. Jon.