From owner-freebsd-current@FreeBSD.ORG Thu May 18 04:41:49 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 16DA216A45E for ; Thu, 18 May 2006 04:41:49 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.FreeBSD.org (Postfix) with SMTP id 80D6B43D48 for ; Thu, 18 May 2006 04:41:48 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 7672 invoked by uid 399); 18 May 2006 04:41:48 -0000 Received: from localhost (HELO ?192.168.0.3?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 18 May 2006 04:41:48 -0000 Message-ID: <446BFB09.2050409@FreeBSD.org> Date: Wed, 17 May 2006 21:41:45 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5.0.2 (X11/20060507) MIME-Version: 1.0 To: "Mars G. Miro" References: <28edec3c0605171638t6398b1a8u6c63a2db9b12d6e5@mail.gmail.com> In-Reply-To: <28edec3c0605171638t6398b1a8u6c63a2db9b12d6e5@mail.gmail.com> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Thu, 18 May 2006 11:38:56 +0000 Cc: freebsd-current@freebsd.org, "Alexander I. Mogilny" Subject: Re: update to RELENG_6 fails X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: FreeBSD Stable List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 May 2006 04:41:54 -0000 Mars G. Miro wrote: > For the record, I've successfully updated a 5.4X to 6.1R w/o a hitch. > I don't think you need to go to 5-stable if you want 6.X. Most apps > will even still work and dont need to be recompiled. As happy as I am to hear that, if you'd read the section in UPDATING that I was referring to, you'd have seen: When upgrading from one major version to another it is generally best to upgrade to the latest code in the currently installed branch first, then do an upgrade to the new branch. This is the best-tested upgrade path, and has the highest probability of being successful. Please try this approach before reporting problems with a major version upgrade. Which clearly applies to the situation at hand. Please move this conversation to freebsd-stable. hope this helps, Doug -- This .signature sanitized for your protection