fedup
fedup copied to clipboard
rhinstaller
Deprecated Fedora Upgrade tool
Where possible (LVM, btrfs, etc.) we should offer to do a filesystem snapshot before the upgrade, and automatically revert to the upgrade if anything goes wrong during the upgrade itself.
There are some problems that have to be fixed _before_ we reboot to start the upgrade; for example, replacing the `KEYTABLE`/`KEYMAP` boot argument with `vconsole.keymap` in Fedora 18. fedup should...
It would make a lot more sense if we didn't touch your bootloader config automatically. Instead it should work kind of like `git rebase --interactive`: ``` # fedup --network 21...
Basically, when the system crashes, we should probably display an error message and tell the user how boned they are, and let them choose between a shell and rebooting. More...
If you do something like `fedup --network 19`, and then decide, whoops, I want to go to 20, we'll still use the cached metadata from the Fedora 19 versions of...
If the ISO provided with `--iso` isn't on a mount that's listed in `/etc/fstab`, we won't be able to find it when we reboot. At the very least, we should...
If you have (e.g.) a NFS repo, its url will be `file:///...` and yum will consider those packages to be local, and thus we won't cache them in /var. So...
`cachedir` and `packagedir` are hardcoded to `/var/tmp/system-upgrade` and `/var/lib/system-upgrade`; if the user doesn't have space on /var (but has plenty of space in, say, `/home`) they can't upgrade their system....