From owner-freebsd-security@FreeBSD.ORG Thu Jun 5 22:45:29 2014 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EBE81E92 for ; Thu, 5 Jun 2014 22:45:29 +0000 (UTC) Received: from mail.utahbroadband.com (mail.utahbroadband.com [204.14.20.91]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mail.utahbroadband.com", Issuer "mail.utahbroadband.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id AB679243B for ; Thu, 5 Jun 2014 22:45:29 +0000 (UTC) Received: (qmail 18877 invoked by uid 89); 5 Jun 2014 22:38:14 -0000 Received: from unknown (HELO ?192.168.0.8?) (danallen46@airwired.net@66.29.174.6) by mail.utahbroadband.com with ESMTPA; 5 Jun 2014 22:38:14 -0000 From: Dan Allen Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: freebsd-update p5 is labeled p4 Message-Id: Date: Thu, 5 Jun 2014 16:38:44 -0600 To: freebsd-security@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) X-Mailer: Apple Mail (2.1510) X-Mailman-Approved-At: Fri, 06 Jun 2014 00:10:27 +0000 X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jun 2014 22:45:30 -0000 I am not sure if this is the right forum, but since these binary updates = via freebsd-update are usually security oriented... I wanted to report that today's latest binary p5 update (June 5, 2014) = does not correctly update the boot line that says 10.0p5. Rather, it = reports p4, even after install p5 and rebooting. It is a nit, but it is = nice to have it correct. After installing p5 this is what I get just = before the login prompt: FreeBSD 10.0-RELEASE-p4 (GENERIC) #0: Tue Jun 3 12:52:18 UTC 2014 If somebody sees this and knows a better list to report this on, could = you please forward it appropriately? Thanks, Dan Allen Building FreeBSD since 2.15