Bug 88296 - trigger script incorrectly edits modules.conf
trigger script incorrectly edits modules.conf
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Arjan van de Ven
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2003-04-08 13:24 EDT by Stew Smith
Modified: 2005-10-31 17:00 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-30 11:40:46 EDT
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 Stew Smith 2003-04-08 13:24:50 EDT
Description of problem:
kernel-2.4.spec contains a trigger script which will basically always edit

Version-Release number of selected component (if applicable):

How reproducible:
install kernel rpms built from the above source rpm

Actual results:
the trigger is run everytime, so you get multiple "options i810 xfreeversion=41"
entries in modules.conf

Expected results:
one entry of "options i810 xfreeversion=41" in modules.conf.

Additional info:

These (there are three) trigger scripts are the culprit:

%triggerin smp -- XFree86 < 4.2
-cat /etc/modules.conf 2>/dev/null | grep -v xfreeversion > /dev/null && ( echo
"options i810 xfreeversion=41" >> /etc/modules.conf ) || :

Here is the change I made (remove -v from grep, make the echo an || condition:

%triggerin smp -- XFree86 < 4.2
cat /etc/modules.conf 2>/dev/null | grep xfreeversion > /dev/null || ( echo
"options i810 xfreeversion=41" >> /etc/modules.conf ) || :

That way, it should only run if the string "xfreeversion" does not appear in the
Comment 1 Bugzilla owner 2004-09-30 11:40:46 EDT
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/

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