Bug 52999 – /sbin/modules-update and /sbin/generate-modprobe.conf don't work together properly (again)

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description monkey 2004-06-04 11:11:41 UTC]

/sbin/modules-update calls /sbin/generate-modprobe.conf with options that the later does not deal with.  Currently sys-apps/baselayout-1.9.4 and sys-apps/module-init-tools-3.0 are stable.  The modules-update in baselayout calls the generate-modprobe.conf in module-init-tools with a --assume-kernel option, but that particular option was not added to generate-modprobe.conf until module-init-tools-3.0-r2.  The tell-tale result is that modules-update will leave a file called '--assume-kernel<foo>' in the CWD when it is used, that file of course should have gone to /etc/modprobe.conf.

Reproducible: Always
Steps to Reproduce:
1. install sys-apps/baselayout-1.9.4 and sys-apps/module-init-tools-3.0
2. run modules-update
3. /etc/modprobe* not correctly updated and '--assume-kernel<foo>' file in CWD.



Expected Results:  
Correctly update /etc/modprobe.conf

Emerging module-init-tools-3.0-r2 fixes this problem as
/sbin/generate-modprobe.conf has been updated.

[Comment 1 Tuan Van (RETIRED) 2004-06-04 11:41:48 UTC]

your bug is a dup of bug #52886 with more info :)

[Comment 2 Seemant Kulleen (RETIRED) 2004-06-04 11:57:23 UTC]

*** Bug 52886 has been marked as a duplicate of this bug. ***

[Comment 3 Felix Braun 2004-06-04 13:22:25 UTC]

If module-init-tools-3.0-r2 fixes this, eitherthat package has to be maked stable or baselayout-1.9 needs to go back into unstable. Right now, stable people are getting upgraded to baselayout 1.9 without working modules :-(

[Comment 4 Aron Griffis (RETIRED) 2004-06-04 16:05:59 UTC]

Thanks.  module-init-tools-3.0-r2 is now marked stable and baselayout has been bumped to 1.9.4-r1 to push out the change.

[Comment 5 Aron Griffis (RETIRED) 2004-06-04 16:06:27 UTC]

...and baselayout-1.9.4-r1 DEPENDs on >=module-init-tools-3.0-r2