From owner-freebsd-questions@FreeBSD.ORG Sat Oct 13 03:29:59 2007 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 5CD6416A4EF for ; Sat, 13 Oct 2007 03:29:59 +0000 (UTC) (envelope-from vinny-mail-01+f.questions20071007@palaceofretention.ca) Received: from www.giovannetti.ca (www.giovannetti.ca [206.248.136.48]) by mx1.freebsd.org (Postfix) with ESMTP id 44C0013C45D for ; Sat, 13 Oct 2007 03:29:59 +0000 (UTC) (envelope-from vinny-mail-01+f.questions20071007@palaceofretention.ca) Received: from the.palaceofretention.ca (intgateway.palaceofretention.ca [10.10.10.42]) by www.giovannetti.ca (Postfix) with ESMTP id E25DF11460 for ; Fri, 12 Oct 2007 23:41:44 -0400 (EDT) Message-ID: <47103B95.7010606@palaceofretention.ca> Date: Fri, 12 Oct 2007 23:29:25 -0400 From: Vinny User-Agent: Thunderbird 2.0.0.0 (X11/20070528) MIME-Version: 1.0 To: freebsd-questions Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: freebsd-update port uname/internal patch level mismatch 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, 13 Oct 2007 03:29:59 -0000 Hi, I noticed that using freebsd-update on a freshly installed 6.2-RELEASE system yielded the following mismatch: $ uname -vp FreeBSD 6.2-RELEASE-p4 #0: Thu Apr 26 17:55:55 UTC 2007 root@i386-builder.daemonology.net:/usr/obj/usr/src/sys/SMP i386 The results of running a freebsd-update fetch give: zcnew# freebsd-update fetch Looking up update.FreeBSD.org mirrors... 1 mirrors found. Fetching metadata signature from update1.FreeBSD.org... done. Fetching metadata index... done. Inspecting system... done. Preparing to download files... done. No updates needed to update system to 6.2-RELEASE-p8. So uname says -p4 and freebsd-update says -p8 I know -p8 is correct. The kernel was last patched in -p4 so maybe the uname information isn't updated if the kernel isn't updated...? If there is something I'm doing wrong, please let me know. Thank you. Vinny