Thanks for your Oon-ee. Sun, May 29, 2011 at 10:53 AM, Oon-Ee Ng <ngoonee.talk@xxxxxxxxx> wrote: > On Sat, May 28, 2011 at 9:16 PM, Tom Gundersen <teg@xxxxxxx> wrote: > <snip> >> rc.conf - MODULES(!mod1, !mod2): blacklisting modules in the modules >> array will no longer have any effect. modprobe already provides two >> different ways of preventing modules from being loaded, so this is >> just a matter of updating some configuration files. To blacklist >> modules, add a new .conf file to /etc/modprobe.d/ with the contents >> >> blacklist mod1 >> blacklist mod2 > <snip> > > This seems a regression of current rc.conf behaviour (in essence, > moves another configuration back to upstream default which was > previously in rc.conf). Is there any good reason to keep current > behaviour (perhaps an Arch-specific udev rule which parses MODULES for > blacklisting?) I have not found any uses of the MODULES array like you describe (if they exist they should be considered bugs though, the MODULES array was not meant to be used in this way). However, if anyone knows of any, then please let me know. Cheers, Tom
