![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
swarm32I went down the gnarly road of crossgrading from i686 to x86_64 fedora one of my VMs because it was supposedly possible. While it is definitely doable with enough patience, it's time consuming and needs to be done in the right sequence. I figured I'd at least write down the cliff's notes
1) Backup/snapshot your working system
2) Upgrade from a 32-bit kernel to a 64-bit kernel, reboot and confirm everything works
3) et selinux to permissive
4) Make sure you download or statically compile a 64-bit version of RPM
5) be prepared to use rpm -qa , rpm -e , rpm -e --nodeps, rpm -ivh a lot, dnf download
6) when you get to the point of migrating RPM and DNF, be prepared for fixing a lot of python stuff too
7) make sure plymouth is x86_64
8) set selinux to permissive
9) you will have to power cycle/hard reset the machine to start the final upgrade, be prepared for if this fails
Other notes:
- it's actually helpful to have an X session with something like XFCE terminal and firefox running if you can
- Be prepared to download and manually install/reinstall a lot of packages
- expect sudo to either break or get weird, use sudo -i or just plain su
- at a certain point, authorizing not root users will break and you will not be able to establish a new ssh session if using ssh
- Post migration things will be wonky and may take some additional time to sort out
1) Backup/snapshot your working system
2) Upgrade from a 32-bit kernel to a 64-bit kernel, reboot and confirm everything works
3) et selinux to permissive
4) Make sure you download or statically compile a 64-bit version of RPM
5) be prepared to use rpm -qa , rpm -e , rpm -e --nodeps, rpm -ivh a lot, dnf download
6) when you get to the point of migrating RPM and DNF, be prepared for fixing a lot of python stuff too
7) make sure plymouth is x86_64
8) set selinux to permissive
9) you will have to power cycle/hard reset the machine to start the final upgrade, be prepared for if this fails
Other notes:
- it's actually helpful to have an X session with something like XFCE terminal and firefox running if you can
- Be prepared to download and manually install/reinstall a lot of packages
- expect sudo to either break or get weird, use sudo -i or just plain su
- at a certain point, authorizing not root users will break and you will not be able to establish a new ssh session if using ssh
- Post migration things will be wonky and may take some additional time to sort out
