> When calling modprobe -q with a non-existing module, it returns with > exit code 1. According to the manpage, modprobe "normally" will report > an error, and with -q shouldn't, so I believe the exist code should > always be 0, at least that seems to be the assumption in some init > scripts (e.g. binfmt-support).
That part is ambiguous, but I guess "modprobe will simply ignore any bogus names" is pretty clear. ... and comments in the git log imply we _used_ to get this right. "" Andreas, at first glance this regression is due to your commit 73bdf4ab. Care to submit a patch to revert the relevant lines? Thanks! Alan -- To unsubscribe from this list: send the line "unsubscribe linux-modules" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
