Bug 121737 - anaconda leaves modprobe.conf.anacbak behind, no modprobe.conf
anaconda leaves modprobe.conf.anacbak behind, no modprobe.conf
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
All Linux
medium Severity high
: ---
: ---
Assigned To: Jeremy Katz
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2004-04-26 18:41 EDT by Carlos Morgado
Modified: 2007-11-30 17:10 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-08-15 12:11:29 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 Carlos Morgado 2004-04-26 18:41:02 EDT
Fedora Core 2 Test 3 installer

Chose upgrade, the installer complained I didn't have enough space,
went  back, chose reboot on the "do you have all needed media" screen. 

The system didn't have modprobe.conf after the upgrade, anaconda needs
to restore the file when the user aborts.
Comment 1 Michael Koziarski 2004-05-01 00:30:14 EDT
My upgrade completed successfully, but my modprobe.conf file was empty.

The .anacbak file was still there.
Comment 2 Michael Koziarski 2004-05-01 00:32:23 EDT
I copied the .anacbak file back into place and it worked fine. So the
problem is broader than just backing out of an upgrade.
Comment 3 Jeremy Katz 2004-05-06 21:09:29 EDT
Fixed in CVS

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