Date: Tue, 23 May 2017 07:10:29 -0700 From: Ravi Pokala <rpokala@mac.com> To: Ed Maste <emaste@freebsd.org>, Konstantin Belousov <kib@freebsd.org> Cc: "src-committers@freebsd.org" <src-committers@freebsd.org>, "svn-src-all@freebsd.org" <svn-src-all@freebsd.org>, "svn-src-head@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... Message-ID: <76949219-D46A-4D27-A331-1317A1410CD3@panasas.com> In-Reply-To: <CAPyFy2BwmMbRXGO2tT5SiRquUsSbFMYaG0kqy9kxATDQTgB%2B_A@mail.gmail.com> References: <201705230929.v4N9T5g1028124@repo.freebsd.org> <CAPyFy2BwmMbRXGO2tT5SiRquUsSbFMYaG0kqy9kxATDQTgB%2B_A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
-----Original Message----- > From: <owner-src-committers@freebsd.org> on behalf of Ed Maste <emaste@freebsd.org> > Date: 2017-05-23, Tuesday at 07:00 > To: Konstantin Belousov <kib@freebsd.org> > Cc: "src-committers@freebsd.org" <src-committers@freebsd.org>, "svn-src-all@freebsd.org" <svn-src-all@freebsd.org>, "svn-src-head@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 <kib@freebsd.org> 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@)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?76949219-D46A-4D27-A331-1317A1410CD3>