From owner-freebsd-stable Thu Jul 13 1:55:55 2000 Delivered-To: freebsd-stable@freebsd.org Received: from zipcode.corp.home.net (zipcode.corp.home.net [24.0.26.58]) by hub.freebsd.org (Postfix) with ESMTP id 0E6A237B7C6 for ; Thu, 13 Jul 2000 01:55:51 -0700 (PDT) (envelope-from manek@ecst.csuchico.edu) Received: from after (dialup69.home.net [24.0.25.69]) by zipcode.corp.home.net (8.9.3/8.9.3) with SMTP id BAA28933; Thu, 13 Jul 2000 01:55:41 -0700 (PDT) From: "Sameer R. Manek" To: "Andreas Klemm" , Subject: RE: how to update from FreeBSD 2.2.8 to RELENG_4 Date: Thu, 13 Jul 2000 01:55:50 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: <20000713091845.A2997@titan.klemm.gtn.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Andreas Klemm > I have an old FreeBSD 2.2.8 installation at a customers site. > Does somebody have any experience in upgrading such a machine to 4.0 ? > > Or is there a document available where these steps are documented > over the different FreeBSD releases ??? > > I'd do the following and pray ... > Given that you plan to do 5 make worlds, on a pII 400, that's about 2.5-3 hours each. So that's a good 10-15 hours of just compiling? Assuming it works flawlessly. You should ask yourself is such an upgrade worth the man hours? Not to mention, this has to be a production system. You should have a development system to test the planned upgrade, or at the very least a server designed as a replacement, for the current production system. Really a fresh install of 4.0, or soon 4.1 would be your best bet. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message