From owner-freebsd-questions@FreeBSD.ORG Thu May 3 22:42:04 2012 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 CA100106566C for ; Thu, 3 May 2012 22:42:04 +0000 (UTC) (envelope-from bonomi@mail.r-bonomi.com) Received: from mail.r-bonomi.com (mx-out.r-bonomi.com [204.87.227.120]) by mx1.freebsd.org (Postfix) with ESMTP id 8AEBC8FC0C for ; Thu, 3 May 2012 22:42:04 +0000 (UTC) Received: (from bonomi@localhost) by mail.r-bonomi.com (8.14.4/rdb1) id q43Mh6x5030357; Thu, 3 May 2012 17:43:06 -0500 (CDT) Date: Thu, 3 May 2012 17:43:06 -0500 (CDT) From: Robert Bonomi Message-Id: <201205032243.q43Mh6x5030357@mail.r-bonomi.com> To: freebsd-questions@freebsd.org, mike@skew.org In-Reply-To: <201205032152.q43LqNZO004512@chilled.skew.org> Cc: Subject: Re: freebsd-update not updating reported patchlevel 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: Thu, 03 May 2012 22:42:04 -0000 Mike Brown wrote; > I installed 8.2-RELEASE when it was new, and have been just using > freebsd-update since then. I run freebsd-update whenever there are new > critical patches. But for some reason, my system's reported patchlevel number > hasn't updated since p3. [sneck] > But 'uname -r' continues to return "8.2-RELEASE-p3". Rebooting doesn't help. > Is there something I need to do in order to bump the reported patchlevel? I > thought this was supposed to happen automatically, since I didn't have to do > anything to get it up to -p3. Amazingly, this very question was covered on this list within the last few hours. Executive summary: the kernel ID string that uname reports changes only when the -kernel- is changed. -p4, -p5, -p6, and -p7. have -not- involved any changes to the kernel. hence the ID string has stayed at '-p3'. While this _is_ counter-intuitive, it does make sense to avoid pushing a new k ernel out, and/or forcing an admin to rebuild a custom kernel, when the -only- change would be to the ID string.