From owner-svn-src-all@freebsd.org Tue May 23 14:10:44 2017 Return-Path: Delivered-To: svn-src-all@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 46829D7AD0C; Tue, 23 May 2017 14:10:44 +0000 (UTC) (envelope-from rpokala@mac.com) Received: from mr11p00im-asmtp004.me.com (mr11p00im-asmtp004.me.com [17.110.69.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 280721359; Tue, 23 May 2017 14:10:44 +0000 (UTC) (envelope-from rpokala@mac.com) Received: from process-dkim-sign-daemon.mr11p00im-asmtp004.me.com by mr11p00im-asmtp004.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) id <0OQE00F00S2JD200@mr11p00im-asmtp004.me.com>; Tue, 23 May 2017 14:10:31 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mac.com; s=4d515a; t=1495548631; bh=9Er4YjISgiYC5Jc7lYtF4Qp/grD1lxlcA7hzE52yDwg=; h=Date:Subject:From:To:Message-id:MIME-version:Content-type; b=u+Slni5a/fg4o2pinSN1BLdEHKJsZRjd/KabGae/Pf91ryVmzagXFkPAiXaNEUCnj IFZSm+04PJGVj4vByep0wTpR0e97XD37q0tPfM7q+sL97UVBlOPQ9f6AzMDDw2Z7hK Gs/ugcGYoOkiu3tyVks7msKM1y6wnV2vjyg4CVvZW9UKHQyI4ReMQc8xIxdVsNkkt7 HaGrjBpsGpsH/UD/XkHxUqcN72KahJll7C4oDiiO+rHnWrjLLa7ToPf7yg76yLjklJ 0VDQull+Fz0KrXFSq3DwDU+zVdXfslylpuIQ8O6S1wbyDYy2s0B8F8W1qNBpG8Aph9 nQOvC8dABDeBw== Received: from icloud.com ([127.0.0.1]) by mr11p00im-asmtp004.me.com (Oracle Communications Messaging Server 7.0.5.38.0 64bit (built Feb 26 2016)) with ESMTPSA id <0OQE00OB6SPHK020@mr11p00im-asmtp004.me.com>; Tue, 23 May 2017 14:10:30 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-05-23_04:,, signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1034 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1701120000 definitions=main-1705230074 User-Agent: Microsoft-MacOutlook/f.21.0.170409 Date: Tue, 23 May 2017 07:10:29 -0700 Subject: Re: svn commit: r318736 - in head: cddl/lib/libzfs contrib/compiler-rt/lib/sanitizer_common contrib/openbsm/libbsm include lib/libarchive lib/libc/gen lib/libc/include lib/libc/sys lib/libkvm lib/libmi... From: Ravi Pokala To: Ed Maste , Konstantin Belousov Cc: "src-committers@freebsd.org" , "svn-src-all@freebsd.org" , "svn-src-head@freebsd.org" Message-id: <76949219-D46A-4D27-A331-1317A1410CD3@panasas.com> Thread-topic: svn commit: r318736 - in head: cddl/lib/libzfs contrib/compiler-rt/lib/sanitizer_common contrib/openbsm/libbsm include lib/libarchive lib/libc/gen lib/libc/include lib/libc/sys lib/libkvm lib/libmi... References: <201705230929.v4N9T5g1028124@repo.freebsd.org> In-reply-to: MIME-version: 1.0 Content-type: text/plain; charset=UTF-8 Content-transfer-encoding: 7bit X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2017 14:10:44 -0000 -----Original Message----- > From: on behalf of Ed Maste > Date: 2017-05-23, Tuesday at 07:00 > To: Konstantin Belousov > Cc: "src-committers@freebsd.org" , "svn-src-all@freebsd.org" , "svn-src-head@freebsd.org" > Subject: Re: svn commit: r318736 - in head: cddl/lib/libzfs contrib/compiler-rt/lib/sanitizer_common contrib/openbsm/libbsm include lib/libarchive lib/libc/gen lib/libc/include lib/libc/sys lib/libkvm lib/libmi... > > On 23 May 2017 at 05:29, Konstantin Belousov wrote: >> Author: kib >> Date: Tue May 23 09:29:05 2017 >> New Revision: 318736 >> URL: https://svnweb.freebsd.org/changeset/base/318736 >> >> Update note: strictly follow the instructions in UPDATING. Build >> and install the new kernel with COMPAT_FREEBSD11 option enabled, >> then reboot, and only then install new world. > > There's been some confusion over this point, so let me clarify: this > note refers to the regular upgrade procedure documented in UPDATING > under the heading "To rebuild everything and install it on the current > system". Following the regular, documented procedure is both necessary > and sufficient for the ino64 change. > > It's mentioned explicitly here because folks often take shortcuts with > updating (e.g. not rebooting), and such a shortcut will fail with the >ino64 change. So then `tools/build/beinstall.sh' won't DTRT for this upgrade? -Ravi (rpokala@)