Bug 177342

Summary:	fix inclusion of modprobe.conf.dist
Product:	[Fedora] Fedora	Reporter:	Bill Nottingham <notting>
Component:	module-init-tools	Assignee:	Harald Hoyer <harald>
Status:	CLOSED WORKSFORME	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	rvokal
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-01-24 18:57:19 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	150221

Description Bill Nottingham 2006-01-09 21:29:01 UTC

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 14:10:42 UTC

what do you mean? get rid of module-init-tools-allconf.patch ??

Comment 2 Bill Nottingham 2006-01-24 18:57:19 UTC

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.