You should not have to wrap depmod. Standard 2.4.* modutils returns 0
for unresolved errors, for compatibility with previous behaviour. You
have to do depmod -u to get a non-zero return code. The -u flag was
added in modutils 2.4.7 and defaults to off. In modutils 2.5 it will
default to on, that will break code that relies on the existing
behaviour. I will not change modutils default behaviour in 2.4.
So why is your version of depmod breaking? Either you are specifying
-u or your distribution has hacked depmod to default -u to on. Check
depmod.c for variable flag_unresolved_error, it should default to 0.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/