From owner-freebsd-questions Thu Apr 27 14:20:44 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mail-1.sjc.telocity.net (mail-1.sjc.telocity.net [216.227.56.41]) by hub.freebsd.org (Postfix) with ESMTP id 7FE5037B6FD for ; Thu, 27 Apr 2000 14:20:41 -0700 (PDT) (envelope-from otter@otter.cc) Received: from otter.cc (dsl-216-227-91-85.telocity.com [216.227.91.85]) by mail-1.sjc.telocity.net (8.9.3/8.9.3) with ESMTP id OAA28290; Thu, 27 Apr 2000 14:19:31 -0700 (PDT) Message-ID: <3908AF63.862AAAF5@otter.cc> Date: Thu, 27 Apr 2000 17:21:39 -0400 From: Otter X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 5.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: marcus@redcentre.com Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Upgrading FreeBSD 2.2.7 to 4.0 References: <200004271422.AAA19422@mail01.redcentre.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG marcus@redcentre.com wrote: > > Hi, > > I'm just after a bit of advice regarding upgrading a production > server from 2.2.7 to 4.0 (?). Is there a safe way to do this or > would it be wiser to configure a new server and transfer the accounts > across? > > Marcus > Remembering the upgrade process from 2.x to 3.x and 3.x to 4.0, I'd recommend doing a new install. Consider too that 2.x to 3.x required an a.out->elf conversion. Since you have production machines, you might want to do a trial run on an unused box just to make sure the upgrade/change goes smoothly before you make it go live. (IMHO) -Otter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message