From owner-freebsd-questions@FreeBSD.ORG Thu Jan 12 10:00:57 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 DC34616A420 for ; Thu, 12 Jan 2006 10:00:57 +0000 (GMT) (envelope-from crispy.beef@ntlworld.com) Received: from mta07-winn.ispmail.ntl.com (mta07-winn.ispmail.ntl.com [81.103.221.47]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7168843D55 for ; Thu, 12 Jan 2006 10:00:55 +0000 (GMT) (envelope-from crispy.beef@ntlworld.com) Received: from aamta11-winn.ispmail.ntl.com ([81.103.221.35]) by mta07-winn.ispmail.ntl.com with ESMTP id <20060112100052.FAZG15999.mta07-winn.ispmail.ntl.com@aamta11-winn.ispmail.ntl.com>; Thu, 12 Jan 2006 10:00:52 +0000 Received: from [192.168.0.2] (really [82.12.81.129]) by aamta11-winn.ispmail.ntl.com with ESMTP id <20060112100052.JQLF19063.aamta11-winn.ispmail.ntl.com@[192.168.0.2]>; Thu, 12 Jan 2006 10:00:52 +0000 Message-ID: <43C628D2.3070500@ntlworld.com> Date: Thu, 12 Jan 2006 10:00:50 +0000 From: Crispy Beef User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051017) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kent Stewart References: <43C540A1.7060805@ntlworld.com> <200601111059.21012.kstewart@owt.com> In-Reply-To: <200601111059.21012.kstewart@owt.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: 4.6-RELEASE to 6.0-RELEASE... X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jan 2006 10:00:58 -0000 > There have been major changes in processes such as threads. You also > have to boot the 5.3 update in single user mode to have a kernel that > accepts the new arrangement and then install the userland. Before 5.1 > or 5.2 it didn't matter much but there was an fs change that you update > in single user mode or boot the fix disc to finish the botched update. > > You also have the problem that probably none of your ports from 4.x will > work at 6.0. This could take quite a bit of time to upgrade. One advantage is that I didn't really bother with the ports on that server, I rolled my own apps as I wasn't totally up with the ports system at the time, just seemed easier until I go the hang of it, so I probably would go for a fresh install of ports and get the latest versions of software installed that way. The server is used for web hosting so I only really need to save out a few config files for virtual hosts etc. and the email directories. It's sounding as though it might be easier just to have an hour or two of downtime late one night and do a fresh install...