Date: Thu, 22 Sep 2016 06:14:28 -0400 From: Ian Jefferson <ijeff@sandbox.ca> To: freebsd-questions@freebsd.org Subject: Re: freebsd-update not updating kernel? Message-ID: <0B507E9E-77ED-4CD9-A51D-EF1B35DA45CD@sandbox.ca> In-Reply-To: <CAAiTEH-DC8riFyroP-kMuptXut5-CJLk9M52vd9kH9FJ_y=8GQ@mail.gmail.com> References: <CAAiTEH-DC8riFyroP-kMuptXut5-CJLk9M52vd9kH9FJ_y=8GQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I was having a similar issue with freebsd-update not being aware (able?) = to patch up to 9.3-RELEASE-p45. I am continually getting messages from freebsd-update cron like this: = **************************************************************************= **** Looking up update.FreeBSD.org mirrors... 4 mirrors found. Fetching metadata signature for 9.3-RELEASE from update6.freebsd.org... = done. Fetching metadata index... done. Inspecting system... done. Preparing to download files... done. The following files will be removed as part of updating to = 9.3-RELEASE-p45: = **************************************************************************= ****** I can run freebsd-update fetch and install all day long with reboots and = uname still reports 9.3-RELEASE-p43. For fun I installed lsof and I can reproduce Matt=E2=80=99s problem = exactly. So does uname(3) or uname(1) report on the kernel or does it simply = report back an environment variable? It looks to me like the latter and = perhaps there is something about this p43 to p45 update that is not = setting this environment variable up. Both "freebsd-update cron" and =E2=80=9Clsof" don=E2=80=99t seem to = think the upgrade/patch has occurred. In the case "freebsd-update = cron=E2=80=9D every day it reports by email that some update is required = to get to p43. Is this a bug? Ian > On Sep 7, 2016, at 8:38 AM, Matthew Pounsett <matt@conundrum.com> = wrote: >=20 > It looks to me from what I'm pasting below as if there is a kernel out > there somewhere for 9.3-RELEASE-p45, but freebsd-update is = unable/unwilling > to fetch it. I've also got Virtualbox segfaulting, which frequently > happens to me mid-upgrade when there's a kernel/package mismatch. >=20 > Does anyone have an explanation for what's happening here? >=20 > % uname -a > FreeBSD localhost 9.3-RELEASE-p43 FreeBSD 9.3-RELEASE-p43 #0: Sat May = 28 > 00:19:32 UTC 2016 > root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC > amd64 >=20 > % sudo freebsd-update -F fetch install > Looking up update.FreeBSD.org mirrors... 4 mirrors found. > Fetching metadata signature for 9.3-RELEASE from = update6.freebsd.org... > done. > Fetching metadata index... done. > Inspecting system... done. > Preparing to download files... done. >=20 > No updates needed to update system to 9.3-RELEASE-p45. > No updates are available to install. > Run '/usr/sbin/freebsd-update fetch' first. >=20 > % sudo pkg install -f lsof > Updating FreeBSD repository catalogue... > FreeBSD repository is up-to-date. > All repositories are up-to-date. > The following 1 package(s) will be affected (of 0 checked): >=20 > Installed packages to be REINSTALLED: > lsof-4.90.e,8 >=20 > Number of packages to be reinstalled: 1 >=20 > 111 KiB to be downloaded. >=20 > Proceed with this action? [y/N]: y > Fetching lsof-4.90.e,8.txz: 100% 111 KiB 113.9kB/s 00:01 > Checking integrity... done (0 conflicting) > [1/1] Reinstalling lsof-4.90.e,8... > [1/1] Extracting lsof-4.90.e,8: 100% >=20 > % lsof >/dev/null > lsof: WARNING: compiled for FreeBSD release 9.3-RELEASE-p45; this is > 9.3-RELEASE-p43. > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to = "freebsd-questions-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0B507E9E-77ED-4CD9-A51D-EF1B35DA45CD>