Date: Thu, 22 Sep 2016 12:49:15 +0100 From: Steve O'Hara-Smith <steve@sohara.org> To: Ian Jefferson <ijeff@sandbox.ca> Cc: freebsd-questions@freebsd.org Subject: Re: freebsd-update not updating kernel? Message-ID: <20160922124915.a0867f6b437f9dc778020d1a@sohara.org> In-Reply-To: <E13BA61B-1299-4C3D-BC48-826A835B9A2C@sandbox.ca> References: <CAAiTEH-DC8riFyroP-kMuptXut5-CJLk9M52vd9kH9FJ_y=8GQ@mail.gmail.com> <0B507E9E-77ED-4CD9-A51D-EF1B35DA45CD@sandbox.ca> <20160922120159.362abd1963b2baee4b148ebd@sohara.org> <E13BA61B-1299-4C3D-BC48-826A835B9A2C@sandbox.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 22 Sep 2016 07:27:40 -0400 Ian Jefferson <ijeff@sandbox.ca> 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 <steve@sohara.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160922124915.a0867f6b437f9dc778020d1a>