This is one for P (Peter?) Robinson I think
You think wrong.
I have just done fedup-cli on my Raspberry Pi which worked fine but on re-booting there is no
boot menu from grub - it simply boots, as before, into FC17 with graphical login invitation.
That is because the RPi doesn't run grub, in fact none of the ARM platforms currently support grub and as a result fedup isn't currently supported.
I looked at /boot and see that there is an executable file vmlinuz-fedup there, should
I just execute it and hope for the best? I recently did the same operation for fc17 -> fc18 on
my 686 machine which went without a hitch - perhaps because it always gives a
(brief glimpse of!) a grub boot menu.
Generally I don't execute random binaries and hope for the best.... We currently don't really support upgrades on ARM. I've used "yum upgrade" without issues in the past but on hardfp platforms there was a change in the core linker soname path so it's not always reliable. That said we currently don't support fedup as it has a hard requirement on the bootloader which doesn't currently work on ARM. I find in most cases it's easiest to get a new SD card and set it up with the new release then pull the old one out and plug the new one in. It has easy roll back and other advantages.
Ultimately though the upgradability and dealing with new RPi kernels is a question for Seneca to answer as the RPi is their project
Peter
_______________________________________________ arm mailing list arm@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/arm
