On Fri, Mar 15, 2013 at 12:34 AM, Lucas De Marchi <lucas.demar...@profusion.mobi> wrote: > > On Mar 14, 2013 4:25 PM, "Alberto Milone" <alberto.mil...@canonical.com> > wrote: >> >> On 14/03/13 23:34, Lucas De Marchi wrote: >> > Do you realize you are quoting the man page of modutils? It's not >> > kmod or module-init-tools, which kmod replaced. It's the old modutils >> > used with Linux 2.4. kmod is a drop-in replacement to m-i-t, but we >> > are not putting back the things from modutils if we don't have a >> > reason to. >> >> It wasn't documented in m-i-t but it was supported. See line 167 of the >> following file: >> >> https://github.com/vadmium/module-init-tools/blob/master/generate-modprobe.conf > > This script shows exactly the opposite... it was not supported in m-i-t and > thus they were converted to install commands using /bin/true > >> >> > Why do you want to get the initstate of an inexistent module? Why do >> > you think null and off should be special? And more important, you >> > still didn't answer why the available options are not working for you >> > - you said you cannot get the initstate - but that is a non-issue >> > since libkmod shouldn't even try to get the initstate. >> > >> > Please give some real example of what you are trying to do so we can >> > figure out a solution. >> >> All I'm saying is that modprobe raises an error if it finds strings such >> as the following in configuration files in /etc/modprobe.d/ : >> >> alias nouveau off > > And it's right to complain, it's not something valid in the > configuration.... It never was, even in m-i-t. > >> >> As in comment 15, this is particularly annoying when it causes >> update-initramfs to fail: >> >> update-initramfs: Generating /boot/initrd.img-3.8.0-3-generic >> modprobe: ../tools/modprobe.c:550: print_action: Assertion >> `kmod_module_get_initstate(m) == KMOD_MODULE_BUILTIN' failed. >> Aborted (core dumped) >> >> It seems that update-initramfs calls modprobe in the following way: >> >> modprobe --set-version=3.8.0-3-generic --ignore-install --quiet >> --show-depends nouveau
Ok... I pushed an alternative fix to have the same behavior as for modprobe (except the exit code). As I said "off" and "null" are note special, and they weren't in module-init-tools neither. The thing we were doing wrong is that in presence of an alias to anything that doesn't exist we should exit silently instead of exploding. I fixed and added a test case to the testsuite with this in the config file: "alias psmouse deaddood". It's working now, at least for me. Let me know if you still have issues. Lucas De Marchi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
