Re: update mechanism for new releases

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Adam Williamson wrote:
On Wed, 2009-06-24 at 11:05 +0100, Peter Robinson wrote:
The problem with preupgrade is that it needs user interaction and a
lot of space. It downloads the distro update locally, reboots the
machine and then runs anaconda.

Well, as yum doesn't group transactions, yum upgrades also require a lot
of space (enough to store the entire set of upgrade packages, as they're
_all_ downloaded prior to the operation).

...if you just run 'yum upgrade' and not 'yum upgrade <list>'. I don't know that I've /ever/ done all-at-once, if only because of more risk of the transaction taking so long that something bad happens (e.g. power failure). F10 -> F11 was just especially bad due to all of KDE needing to be upgraded in order to upgrade yum (due to openssl deps).

The trick, as I've discovered, is not to reboot in between chunks ;-).

--
Matthew
Please do not quote my e-mail address unobfuscated in message bodies.
--
"Who wants to sing?" -- Orcs (Warcraft II)

--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux