From owner-freebsd-questions@FreeBSD.ORG Wed Apr 24 19:52:25 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4786A9F5 for ; Wed, 24 Apr 2013 19:52:25 +0000 (UTC) (envelope-from feld@feld.me) Received: from new1-smtp.messagingengine.com (new1-smtp.messagingengine.com [66.111.4.221]) by mx1.freebsd.org (Postfix) with ESMTP id 1CAC91B14 for ; Wed, 24 Apr 2013 19:52:24 +0000 (UTC) Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id BECC51C26; Wed, 24 Apr 2013 15:52:18 -0400 (EDT) Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute1.internal (MEProxy); Wed, 24 Apr 2013 15:52:18 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=feld.me; h= content-type:to:subject:references:date:mime-version :content-transfer-encoding:from:message-id:in-reply-to; s= mesmtp; bh=DsPm58mn/AVrnkJNbUbcqVTYuwY=; b=C5HwRGjpStBanw10yhLv0 Fftoq+rqABqR6uWro5moj1mhtVbeSSP4TsLaKHcXoISuGQl+pIm6XHBGtA67dJOg gKIS8yJTpmjsXah+CnebEaoATSEgWbfUJ3FU7mla/iBY3J9bpyaVH36YEM1mfYg6 pNa6JJXcMSYxxOPlvjnwjA= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-type:to:subject:references:date :mime-version:content-transfer-encoding:from:message-id :in-reply-to; s=smtpout; bh=DsPm58mn/AVrnkJNbUbcqVTYuwY=; b=n0Vl 0XcwZvBL9+bAjvlWjle9lwNHkqhB3IxWP8xGWLAcd6Qo3THDfINMxBj0QjXAjZez 9ID2X8gMSJ+tXkGuMMOkvbhtIVe3bgzW+ysC0MunfPZ+fO+pJTTJQb8JJnoG4sfE fu+bzEFF0IqBAgIhkScacrOjm+MYOGGm2nYYouA= X-Sasl-enc: dkUIWSbCyO3KpacXLLvHT5Jy/sIxaadv4fRj1PMgKGcN 1366833138 Received: from tech304.office.supranet.net (unknown [66.170.8.18]) by mail.messagingengine.com (Postfix) with ESMTPA id 4BE07C8000D; Wed, 24 Apr 2013 15:52:18 -0400 (EDT) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes To: freebsd-questions@freebsd.org, "Steve O'Hara-Smith" Subject: Re: FreeBSD-update? References: <20130424203430.e127c9a56fe88f968eed6ad5@sohara.org> Date: Wed, 24 Apr 2013 14:52:17 -0500 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: "Mark Felder" Message-ID: In-Reply-To: <20130424203430.e127c9a56fe88f968eed6ad5@sohara.org> User-Agent: Opera Mail/12.14 (FreeBSD) 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: Wed, 24 Apr 2013 19:52:25 -0000 On Wed, 24 Apr 2013 14:34:30 -0500, Steve O'Hara-Smith wrote: > You have updated to 9.1-RELEASE-p2 - but since there have been no > kernel changes since 9.1-RELEASE the kernel version message hasn't > changed. > This could very reasonably be regarded as bug in the update/version > reporting process but I wouldn't hold my breath for a fix, as things > stand > the version reported only changes when the kernel is updated, or if you > recompile it after the update. It would be nice if the version of the OS itself was stored in something like /etc/freebsd-version so you know what the version of the OS as a whole is. I'd even accept some sort of output by freebsd-update. It just seems silly that there's no other way -- kern.osrelease is just the base release and kern.version is the same thing that uname -a outputs. It's hard to pick this up and monitor it accurately.