From owner-freebsd-stable@FreeBSD.ORG  Fri Dec 12 15:30:14 2014
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 5000EFDD
 for <freebsd-stable@freebsd.org>; Fri, 12 Dec 2014 15:30:14 +0000 (UTC)
Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.126.120])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "gromit.dlib.vt.edu",
 Issuer "Chumby Certificate Authority" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 2496B894
 for <freebsd-stable@freebsd.org>; Fri, 12 Dec 2014 15:30:13 +0000 (UTC)
Received: from macbook.chumby.lan (c-71-63-94-21.hsd1.va.comcast.net
 [71.63.94.21])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by gromit.dlib.vt.edu (Postfix) with ESMTPSA id 87975119;
 Fri, 12 Dec 2014 10:23:04 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: wrong patchlevel after freebsd-update install?
From: Paul Mather <paul@gromit.dlib.vt.edu>
In-Reply-To: <201412120930.sBC9UUEF041702@mech-as221.men.bris.ac.uk>
Date: Fri, 12 Dec 2014 10:23:03 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <7B7C7B31-B89F-4770-8DA1-CE7D0BD513EB@gromit.dlib.vt.edu>
References: <201412120930.sBC9UUEF041702@mech-as221.men.bris.ac.uk>
To: mexas@bris.ac.uk
X-Mailer: Apple Mail (2.1878.6)
Cc: freebsd-stable@freebsd.org
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Dec 2014 15:30:14 -0000

On Dec 12, 2014, at 4:30 AM, Anton Shterenlikht <mexas@bris.ac.uk> =
wrote:

> On 10.0-RELEASE-p12 amd64 I updated to p13 as:
>=20
> freebsd-update fetch
> freebsd-update install
> reboot
>=20
> However, uname still shows the old patchlevel:
>=20
> # uname -a
> FreeBSD 001cc0f01814.anet.bris.ac.uk 10.0-RELEASE-p12 FreeBSD =
10.0-RELEASE-p12 #0: Tue Nov  4 05:07:17 UTC 2014     =
root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64
> #
>=20
> But freebsd-update fetch suggests I'm already at p13:
>=20
> # freebsd-update fetch
> Looking up update.FreeBSD.org mirrors... 5 mirrors found.
> Fetching metadata signature for 10.0-RELEASE from =
update5.freebsd.org... done.
> Fetching metadata index... done.
> Inspecting system... done.
> Preparing to download files... done.
>=20
> No updates needed to update system to 10.0-RELEASE-p13.
> #
>=20
> So has the update p12 -> p13 succeeded?

What does "freebsd-version" report?  If it returns 10.0-RELEASE-p13 then =
your freebsd-update succeeded.

> Please clarify

It's my understanding that uname only gets updated when freebsd-update =
updates the kernel.  I think that's why freebsd-version was introduced.

>=20
> Thanks
>=20
> Anton

Cheers,

Paul.