From owner-freebsd-questions@FreeBSD.ORG Mon Jul 14 23:57:40 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7186A1065676 for ; Mon, 14 Jul 2008 23:57:40 +0000 (UTC) (envelope-from fbsd06+X2=af3cff63@mlists.homeunix.com) Received: from fallback-in1.mxes.net (fallback-out1.mxes.net [216.86.168.190]) by mx1.freebsd.org (Postfix) with ESMTP id 51F648FC19 for ; Mon, 14 Jul 2008 23:57:40 +0000 (UTC) (envelope-from fbsd06+X2=af3cff63@mlists.homeunix.com) Received: from mxout-03.mxes.net (mxout-03.mxes.net [216.86.168.178]) by fallback-in1.mxes.net (Postfix) with ESMTP id 43395163F82 for ; Mon, 14 Jul 2008 19:49:51 -0400 (EDT) Received: from gumby.homeunix.com. (unknown [87.81.140.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTP id B9AE623E408; Mon, 14 Jul 2008 19:49:48 -0400 (EDT) Date: Tue, 15 Jul 2008 00:49:44 +0100 From: RW To: freebsd-questions@freebsd.org Message-ID: <20080715004944.712c08ee@gumby.homeunix.com.> In-Reply-To: <20080714233542.GA59789@root.ucsc.edu> References: <20080714233542.GA59789@root.ucsc.edu> X-Mailer: Claws Mail 3.5.0 (GTK+ 2.12.11; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: booloo@ucsc.edu Subject: Re: freebsd-update says -p3, but i've got -p2 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Jul 2008 23:57:40 -0000 On Mon, 14 Jul 2008 16:35:42 -0700 Mark Boolootian wrote: > which leads me to conclude I've got -p3, including the BIND update. > However 'uname -a' says something else: > > FreeBSD mumble.ucsc.edu 7.0-RELEASE-p2 FreeBSD 7.0-RELEASE-p2 #0: Wed I don't use freebsd-update myself, but as I understand it, the kernel doesn't get modified just to change the versioning infomation, so if an update doesn't affect the kernel, you don't see a change in uname -a.