> On Tue, 9 Nov 2004, Kenn Humborg wrote:
>> > I'm not 100% sure about this, but I'd say that the transaction
> > handling in the RPM database should be able to survive a crash in
> > the middle of an upgrade.
>> I've had this happen to me, and yes it can survive. however..
>> > Either a package is installed, not installed or partially
> > installed. If the post-install scripts are sane, it should always
> > be safe to completely re-install an already-installed or
> > partially-installed package. So restarting the upgrade should be
> > OK.
>> The problem is though you'll be left with a half-upgrade, some
> packages will have been upgraded, some will still be the old. If
> you're lucky, it needs no more than apt-get dist-upgrade, if you're
> unlucky it can take major futzing.
>> I dont see how an anaconda based upgrade could avoid this problem
You missed my point. I'm talking about the question of "what happens
if the upgrade is interrupted". I'm saying that the situation
should always be recoverable by running the upgrade again (yum,
apt, anaconda, whatever). I never said that the half-upgraded
system would be bootable or functional, so getting to the point
of using yum or apt to fix it up could be tricky :-)
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!