From owner-freebsd-questions@freebsd.org Tue Nov 14 17:12:26 2017 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 6DEA6DD7C3A for ; Tue, 14 Nov 2017 17:12:26 +0000 (UTC) (envelope-from mail@ozzmosis.com) Received: from homiemail-a123.g.dreamhost.com (sub5.mail.dreamhost.com [208.113.200.129]) (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 511CD6671B for ; Tue, 14 Nov 2017 17:12:25 +0000 (UTC) (envelope-from mail@ozzmosis.com) Received: from homiemail-a123.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a123.g.dreamhost.com (Postfix) with ESMTP id 242386000092F; Tue, 14 Nov 2017 09:12:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=ozzmosis.com; h=date:from :to:cc:subject:message-id:references:mime-version:content-type :in-reply-to; s=ozzmosis.com; bh=e6MVEFA2gwB3OoEDF9M9FuEoQjc=; b= HzgCYRP0rv4Ib2QW5+q6T45tRBoc2ZStvefsLF+0Nqy6Uy8BLsp0ohlV+cUXTBfa MLmRMlqZXtBuMGSDuNsFMd6dfF3qY9WGbZnzef8jThTBtSskj1Tdpn1mx2QMj7s9 WFNT5pPM1fYArf7Ivc4f/5UrEiprwCkjRTVBiVf2fvc= Received: from blizzard.ozzmosis.com (124-148-135-246.dyn.iinet.net.au [124.148.135.246]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: relay@ozzmosis.com) by homiemail-a123.g.dreamhost.com (Postfix) with ESMTPSA id D8E8C60000926; Tue, 14 Nov 2017 09:12:18 -0800 (PST) Received: by blizzard.ozzmosis.com (Postfix, from userid 1001) id 1B1EA9D2; Wed, 15 Nov 2017 04:12:16 +1100 (AEDT) Date: Wed, 15 Nov 2017 04:12:16 +1100 From: andrew clarke To: byrnejb@harte-lyne.ca Cc: freebsd-questions@freebsd.org Subject: Re: why does freebsd-update and uname report different patch levels? Message-ID: <20171114171215.lo4j4fvpxlstxdtb@ozzmosis.com> References: <4432633d41c0c5fcf575fdae0af60245.squirrel@webmail.harte-lyne.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4432633d41c0c5fcf575fdae0af60245.squirrel@webmail.harte-lyne.ca> User-Agent: NeoMutt/20171027 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Nov 2017 17:12:26 -0000 On Tue 2017-11-14 12:04:19 UTC-0500, James B. Byrne via freebsd-questions (freebsd-questions@freebsd.org) wrote: > We have recently completed upgrading all of our freebsd-11 systems to > 11.1. Now when we run freebsd-update fetch we see this: > > # freebsd-update fetch > src component not installed, skipped > Looking up update.FreeBSD.org mirrors... 3 mirrors found. > Fetching metadata signature for 11.1-RELEASE from > update5.freebsd.org... done. > Fetching metadata index... done. > Fetching 2 metadata patches.. done. > Applying metadata patches... done. > Fetching 2 metadata files... done. > Inspecting system... done. > Preparing to download files... done. > > No updates needed to update system to 11.1-RELEASE-p3. > > However, when we do 'uname -a' on the same system then we see this: > > FreeBSD inet13.hamilton.harte-lyne.ca 11.1-RELEASE-p1 FreeBSD > 11.1-RELEASE-p1 #0: Wed Aug 9 11:55:48 UTC 2017 > root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 > > Why is there a difference in the reported patch level of the same system? 'uname -a' shows the version of the currently running kernel. 'freebsd-version -k' shows the version of the installed kernel. 'freebsd-version -u' shows the version of the installed userland. Often freebsd-update does not to patch the kernel. It is normal to see the kernel and userland at different patch levels.