From owner-freebsd-stable@FreeBSD.ORG Fri Dec 12 09:41:01 2014 Return-Path: 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 E35C7DAF for ; Fri, 12 Dec 2014 09:41:01 +0000 (UTC) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A4DFCCF1 for ; Fri, 12 Dec 2014 09:41:01 +0000 (UTC) Received: from pi by home.opsec.eu with local (Exim 4.82 (FreeBSD)) (envelope-from ) id 1XzMiZ-000MQ0-BH; Fri, 12 Dec 2014 10:40:59 +0100 Date: Fri, 12 Dec 2014 10:40:59 +0100 From: Kurt Jaeger To: Anton Shterenlikht Subject: Re: wrong patchlevel after freebsd-update install? Message-ID: <20141212094059.GX44537@home.opsec.eu> References: <201412120930.sBC9UUEF041702@mech-as221.men.bris.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201412120930.sBC9UUEF041702@mech-as221.men.bris.ac.uk> 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2014 09:41:02 -0000 Hi! > On 10.0-RELEASE-p12 amd64 I updated to p13 as: > > freebsd-update fetch > freebsd-update install > reboot Please add another freebsd-update install for the user-space. > But freebsd-update fetch suggests I'm already at p13: Yes. > So has the update p12 -> p13 succeded? I think, yes. Use freebsd-version to compare. Some updates only change userspace, not kernels and uname stays on the old patch level. Yes, annoying, not trivial to fix. -- pi@opsec.eu +49 171 3101372 6 years to go !