On 14/03/13 03:39, Lucas De Marchi wrote: > Hi Alberto > > First of all, please inline your patch next time, so we can comment on it. >
Sorry about that. > On Wed, Mar 13, 2013 at 1:15 PM, Alberto Milone > <alberto.mil...@canonical.com> wrote: >> Hi all, >> >> I think the problem is that modprobe looks for the module (which in this >> case is aliased as "off") in /sys and raises an error if it doesn't find >> it (there's no such thing as an "off" module in /sys). >> >> In the attached patch I check that the module name is not "off" or >> "null" before doing assert(kmod_module_get_initstate(m) == >> KMOD_MODULE_BUILTIN). > > Why is "off" and "null" special? > Let me quote this page: http://ccrma.stanford.edu/planetccrma/man/man5/modules.conf.5.html "Note that the line: alias some_module off will make modprobe ignore requests to load that module. Another special alias is: alias some_module null which will make requests for some_module always succeed, but no module will actually be installed. This can be used as a base for stacks created via the above and below directives." > >> >> This solves the problem on my systems. > > What are you solving that is not solved by putting /bin/true or > blacklisting the module? As you can see, "blacklist" is different from "off". Furthermore udev ignores blacklist but honours "off". And, as I said, the problem is that we cannot get the initstate ( /sys/module/$module_name/initstate ) of "off" or "null" because they are not real modules and using "/bin/true" as the installation command (if this is what you're suggesting) won't solve the problem. -- Alberto Milone Software Engineer Hardware Enablement Team Professional and Engineering Services -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
