Bug 118738 - module settings not maintained during upgrade
module settings not maintained during upgrade
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Mike McLean
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2004-03-19 12:47 EST by Need Real Name
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-03-19 17:36:36 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 Need Real Name 2004-03-19 12:47:54 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1)

Description of problem:
I have a USB hard drive that was successfully working under RH9.  When
Iupgraded to FC1, I lost my modules.conf setting (and my human memory
that it hadto be modified).  I also found the settings in "make
xconfig" that related tothe device to be, many of them, set to "N". 
It has taken me two days to figure out what had to be changed and to
make the changes -- and I'm a techie.  Would it be possible for the
installer to be cognizant of the settings of a previous version and/or
devices that are plugged into the system when the install takes place?  

And how about devices that are plugged in after an install?  Would it
be possible to communicate to the OS what has been plugged in and to
automate the module selection and "make dep" process as well as
required modifications to modules.conf.  The idea is to enable the
casual user to attach USB and/or FireWire devices? 

Thanks for considering this.

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

How reproducible:

Steps to Reproduce:
1.  Upgrade an OS version (RH9 to FC1, for example) without formatting
hard drive.

Actual Results:  The external drive plugged into my USB port could not
be detected.

Expected Results:  The fact that the device plugged into my USB port
was detectable and working under RH9 led me to think that it should
have continued to be detectable and working after I upgraded to FC1.

Additional info:

I was only able to find documentation that enabled me to use this
device after a couple of days' search on the web.  However this is
resolved, even if no software changes are made, the means for enabling
the system to detect such devices should be in the documentation.
Comment 1 Jeremy Katz 2004-03-19 17:36:36 EST
If you install rather than upgrade, then we overwrite config files
with fresh ones.  There's no other way to do things and have any sort
of minimal sanity about the system.

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