[arch-projects] initscripts: about MODULES() behaviour and blacklist
Hello, Tom Gundersen: "If you want to have a temporary workaround I guess it would be possible to blacklist your wireless module in /etc/modprobe.d and add it to MODULES in rc.conf." [#1]. But in functions::udev_modprobe() there is a modprobe -ab, and -b implies does not load a blacklisted module. Since MODULES() is supposed (at least for me) to be "always load all listed modules", should be -b removed from modprobe line? Good Luck! [#1] https://bugs.archlinux.org/task/27938#comment88136
On Fri, Jan 20, 2012 at 8:01 AM, Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar> wrote:
Hello,
Tom Gundersen: "If you want to have a temporary workaround I guess it would be possible to blacklist your wireless module in /etc/modprobe.d and add it to MODULES in rc.conf." [#1].
But in functions::udev_modprobe() there is a modprobe -ab, and -b implies does not load a blacklisted module. Since MODULES() is supposed (at least for me) to be "always load all listed modules", should be -b removed from modprobe line?
Damn, you caught me contradict myself. I think you might have caused a rupture in the space-time continuum... My comment was wrong, this is how it used to work, but I forgot that we have changed it. I believe the current behavior is the correct one, if a module is blacklisted we should not automatically insert it (not from udev, nor from MODULES). This is particularly useful if the module is causing problems and is blacklisted on the kernel command line. Thanks for pointing out my mistake, I'll correct myself on the bug report. Cheers, Tom
On 01/20/2012 09:21 AM, Tom Gundersen wrote:
On Fri, Jan 20, 2012 at 8:01 AM, Gerardo Exequiel Pozzi <vmlinuz386@yahoo.com.ar> wrote:
Hello,
Tom Gundersen: "If you want to have a temporary workaround I guess it would be possible to blacklist your wireless module in /etc/modprobe.d and add it to MODULES in rc.conf." [#1].
But in functions::udev_modprobe() there is a modprobe -ab, and -b implies does not load a blacklisted module. Since MODULES() is supposed (at least for me) to be "always load all listed modules", should be -b removed from modprobe line? Damn, you caught me contradict myself. I think you might have caused a rupture in the space-time continuum... My comment was wrong, this is how it used to work, but I forgot that we have changed it.
I believe the current behavior is the correct one, if a module is blacklisted we should not automatically insert it (not from udev, nor from MODULES). This is particularly useful if the module is causing problems and is blacklisted on the kernel command line.
Thanks for pointing out my mistake, I'll correct myself on the bug report.
Cheers,
Tom
Oh no! There is a new Black Hole! OK, so for anyone that want to blacklist a module "for udev" but need to be loaded manually on startup, should write your own initscript hook / rc.d / rc.local. -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1
On Fri, Jan 20, 2012 at 4:30 PM, Gerardo Exequiel Pozzi
OK, so for anyone that want to blacklist a module "for udev" but need to be loaded manually on startup, should write your own initscript hook / rc.d / rc.local.
I'd probably put a modprobe in rc.local for now. That said, if you want to blacklist something from udev, but load it anyway, that's a sign that something is really broken and should be fixed in the proper place. We therefore do not want to provide/encourage permanent workarounds. -t
participants (2)
-
Gerardo Exequiel Pozzi
-
Tom Gundersen