From owner-svn-src-head@freebsd.org Sat Mar 9 17:17:45 2019 Return-Path: Delivered-To: svn-src-head@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 9B20D152E937; Sat, 9 Mar 2019 17:17:45 +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 4067F8FC3F; Sat, 9 Mar 2019 17:17:45 +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 313DAE604; Sat, 9 Mar 2019 17:17:45 +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 x29HHja4069619; Sat, 9 Mar 2019 17:17:45 GMT (envelope-from imp@FreeBSD.org) Received: (from imp@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x29HHjcc069618; Sat, 9 Mar 2019 17:17:45 GMT (envelope-from imp@FreeBSD.org) Message-Id: <201903091717.x29HHjcc069618@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:17:45 +0000 (UTC) To: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: svn commit: r344970 - head X-SVN-Group: head X-SVN-Commit-Author: imp X-SVN-Commit-Paths: head X-SVN-Commit-Revision: 344970 X-SVN-Commit-Repository: base MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 4067F8FC3F 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]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; ASN(0.00)[asn:11403, ipnet:2610:1c1:1::/48, country:US] X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Mar 2019 17:17:45 -0000 Author: imp Date: Sat Mar 9 17:17:44 2019 New Revision: 344970 URL: https://svnweb.freebsd.org/changeset/base/344970 Log: Misc fixes based on upgrading a laptop from 11.1R to -current Add note about needing to start zfs because mount -a doesn't do that. Add the word 'supported' before 'older branches' for older binaries. Add note about options in custom config files as well. Modified: head/UPDATING Modified: head/UPDATING ============================================================================== --- head/UPDATING Sat Mar 9 12:54:10 2019 (r344969) +++ head/UPDATING Sat Mar 9 17:17:44 2019 (r344970) @@ -1901,7 +1901,8 @@ COMMON ITEMS: fsck -p mount -u / mount -a - cd src + sh /etc/rc.d/zfs start # mount zfs filesystem, if needed + cd src # full path to source adjkerntz -i # if CMOS is wall time Also, when doing a major release upgrade, it is required that you boot into single user mode to do the installworld. @@ -1931,10 +1932,12 @@ COMMON ITEMS: option for existing binaries (e.g. COMPAT_FREEBSD11 to run 11.x binaries). Failure to do so may leave you with a system that is hard to boot to recover. A GENERIC kernel will include suitable - compatibility options to run binaries from older branches. + compatibility options to run binaries from supported older branches. Make sure that you merge any new devices from GENERIC since the - last time you updated your kernel config file. + last time you updated your kernel config file. Options also + change over time, so you may need to adjust your custom kernels + for these as well. [9] If CPUTYPE is defined in your /etc/make.conf, make sure to use the "?=" instead of the "=" assignment operator, so that buildworld can