Bug 168069 - modprobe doesn't ignore RCS files in /etc/modprobe.d
Summary: modprobe doesn't ignore RCS files in /etc/modprobe.d
Alias: None
Product: Fedora
Classification: Fedora
Component: module-init-tools
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2005-09-12 04:41 UTC by Jonathan Kamens
Modified: 2014-03-17 02:55 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2005-09-12 19:46:57 UTC

Attachments (Terms of Use)

Description Jonathan Kamens 2005-09-12 04:41:14 UTC
I check in all my config files with RCS before editing them.  I recently added a
line to /etc/modprobe.d/backlist, and hence created /etc/modprobe.d/RCS and
/etc/modprobe.d/RCS/blacklist,v.  Modprobe tried to read the latter and
obviously got all confused.  This is wrong behavior.  Various other tools which
have ".d" folders are smart enough not to read RCS files checked in underneath
them.  Whatever logic those tools use, modprobe needs to use as well.

Comment 1 Bill Nottingham 2005-09-12 19:46:57 UTC
This would be a somewhat significant divergence from the upstream
module-init-tools code, and therefore, it's unlikely that we'd do work to
specifically add this support.

Reporting this to the upstream maintainers might be more effective.

Comment 2 Jonathan Kamens 2005-09-12 20:55:09 UTC
CLOSED/UPSTREAM used to mean that Red Hat had reported the bug upstream, or at 
least that what I thought it meant.  I've seen it used recently to mean "YOU 
should report the bug upstream."  When did this change (or did it change)?

"rpm -qi module-init-tools" doesn't list an author or a URL for where this 
package comes from, so who do I report it to?

Comment 3 Bill Nottingham 2005-09-12 21:25:45 UTC
The AUTHORS file in the source tarball lists:

Rusty Russell <rusty@rustcorp.com.au>
Adam J. Richter <adam@yggdrasil.com>

I've sent this issue to them by e-mail, along with a query as to whether there's
a better mechanism for this.

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