Bug 177342 - fix inclusion of modprobe.conf.dist
fix inclusion of modprobe.conf.dist
Product: Fedora
Classification: Fedora
Component: module-init-tools (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Harald Hoyer
Depends On:
Blocks: FC5Target
  Show dependency treegraph
Reported: 2006-01-09 16:29 EST by Bill Nottingham
Modified: 2014-03-16 22:57 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-01-24 13:57:19 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 Bill Nottingham 2006-01-09 16:29:01 EST
Right now, we patch the module tools to automatically include modprobe.conf.dist.

This needs to be reworked to fit in better with upstream, either using include
statements (including adding the necessary include with a %post program) or
using /etc/modprobe.d.

Also, modprobe.conf.dist probably could stand some pruning - there's decent
chunks of it that aren't relevant any more.
Comment 1 Harald Hoyer 2006-01-24 09:10:42 EST
what do you mean? get rid of module-init-tools-allconf.patch ??
Comment 2 Bill Nottingham 2006-01-24 13:57:19 EST
Hm, looking at it again...

The issue is that current upstream module-init-tools only supports either
a) /etc/modprobe.conf
b) /etc/modprobe.d

We patch it to read modprobe.conf, then modprobe.d. If we went with upstream, we
would in theory have to move modprobe.conf to modprobe.d. However, that means
the first app to write a modprobe.conf (crappy nVidia %post script, or
something) would cause all the default state to not get read.  So maybe that's
not the best solution.

Probably best to just keep changing this for our packages.

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