From owner-freebsd-questions@freebsd.org Thu Sep 22 11:49:21 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5284FBE5955 for ; Thu, 22 Sep 2016 11:49:21 +0000 (UTC) (envelope-from steve@sohara.org) Received: from smtp3.irishbroadband.ie (smtp3.irishbroadband.ie [62.231.32.5]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1DF93C2F for ; Thu, 22 Sep 2016 11:49:20 +0000 (UTC) (envelope-from steve@sohara.org) Received: from [89.127.62.20] (helo=smtp.lan.sohara.org) by smtp3.irishbroadband.ie with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.76) (envelope-from ) id 1bn2VC-0005i9-4o; Thu, 22 Sep 2016 12:49:18 +0100 Received: from [192.168.63.1] (helo=steve.lan.sohara.org) by smtp.lan.sohara.org with smtp (Exim 4.87 (FreeBSD)) (envelope-from ) id 1bn2VZ-000B8g-53; Thu, 22 Sep 2016 11:49:41 +0000 Date: Thu, 22 Sep 2016 12:49:15 +0100 From: Steve O'Hara-Smith To: Ian Jefferson Cc: freebsd-questions@freebsd.org Subject: Re: freebsd-update not updating kernel? Message-Id: <20160922124915.a0867f6b437f9dc778020d1a@sohara.org> In-Reply-To: References: <0B507E9E-77ED-4CD9-A51D-EF1B35DA45CD@sandbox.ca> <20160922120159.362abd1963b2baee4b148ebd@sohara.org> X-Mailer: Sylpheed 3.5.0 (GTK+ 2.24.29; amd64-portbld-freebsd10.1) X-Clacks-Overhead: "GNU Terry Pratchett" Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2016 11:49:21 -0000 On Thu, 22 Sep 2016 07:27:40 -0400 Ian Jefferson wrote: > It doesn’t seem like freebsd-version is backported to 9.3 but I’m not > sure that would fix the freebsd-update problem nor the lsof issue either. It was part of a fix for that problem - in 9.3 the kernel version is all there is later a userspace version was added along with freebsd-version. > I also found this: > > "The updates distributed by freebsd-update do not always involve the > kernel. It is not necessary to rebuild a custom kernel if the kernel > sources have not been modified by freebsd-update install. However, > freebsd-update will always update/usr/src/sys/conf/newvers.sh. The > current patch level, as indicated by the -p number reported by uname -r, > is obtained from this file. Rebuilding a custom kernel, even if nothing > else changed, allows uname to accurately report the current patch level > of the system. This is particularly helpful when maintaining multiple > systems, as it allows for a quick assessment of the updates installed in > each one. “ Yep that's the full version. > Indeed it looks to me like /usr/src/sys/conf/newvers.sh on my system > “knows” that I am at patch level 45 but freebsd-update doesn’t nor does > uname. Right - so if you do a kernel build and install then the whole system will know about it otherwise it's just tucked away in an unused source file. > I think you are saying that uname get’s its information from the > kernel but that is contradicted by the handbook points above so I’m > unclear and regardless freebsd-update seems broken in this patch. Yep uname gets the version data from the kernel, which gets it from newvers.sh when the kernel is built - which is what that handbook section is telling you in a roundabout and not entirely clear way. > I suppose the ultimate answer is we need to move off 9.3 since it is just > about EOL anyway but I wonder… if freebsd-update is confused will it > perform the upgrade correctly? Yes it will. -- Steve O'Hara-Smith