Why quaid put the needs_love tag on the page
- Needs to be rewritten to follow command examples and technical markup usage from:
- Renamed to be descriptive, natural name as per Help:Wiki structure
- Added to Category:Documentation and the ever cool new Category:How to
If a PreUpgrade stand alone page is needed, that can be created separately with feature content, then have this page linked. However, most features use their Features/PreUpgrade-style page as the main reference point, so there is no reason to create a PreUpgrade page.
quaid 04:55, 24 November 2008 (UTC)
Another method to free space: Convert /boot to ext2
If /boot is an ext3 filesystem it's possible to free about 4 MB by converting it to an ext2 filesystem. It goes something like this:
umount /boot tune2fs -O ^has_journal /dev/sda1 - where /dev/sda1 is the /boot partition $EDITOR /etc/fstab - change ext3 to ext2 for /boot mount /boot
-- Abo
Troubleshooting - "characters: ordinal not in range(128)"
I would suggested to add one more item into troubleshooting section. When using multibyte environment with local language, PreUpgrade can end with the message like this:
Traceback (most recent call last):
File "/usr/share/preupgrade/preupgrade-cli.py", line 329, in <module>
pu.main(release)
File "/usr/share/preupgrade/preupgrade-cli.py", line 267, in main
if not self.userconfirm():
File "/usr/share/yum-cli/output.py", line 687, in userconfirm
choice = raw_input(_('Is this ok [y/N]: '))
UnicodeEncodeError: 'ascii' codec can't encode characters in position 4-5: ordinal not in range(128)
Solution is to prepend LANG=C to the preupgrade-cli:
LANG=C;preupgrade-cli "Fedora 15 (Lovelock)"
This bug is still present in the actual repo version of yum (3.2.28-6.fc14) or PreUpgrade (1.1.9-1.fc14). Regarding ticket is 635432.
I just tried using preupgrade as described here, and discovered a couple of errors.
- First: After downloading the install files, the upgrade did not install upon reboot. Using the instructions, I booted into the grub command line. The grub "kernel" and "initrd" commands show the paths "/boot/upgrade/...". That's wrong, the paths should just be "/upgrade/...".
- Next: The Advice "Upgrade to current release directly" did not work for me. Current release is 15, my installation is 12. The upgrade died with the message: "Your current installation cannot be upgraded. This is likely due to it being too old. Only the previous two release [sic] may be upgraded. To upgrade older releases you must first upgrade through all intermediate releases".
-- kjohnstn
Skipping intermediate versions
The current comment implies one can update from any fedora release. When I tried to update from f12 to f15, I got the following message in a dialog box...
"Your current installation cannot be upgraded. This is likely due to it being too old. Only the previous two release may be upgraded. To upgrade older releases you must first upgrade through all intermediate releases."
... and the choice to 'Exit Installer' or 'Continue'.
I suspect this is because fedora 12 is no longer supported.
The conditions under which one can update from an older release (or not) could be spelled out more clearly. I don't know what those are for certain, so I'll leave it to someone else to add that information.
What happens if I don't click the preupgrade Reboot button?
If I con't click the Reboot button in preupgrade:
- I hope and reasonably expect that the system will still reboot normally in the present system version.
- I fear that if I quit from preupgrade before clicking the button, the next time the system reboots, it will proceed to upgrade.
Daveyost 08:06, 26 February 2012 (UTC)