Red Hat Bugzilla – Bug 52053
sndconfig --mungepnp should be followed be depmod
Last modified: 2014-03-16 22:22:45 EDT
Currently "sndconfig --mungepnp" is called *after* "depmod -a". This means
that if sndconfig decides to update the modules.conf, then we'll end up
with lots of warnings about modules.conf being newer then modules.dep (and
may be other problems - I am not sure).
IMHO, we should either move sndconfig before depmod or change sndconfig so
that it calls depmod whenever it updates modules.conf (although the second
solution would cause depmod to be sometime ran twice during boot).
P.S. See bug #44760 for another problem with depmod position in initscripts
- still exists in Roswell2.
Are you sure you're running the correct modutils? That message is *removed* in
the current modutils.