From owner-freebsd-questions@FreeBSD.ORG Thu Oct 10 17:07:21 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 8C5DCF6D for ; Thu, 10 Oct 2013 17:07:21 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5FFBB2BF2 for ; Thu, 10 Oct 2013 17:07:21 +0000 (UTC) Received: from compute6.internal (compute6.nyi.mail.srv.osa [10.202.2.46]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 4CD1C215E2 for ; Thu, 10 Oct 2013 13:07:20 -0400 (EDT) Received: from web3 ([10.202.2.213]) by compute6.internal (MEProxy); Thu, 10 Oct 2013 13:07:20 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:mime-version :content-transfer-encoding:content-type:subject:date:in-reply-to :references; s=smtpout; bh=x/f4+lsTeOhn7vlmwDIWjyUi0K8=; b=P27vs wr+yQLQcibxVR6zwtSFFjKjq9Ep3Zrm+JRO/q2nlrm7UgETM2FuPSqB3oII1QuBh +Jq5jhthhewru8hLErtj7KzIj6DerYlHG+H5zDMgCI3iNi+wAIxmKAlAIHEtjC7t w7hTNFnFJrzKyP9NIgU+C9/g2/e9e27g1tFsO4= Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99) id 2A552117449; Thu, 10 Oct 2013 13:07:20 -0400 (EDT) Message-Id: <1381424840.11040.32473177.511919E0@webmail.messagingengine.com> X-Sasl-Enc: OPIKaXIQ0B1YHpXfoiBKQGtBTWAfzp6LZJCld9Yw7KNv 1381424840 From: Mark Felder To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-ce174988 Subject: Re: freebsd-update upgrade -r 7.4-RELEASE-p12 Date: Thu, 10 Oct 2013 12:07:20 -0500 In-Reply-To: <20131009153605.3c6524c8a1ce44965a54ae6a@yahoo.es> References: <201310090332.r993We9X098245@chilled.skew.org> <20131009153605.3c6524c8a1ce44965a54ae6a@yahoo.es> X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Oct 2013 17:07:21 -0000 On Wed, Oct 9, 2013, at 8:36, Eduardo Morras wrote: > On Tue, 8 Oct 2013 21:32:39 -0600 (MDT) > Mike Brown wrote: > > > alexus wrote: > > > ok, I just did fetch & install and got bumped from p5 to p9 > > > > > > # uname -a > > > FreeBSD XX.XXXXX.org 7.4-RELEASE-p9 FreeBSD 7.4-RELEASE-p9 #0: Mon Jun 11 > > > 19:47:58 UTC 2012 > > > root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC > > > amd64 > > > # > > > > > > can I take it all the way to -p12? > > > > -p10 through -p12 probably didn't involve any kernel changes. Bumping the > > reported patchlevel isn't considered important enough to warrant building a > > new kernel. > > That there's no kernel changes doesn't mean that uname -a info is not > updated. You are incorrect. The output of uname -a is taken from the kernel and cannot be updated without installing a new kernel. The good news is that FreeBSD 10 will ship with a new utility called freebsd-version which will provide a better way of identifying if your system is up to date. >From the commit message: Introduce the /libexec/freebsd-version script, which is intended to be used by auditing tools to determine the userland patch level when it differs from what `uname -r` reports. This can happen when the system is kept up-to-date using freebsd-update and the last SA did not touch the kernel, or when a new kernel has been installed but the system has not yet rebooted. http://svnweb.freebsd.org/base/head/bin/freebsd-version/ By the way, it will be /bin/freebsd-version as it has been relocated since the import into head.