From owner-freebsd-current@freebsd.org Wed Aug 26 22:55:20 2015 Return-Path: Delivered-To: freebsd-current@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 B8F059C3BE6 for ; Wed, 26 Aug 2015 22:55:20 +0000 (UTC) (envelope-from pawel@dawidek.net) Received: from mail.dawidek.net (garage.dawidek.net [91.121.88.72]) by mx1.freebsd.org (Postfix) with ESMTP id 82C68207 for ; Wed, 26 Aug 2015 22:55:19 +0000 (UTC) (envelope-from pawel@dawidek.net) Received: from localhost (unknown [91.206.210.19]) by mail.dawidek.net (Postfix) with ESMTPSA id E291DD6F; Thu, 27 Aug 2015 00:55:11 +0200 (CEST) Date: Thu, 27 Aug 2015 00:55:13 +0200 From: Pawel Jakub Dawidek To: NGie Cooper Cc: Xin LI , FreeBSD Current Subject: Re: Read-only /usr/obj/ no longer kosher? Message-ID: <20150826225512.GF1172@garage.freebsd.pl> References: <20150823215552.GB1314@garage.freebsd.pl> <55DA492D.4030804@delphij.net> <20150825210437.GB1172@garage.freebsd.pl> <20150825215347.GD1172@garage.freebsd.pl> <20150825215524.GE1172@garage.freebsd.pl> <55DCEA64.8040304@delphij.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="ew6BAiZeqk4r7MaW" Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 11.0-CURRENT amd64 User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Aug 2015 22:55:20 -0000 --ew6BAiZeqk4r7MaW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Aug 25, 2015 at 03:32:35PM -0700, NGie Cooper wrote: > On Tue, Aug 25, 2015 at 3:21 PM, Xin Li wrote: > > On 08/25/15 14:55, Pawel Jakub Dawidek wrote: > >>> Now that I think of it, it might have been that I did > >>> buildworld/buildkernel before -p1. Then freebsd-update updated > >>> newvers.sh and then I was trying to do installworld. > >> > >> Yes, I can now reproduce it with source updated to -p2. > > > > Yes, that's because freebsd-version.sh is generated from the files (but > > it's not clear to me whether if it's a bug or a feature that 'make > > install' checks if it's up-to-date and decides to regenerate it...). >=20 > It's a quirk for sure. If you change the behavior, people will > definitely complain as they will now need to go back and rebuild > everything. What we have now is misleading. People should recompile. It is rather rare to see security advisory which bumps only patch level and something that doesn't require recompilation (eg. a shell script). Current behaviour would make people think they are running latest patch level because freebsd-version says so, eventhough they only did 'make installworld' without rebuilding affected binaries. --=20 Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://mobter.com --ew6BAiZeqk4r7MaW Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCgAGBQJV3kPQAAoJEJVLhSuxKFt14aYP/j5YIuZmGyx9331antI/8NNi cBghv+L0VPCfSmpzz1gOe6lqB6YGvR+jLBH8pTO/hjTVpA2/yjicrfcnS72ypxbG cteyCsw31XbpOAmLG1y+uWJ+l6fdcg9ZrgW78jH7hkp4nhzZGQl2VrzyB2pgek7I QcAbGfyTv5GnYK5CqZVDrXrQUsTIc0mHbawOVpa7LllI3B0/TVNTCwkUz8DTgLeL //XmwhXGNcaKXI2cSpBHWebsw+Ltdbc2m9NCw/F54TUAYbt0T18Cc74jlwgv5cUY xYLLo7D3faG/BOwrSFjdnYHi/KJOIbC5U0rda9vyDCbNrY7vjwrslvx10msMqG23 ly3MdSBnJRkXVTHB5Md/7iKeNTUH9lUK3ipGV7N6dOG4YiKNy29cSa2u/pPEfi7d RB1PjelV0V04ZXh9opylqSOg4s/p6QnZk20mDdtUznSDyT2wgdc66iB/YElwLrmZ KsQfTtomBAG1FV6kKinMmtm2oKnN/HycEBlC9k9YiFcQ0hVcHyFR+AjoBCJbpF2T 8hAlMMfE+X0GnfkMj8nUHL4tT7/OrVuQLzcLejW74JcUr1maJslFwVDQbQWj5Qbj rGaPnSGMbNRhKDyHVc6m7PixBkzcavb94scNnqdzUbDLqQaxJe5C6XR0d+YKZp2P X0gPB06smrrWLcS6GypU =RUzZ -----END PGP SIGNATURE----- --ew6BAiZeqk4r7MaW--