On 08/15/2013 05:37 PM, Kevin Fenzi wrote:
On Thu, 15 Aug 2013 17:32:27 +0200
Reindl Harald <h.reindl@xxxxxxxxxxxxx> wrote:
what does *not* matter in case of "yum distro-sync" because it does
also downgrades and if fedup has a problem with it the people who say
yum is not officially supported (while no support in any case exists)
should ask theirself who in the world needs fedup instead keep
fous on *one* well working tool
besides the fact that yum-upgrades are most times better
yum is used and tested every single day from thousands
of users while "fedup" no normal user touchs half a year
You misunderstand how fedup works.
It gathers up the packages you will need to do the upgrade,
... and stores them in /var/cache/yum/...
If you don't have a sufficiently large /var/cache, such a download
easily exceeds the amount of available diskspace and fails.
then
reboots into a very minimal env and uses yum to do the upgrade.
The difference is that since it's in a minimal env, you don't have
possible problems with running processes, and you can make changes that
would otherwise not be possible to a running system.
Well, may-be I am wrong, but this does not match with what I experienced
during the ca. 8 fedup driven updates, I've done.
If you use and like yum dist upgrades on running systems, thats great.
However, fedup is more safe since it's not happening on a running
system.
If you say so ... I saw f17->f18 hang during the "fedup reboot" and not
come up at all, and had 2 f18->f19 systems suffering from corrupt rpmdbs.
All f18->f19 systems had f18 kernels after fedup had completed, due to
the kernel-versions.
Ralf
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
