Date: Fri, 9 Apr 2004 13:30:53 +0400 From: "Artem Koutchine" <matrix@itlegion.ru> To: "Joshua Lokken" <joshua@twobirds.us> Cc: freebsd-questions@freebsd.org Subject: Re: Install world fails, computer almost unusable Message-ID: <018c01c41e18$684383c0$0c00a8c0@artem> References: <hvsu02.reqtnt@webmail.triera.net><20040407171128.GA74509@xor.obsecurity.org><001301c41d6e$c701d290$0c00a8c0@artem> <20040408202738.GA9742@voyager.swabbies.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>From: "Joshua Lokken" <joshua@twobirds.us> > * Artem Koutchine <matrix@itlegion.ru> [2004-04-08 06:44]: > > IMHO the upgrade pricedure is unstable and wrong in either case. > > > > What do you think? > > I don't pretend to understand *all* of the reasoning behind the > recommended upgrade procedure. Since I began using FreeBSD, I have > performed somewhere around 50 system upgrades on various machines, most > of them 4.x, and have upgraded 5.1->5.2 on four machines. Of those > system upgrades, two have failed, or 'not worked.' One of them was due > to the fact that I didn't follow the recommended procedure (admittedly, > supplemented with list wisdom), the other, because I didn't follow the > recommended procedure. > > It just works. > Actually it failed only once for me since 1996. But! I alway fill shaky when upgrading a remote server and rebootting it. Never failed once but i CAN SEE a case when it will fail because some utility does not match kernel at the time of installation. The ideal upgrade procedure must allow fall back to the previous version. So, the ideal upgrade must install everything into a temporary storage space and after reboot, try to replace existing files with the new onces and if after that boot failes after the next reboot restore the originals while keeping log. I don't think it is as hard to implement as 5.2 locking :) Artem
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?018c01c41e18$684383c0$0c00a8c0>