Bug 52053 - sndconfig --mungepnp should be followed be depmod
sndconfig --mungepnp should be followed be depmod
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
7.3
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-08-19 16:50 EDT by Aleksey Nogin
Modified: 2014-03-16 22:22 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-08-19 16:50:22 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Aleksey Nogin 2001-08-19 16:50:18 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.
Comment 1 Bill Nottingham 2001-08-19 21:52:42 EDT
Are you sure you're running the correct modutils? That message is *removed* in
the current modutils.

Note You need to log in before you can comment on or make changes to this bug.