From owner-svn-src-all@freebsd.org Sat Mar 9 17:18:00 2019 Return-Path: Delivered-To: svn-src-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B2088152E956; Sat, 9 Mar 2019 17:18:00 +0000 (UTC) (envelope-from imp@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3AA4A8FD3F; Sat, 9 Mar 2019 17:18:00 +0000 (UTC) (envelope-from imp@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 2EAEFE618; Sat, 9 Mar 2019 17:18:00 +0000 (UTC) (envelope-from imp@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x29HI0VN069735; Sat, 9 Mar 2019 17:18:00 GMT (envelope-from imp@FreeBSD.org) Received: (from imp@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x29HI0cw069734; Sat, 9 Mar 2019 17:18:00 GMT (envelope-from imp@FreeBSD.org) Message-Id: <201903091718.x29HI0cw069734@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: imp set sender to imp@FreeBSD.org using -f From: Warner Losh Date: Sat, 9 Mar 2019 17:18:00 +0000 (UTC) To: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: svn commit: r344972 - head X-SVN-Group: head X-SVN-Commit-Author: imp X-SVN-Commit-Paths: head X-SVN-Commit-Revision: 344972 X-SVN-Commit-Repository: base MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 3AA4A8FD3F X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.96 / 15.00]; local_wl_from(0.00)[FreeBSD.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.96)[-0.956,0]; ASN(0.00)[asn:11403, ipnet:2610:1c1:1::/48, country:US]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.29 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: Sat, 09 Mar 2019 17:18:00 -0000 Author: imp Date: Sat Mar 9 17:17:59 2019 New Revision: 344972 URL: https://svnweb.freebsd.org/changeset/base/344972 Log: Augment ino64 entry When updating across this change (the introduction of ino64), the "fast and loose" practice of rebooting to multiuser and then doing an installworld fails with missing symbols. Recommend strongly that users do this in single user mode. The multiuser case only ever works by accident because its requirements are stronger than is supported accross this change. It usually works because critical symbols don't change their version number in libc, which wasn't the case here. Modified: head/UPDATING Modified: head/UPDATING ============================================================================== --- head/UPDATING Sat Mar 9 17:17:55 2019 (r344971) +++ head/UPDATING Sat Mar 9 17:17:59 2019 (r344972) @@ -714,11 +714,13 @@ NOTE TO PEOPLE WHO THINK THAT FreeBSD 13.x IS SLOW: system will be running the ino64 kernel with the existing world). For the safest in-place upgrade begin by removing previous build - artifacts via "rm -rf /usr/obj/*". Then, carefully follow the - full procedure documented below under the heading "To rebuild - everything and install it on the current system." Specifically, - a reboot is required after installing the new kernel before - installing world. + artifacts via "rm -rf /usr/obj/*". Then, carefully follow the full + procedure documented below under the heading "To rebuild everything and + install it on the current system." Specifically, a reboot is required + after installing the new kernel before installing world. While an + installworld normally works by accident from multiuser after rebooting + the proper kernel, there are many cases where this will fail across this + upgrade and installworld from single user is required. 20170424: The NATM framework including the en(4), fatm(4), hatm(4), and