From owner-freebsd-isp Tue Oct 20 08:20:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25254 for freebsd-isp-outgoing; Tue, 20 Oct 1998 08:20:44 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA25249 for ; Tue, 20 Oct 1998 08:20:42 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.9.1a/8.9.1) with ESMTP id QAA00792; Tue, 20 Oct 1998 16:20:12 +0100 (BST) Message-ID: <362CA9E4.57ABD3C0@tdx.co.uk> Date: Tue, 20 Oct 1998 16:19:00 +0100 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.5b2 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Paul Stewart CC: freebsd-isp@FreeBSD.ORG Subject: Re: 3.0 Upgrade Question References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Paul Stewart wrote: > > What about running the upgrade feature in sysinstall?? This would upgrade > the entire box correct? > > OR, is it wise to install whatever version we want onto a new server and > then transfer over the user files etc. one by one...:) > > Paul Hmmm... I'm not sure Sysinstall's upgrade will handle 2.2.7 to 3.0... I've never used it though, I seem to remember getting as far as the 'impending doom' screens... When we install our boxes here we do them from clean, we have install logs for them that list the distributions that were put on, the ports that were added - and how the applications (e.g. apache etc.) were setup, so we're quite lucky... You might want to check in -current and the archives to see what issues surround going from 2.2.7 to 3.0... A seperate box might be the 'ideal' way to go if you have the spare boxes, and always remember to back the system up Kp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message