From owner-freebsd-questions@FreeBSD.ORG Sat Jul 19 15:30:46 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 A42F1106566B for ; Sat, 19 Jul 2008 15:30:46 +0000 (UTC) (envelope-from sonic2000gr@gmail.com) Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.189]) by mx1.freebsd.org (Postfix) with ESMTP id 1A4598FC1D for ; Sat, 19 Jul 2008 15:30:45 +0000 (UTC) (envelope-from sonic2000gr@gmail.com) Received: by fk-out-0910.google.com with SMTP id k31so524245fkk.11 for ; Sat, 19 Jul 2008 08:30:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=oKOQQJ2McLbCAl+pZWITwfP8+Pvyj/4zbFoz/72FAUo=; b=p2OVASzVxEUZqSGOU7tJnlJakuAhB55W3bWQ4OtLf3pLsGX7QbtYnlnfRdDHNHREq8 hq+jAOvZ273B5jbwFVQb7waGH0TAjFJsmcnARCIpc0E5QKr2fcQGlTSklGvvpGMhRqGu iThIEiK6xAHOwDQIBUwMXi68O/mY2Ea6KtV8E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=KAJY9vsSXohRMoF+g5bz31UldeKw4/IWhcds4ej67MImJxH0ftA0I4YPv3NDUeQdKU SXW24pF6D/Ht5ivRoBYE2FICsRTmgf5FE6KFp9UgA3iHw1wiDNUtL6Wg5+eA0IBBkHuV vxusBCSjgst0ppiEvoxY7AzzDp1BKtZ8HJviA= Received: by 10.181.24.14 with SMTP id b14mr914210bkj.22.1216481444571; Sat, 19 Jul 2008 08:30:44 -0700 (PDT) Received: from atlantis.dyndns.org ( [79.129.176.45]) by mx.google.com with ESMTPS id 22sm7160215fkr.4.2008.07.19.08.30.42 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 19 Jul 2008 08:30:43 -0700 (PDT) Message-ID: <488208A0.8040004@gmail.com> Date: Sat, 19 Jul 2008 18:30:40 +0300 From: Manolis Kiagias User-Agent: Thunderbird 2.0.0.14 (X11/20080703) MIME-Version: 1.0 To: David Newman References: <20080714233542.GA59789@root.ucsc.edu> <487BE866.2000309@gmail.com> <488188C2.5090705@gmail.com> <4882038F.6060805@networktest.com> In-Reply-To: <4882038F.6060805@networktest.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org 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: Sat, 19 Jul 2008 15:30:46 -0000 David Newman wrote: >>> 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 Jun 18 07:33:20 UTC 2008 >>>> root@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 >>>> >>>> And although /usr/sbin/named has been updated, it appears not to have >>>> been upgraded: >>>> >>>> $ /usr/sbin/named -v >>>> BIND 9.4.2 >>>> >>>> Thoughts? >>>> >>>> >>> >>> You've got p3, don't worry. There was no kernel update in p3, hence >>> you got the p2 GENERIC kernel. If you want uname to actually show p3, >>> you will have to recompile your kernel > > Shouldn't freebsd-update do this, not only for the kernel and named > and whatever else it updates? > > I'm relatively new to freebsd-update, and while I appreciate its speed > advantange over make buildworld/buildkernel, it's confusing when it > applies updates but does not display correct version numbers. > > dn > > This is not a problem with freebsd-update. The kernel has not changed between -p2 and -p3, so freebsd-update will not get you an updated one. If you recompile the kernel afterwards, it will show -p3 because of the change in /usr/src/sys/conf/newvers.sh (this changes everytime freebsd-update gets new updates, regardless of whether the kernel is updated or not). So, simply by recompiling the kernel you will get the -p3 indication, though nothing much else in this case. When an update *does* include a new kernel *and* you are running a GENERIC kernel, freebsd-update will update it. If you are running your custom kernel, you will have to recompile anyway. Also note that you need to have the relevant parts installed for freebsd-update to update them. For example, if you don't have the kernel sources installed, freebsd-update will *not* download and install them for you.