Bug 5717 - Replace all references to /etc/conf.modules with /etc/modules.conf
Summary: Replace all references to /etc/conf.modules with /etc/modules.conf
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: modutils
Version: 6.1
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Michael K. Johnson
QA Contact:
URL: http://www.progressive-comp.com/Lists...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 1999-10-08 09:50 UTC by Keith Owens
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2000-02-02 05:03:36 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Keith Owens 1999-10-08 09:50:35 UTC 
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
error.

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 15:51:59 UTC 
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 22:29:59 UTC 
Assigned to dledford
Comment 3 Jeremy Katz 2000-02-02 05:03:59 UTC 
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 15:39:13 UTC 
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.