Bug 52053 - sndconfig --mungepnp should be followed be depmod
Summary: sndconfig --mungepnp should be followed be depmod
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: initscripts
Version: 7.3
Hardware: i386
OS: Linux
medium
low
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-08-19 20:50 UTC by Aleksey Nogin
Modified: 2014-03-17 02:22 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2001-08-19 20:50:22 UTC
Embargoed:

Attachments (Terms of Use)

Description Aleksey Nogin 2001-08-19 20:50:18 UTC 
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-20 01:52:42 UTC 
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.