Bug 5717 - Replace all references to /etc/conf.modules with /etc/modules.conf
Replace all references to /etc/conf.modules with /etc/modules.conf
Product: Red Hat Linux
Classification: Retired
Component: modutils (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Michael K. Johnson
Depends On:
  Show dependency treegraph
Reported: 1999-10-08 05:50 EDT by Keith Owens
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-02-02 00:03:36 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Keith Owens 1999-10-08 05:50:35 EDT
As modutils maintainer, the inconsistent use of conf.modules
instead of modules.conf has been annoying me.  Starting with
modutils-2.3.4, modutils will warn about conf.modules.  When
kernel/modutils 2.5 is released, that warning will become an

I am notifying all distributions that I can contact about
this change and requesting that all documentation (other
than modutils itself) be checked for conf.modules and
changed where necessary.
Comment 1 Bill Nottingham 1999-10-08 11:51:59 EDT
Duly noted.

Initial plan is to move conf.modules to modules.conf on upgrade,
& create a symlink (and fix the various tools).  Probably won't
be implemented here for a little while, though.
Comment 2 Cristian Gafton 2000-01-04 17:29:59 EST
Assigned to dledford
Comment 3 Jeremy Katz 2000-02-02 00:03:59 EST
This still hasn't been resolved in current Rawhide.  Considering I'd say the
chances are medium-high to high that 2.4.x will come out after the release of
the next version of Red Hat, and that at the same time, people will need to
upgrade modutils for stuff to work "correctly", it would be good if all the
tools already knew they should be using modules.conf instead of conf.modules.
Comment 4 Trond Eivind Glomsrxd 2001-03-13 10:39:13 EST
It has been fixed for some time now.

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