From owner-freebsd-questions@freebsd.org Tue Nov 14 17:14:10 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 6D5E4DD7DC6 for ; Tue, 14 Nov 2017 17:14:10 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mailrelay14.qsc.de (mailrelay14.qsc.de [212.99.163.154]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.antispameurope.com", Issuer "TeleSec ServerPass Class 2 CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D87CA66860 for ; Tue, 14 Nov 2017 17:14:09 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx01.qsc.de ([213.148.129.14]) by mailrelay14.qsc.de; Tue, 14 Nov 2017 18:14:00 +0100 Received: from r56.edvax.de (port-92-195-23-159.dynamic.qsc.de [92.195.23.159]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx01.qsc.de (Postfix) with ESMTPS id E37C63CBF9; Tue, 14 Nov 2017 18:13:59 +0100 (CET) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id vAEHDw0u002397; Tue, 14 Nov 2017 18:13:58 +0100 (CET) (envelope-from freebsd@edvax.de) Date: Tue, 14 Nov 2017 18:13:58 +0100 From: Polytropon To: byrnejb@harte-lyne.ca Cc: "James B. Byrne via freebsd-questions" Subject: Re: why does freebsd-update and uname report different patch levels? Message-Id: <20171114181358.cb19a85d.freebsd@edvax.de> In-Reply-To: <4432633d41c0c5fcf575fdae0af60245.squirrel@webmail.harte-lyne.ca> References: <4432633d41c0c5fcf575fdae0af60245.squirrel@webmail.harte-lyne.ca> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-cloud-security-sender: freebsd@edvax.de X-cloud-security-recipient: freebsd-questions@freebsd.org X-cloud-security-Virusscan: CLEAN X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on mailrelay14.qsc.de with 5832C683456 X-cloud-security-connect: mx01.qsc.de[213.148.129.14], TLS=1, IP=213.148.129.14 X-cloud-security: scantime:.1466 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:14:10 -0000 On Tue, 14 Nov 2017 12:04:19 -0500, James B. Byrne via freebsd-questions 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? The patch level only reflects the updates to the kernel. If an update only contains changes to the userland (and the kernel stays untouched), its version won't be changed. As the "uname" command gets its information from the kernel, userland changes cannot be made visible that way. This is where the "freebsd-version" command is useful. See "man uname" and "man freebsd-version" for details. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...