We now write out a new /etc/fstab on upgrade. This has the unfortunate
side effect of any entries anaconda doesn't understand getting dropped.
After staring at it off and on all day, I can't see any way to fix this
that doesn't involve lots of fairly invasive changes so instead how
about if we just backup the fstab before writing out a new one?
I'm open to other suggestions.
- Chris
diff --git a/packages.py b/packages.py
index 371e10e..c141c92 100644
--- a/packages.py
+++ b/packages.py
@@ -101,6 +101,7 @@ def doMigrateFilesystems(anaconda):
# if we're upgrading, we may need to do lvm device node hackery
anaconda.id.fsset.makeLVMNodes(anaconda.rootPath, trylvm1 = 1)
# and we should write out a new fstab with the migrated fstype
+ shutil.copyfile("%s/etc/fstab" % anaconda.rootPath, "%s/etc/fstab.anaconda" % anaconda.rootPath)
anaconda.id.fsset.write(anaconda.rootPath)
# and make sure /dev is mounted so we can read the bootloader
bindMountDevDirectory(anaconda.rootPath)
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
