Date: Thu, 22 Sep 2016 07:27:40 -0400 From: Ian Jefferson <ijeff@sandbox.ca> To: freebsd-questions@freebsd.org Subject: Re: freebsd-update not updating kernel? Message-ID: <E13BA61B-1299-4C3D-BC48-826A835B9A2C@sandbox.ca> In-Reply-To: <20160922120159.362abd1963b2baee4b148ebd@sohara.org> References: <CAAiTEH-DC8riFyroP-kMuptXut5-CJLk9M52vd9kH9FJ_y=8GQ@mail.gmail.com> <0B507E9E-77ED-4CD9-A51D-EF1B35DA45CD@sandbox.ca> <20160922120159.362abd1963b2baee4b148ebd@sohara.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Sep 22, 2016, at 7:01 AM, Steve O'Hara-Smith <steve@sohara.org> = wrote: >=20 > On Thu, 22 Sep 2016 06:14:28 -0400 > Ian Jefferson <ijeff@sandbox.ca> wrote: >=20 >> I was having a similar issue with freebsd-update not being aware = (able?) >> to patch up to 9.3-RELEASE-p45. >=20 > Not all updates change the kernel so it is very possible for the > kernel version (which uname reports) to be older than the latest = update > installed. In 10.3 there's freebsd-version which reports the system = version > as distinct from the kernel version to resolve this problem, I'm not = sure > if it has been backported to 9.3 though - try it and see. >=20 Thanks, It doesn=E2=80=99t seem like freebsd-version is backported to 9.3 but = I=E2=80=99m not sure that would fix the freebsd-update problem nor the = lsof issue either. 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. =E2=80=9C here: = https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrad= ing-freebsdupdate.html Indeed it looks to me like /usr/src/sys/conf/newvers.sh on my system = =E2=80=9Cknows=E2=80=9D that I am at patch level 45 but freebsd-update = doesn=E2=80=99t nor does uname. I think you are saying that uname = get=E2=80=99s its information from the kernel but that is contradicted = by the handbook points above so I=E2=80=99m unclear and regardless = freebsd-update seems broken in this patch. My newvers.sh file contains the following: TYPE=3D"FreeBSD" REVISION=3D"9.3" BRANCH=3D"RELEASE-p45" if [ "X${BRANCH_OVERRIDE}" !=3D "X" ]; then BRANCH=3D${BRANCH_OVERRIDE} fi RELEASE=3D"${REVISION}-${BRANCH}" VERSION=3D"${TYPE} ${RELEASE}=E2=80=9D I suppose the ultimate answer is we need to move off 9.3 since it is = just about EOL anyway but I wonder=E2=80=A6 if freebsd-update is = confused will it perform the upgrade correctly? Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E13BA61B-1299-4C3D-BC48-826A835B9A2C>