From owner-freebsd-questions@FreeBSD.ORG Fri Apr 9 02:56:07 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6C77C16A4CE for ; Fri, 9 Apr 2004 02:56:07 -0700 (PDT) Received: from osiris.ipform.ru (osiris.itlegion.ru [212.248.52.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4861643D58 for ; Fri, 9 Apr 2004 02:56:06 -0700 (PDT) (envelope-from matrix@itlegion.ru) Received: from artem (artem.office.ipform.ru [192.168.0.12]) by osiris.ipform.ru (8.12.6/8.12.6) with ESMTP id i399u3Xi061004; Fri, 9 Apr 2004 13:56:04 +0400 (MSD) (envelope-from matrix@itlegion.ru) X-AntiVirus: Checked by Dr.Web (http://www.drweb.net) Message-ID: <018c01c41e18$684383c0$0c00a8c0@artem> From: "Artem Koutchine" To: "Joshua Lokken" References: <20040407171128.GA74509@xor.obsecurity.org><001301c41d6e$c701d290$0c00a8c0@artem> <20040408202738.GA9742@voyager.swabbies.org> Date: Fri, 9 Apr 2004 13:30:53 +0400 Organization: IT Legion MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 cc: freebsd-questions@freebsd.org Subject: Re: Install world fails, computer almost unusable X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Apr 2004 09:56:07 -0000 >From: "Joshua Lokken" > * Artem Koutchine [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