From owner-freebsd-questions@FreeBSD.ORG Sat Jul 19 09:57:57 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 08EB0740 for ; Sat, 19 Jul 2014 09:57:57 +0000 (UTC) Received: from zoom.lafn.org (zoom.lafn.org [108.92.93.123]) by mx1.freebsd.org (Postfix) with ESMTP id 80C092BFC for ; Sat, 19 Jul 2014 09:57:56 +0000 (UTC) Received: from [10.0.1.2] (static-71-177-216-148.lsanca.fios.verizon.net [71.177.216.148]) (authenticated bits=0) by zoom.lafn.org (8.14.7/8.14.7) with ESMTP id s6J9vmpK077208 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 19 Jul 2014 02:57:53 -0700 (PDT) (envelope-from bc979@lafn.org) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: Freebsd-update to 9.3 from 9.2 From: Doug Hardie In-Reply-To: Date: Sat, 19 Jul 2014 02:57:47 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <066C2341-F26F-4817-B681-97119FB7EB7C@lafn.org> References: <4CA0146F-BD4E-4613-9050-DB0C1FDB7EA4@lafn.org> <53C8B7A2.1060504@my.hennepintech.edu> <494D0D9E-ED60-4187-ABCF-8E18CDEAB911@lafn.org> <53C8E2A7.6000000@my.hennepintech.edu> <7154054C-47D0-454C-8601-3F17095476EC@lafn.org> To: Warren Block X-Mailer: Apple Mail (2.1510) X-Virus-Scanned: clamav-milter 0.98 at zoom.lafn.org X-Virus-Status: Clean Cc: Andrew Berg , freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Jul 2014 09:57:57 -0000 On 18 July 2014, at 16:01, Warren Block wrote: > On Fri, 18 Jul 2014, Doug Hardie wrote: >=20 >>=20 >> On 18 July 2014, at 14:37, Doug Hardie wrote: >>=20 >>>=20 >>> On 18 July 2014, at 02:02, Andrew Berg = wrote: >>>=20 >>>> On 2014.07.18 03:40, Doug Hardie wrote: >>>>> This gets even more interesting. Unfortunately I do need to = makeworld as sendmail needs SMTP-AUTH and that requires a rebuild. >>>> Then there is no reason to use freebsd-update at at all. >>>>=20 >>>>> That is the date/time when I did the buildworld/buildkernel. = kern.osrelease and kern.version show the same thing. So, now I don't = know if I am running 9.2, 9.3, or a 9.2 kernel and 9.3 world. There = must be some way to tell. >>>> The best thing to do since you need to build world and kernel is to = just use >>>> svn and do all updates via source. freebsd-update does nothing for = you. Grab a >>>> completely new copy of the 9.3 source with svn and then build and = install it. >>>> I'd recommend rolling back to whatever you had before the update = before doing so. >>>>=20 >>>> freebsd-version may have been backported to 9 with 9.3. If so, you = can use it. >>>> Also, 9.2 kernel with 9.3 world is not likely to be functional = since kernels >>>> have no guarantee of forward-compatibility (9.3 kernel and 9.2 = world would >>>> probably be fine, though). >>>>=20 >>>=20 >>>=20 >>> svn doesn't work either: >>>=20 >>> svn checkout https://svn0.us-west.FreeBSD.org/base/release/9.3.0 = /usr/src >>>=20 >>> The latest version of UPDATING I get is from 20130705. The web = repository shows the latest entry as 20140716. I have used FreeBSD = since 2.5.4 and it used to be easy to manage. Now its virtually = impossible. Complete reinstalls on production systems are just not = viable. We need a working way to upgrade. I haven't found it yet. >>=20 >>=20 >> I finally deleted all of /usr/src and /usr/obj and ran the above svn = checkout again. This time the UPDATING file shows the 20140716 entry. I = have started building the system again. We will see what we get this = time. Its fascinating to see that in order to upgrade you have to = delete everything and then reload it all across the internet multiple = times? >=20 > It's not necessary to delete the source every time. But /usr/src = should be empty before the initial svn checkout, or there will be files = in there that are unmanaged and can cause problems. The Subversion = instructions mention this. (Or at least some of them do, we have a fair = amount of similar sections in different chapters and sections that need = to be combined.) >=20 I didn't find any mention of that in the manual.