From owner-freebsd-hackers@freebsd.org Mon Mar 25 02:45:31 2019 Return-Path: Delivered-To: freebsd-hackers@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 258E5154EF6B for ; Mon, 25 Mar 2019 02:45:31 +0000 (UTC) (envelope-from james.wright@jigsawdezign.com) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.17.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8CAE17456A for ; Mon, 25 Mar 2019 02:45:30 +0000 (UTC) (envelope-from james.wright@jigsawdezign.com) Received: from [192.168.0.15] ([82.18.193.38]) by mrelayeu.kundenserver.de (mreue108 [212.227.15.179]) with ESMTPSA (Nemesis) id 1N6KQZ-1gtFwg1YpV-016j1o for ; Mon, 25 Mar 2019 03:45:23 +0100 Subject: Re: Adding a new efi-update-loader script: need help understanding Makefile.inc1 for "make installworld" To: freebsd-hackers@freebsd.org References: <642fed43-0535-9ae3-6f01-a943650cd511@bluestop.org> <20190324090103.GO1923@kib.kiev.ua> <20190325000241.GS1923@kib.kiev.ua> <6badde15-d8f4-c4ea-2061-0d3c80c6e82a@bluestop.org> <4cdd585b-2469-fb19-9ac6-5d0af7b9f607@bluestop.org> From: James Wright Message-ID: <6fcddcfe-8d0e-d493-7a1b-2ba093dacabb@jigsawdezign.com> Date: Mon, 25 Mar 2019 02:45:22 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.6.0 MIME-Version: 1.0 In-Reply-To: <4cdd585b-2469-fb19-9ac6-5d0af7b9f607@bluestop.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Provags-ID: V03:K1:tRyWguORGIPz3jj+cljpXxzcEv788JKxG65uiWqREu/TsMY1pdx nHpAoZh1zMC4qfRWQXxU8GqkTbkE3s+csYASwsQ03Hmm//QSC5+PEylcchZti1wxv6wS3Po 6YP/JOXonw5wP+N7Rvrad8U6q5JhdaSYq+7av/ksnDTtqNTmKG0bKVYu/FR+A6P/EUdtP/k EtvZktI8TVMxFl958xkHw== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:oodvE6ELMPA=:J5zakbu1gBnKvDyI8V79WJ eUG6PXiVi69m64zkCT2yZtRUuYHRJrxgM9NxQYFq63KfPbwHpXK2hHrh5kQlAf/QKLo9vzxji sx7cqeewFcQIXXm633wpmROnvJjE6ghTv4YfV64b0kj9ONdadEB1U1rwpaV2EhkiCdbZ6vKR7 fDQARg9Ph3g0n1AP9SANmguj6VJ/aSd2NvRQgHfEPB7yCORU1Zp+AKnkXZCXswhKjNTkvm1Br EF3EZYhgLrcIjzU4QpohzII4z0yAmtaUO/3qpjWcOaQw74N4ouMfFF9WqBA6BGsn++bdF9GIQ M18J09DXRoWVE1Jx7vKS1SiU8EU60WraG7enaJCHh6eagzH/YNkZqPPz1Gr7hhQeaJlLtwaEY mNf2O9hidlz2AO3Z2d+ayMvxJtAnhdLgDFBt9Jh+VEpROvnIH0hbKqLzhnlsL+aFmxbKBibFm TJdhpbAScpER7NGOvJyqvpDSPjdzBcvp1nA2imcnYWvrhn+aKuNrMSCJ6GARw7mo4JD9rr96E aUG5cs9E1+v779AuU6Ns+HNgVWAFwlLX6Q97C1Fkc2O7+LRwdy4PATqU1kTz96tEk4AOZQkry I83b2zeArCc6XGlU0qw/7V6P03FH/RDs4/8YYBxGkgRVDPeqhX0lb/MpYN+h++AVo35B5F9nB /5/7L5h6SQbdADaCGWKQbHP6lUA4A/cDnxY8I5Ejwmy4Pak3dDRjnaotkjinxkrXzW8MLbu1y ud1XVvRy5Qs6slfn3X+VWDf8G+eJHsvQguRNHYBbkNlFxWO+iqJbPt3eEwLqaEUzpUWzSrLvr IS30HCB X-Rspamd-Queue-Id: 8CAE17456A X-Spamd-Bar: ------ Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-6.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.99)[-0.988,0]; REPLY(-4.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Mar 2019 02:45:31 -0000 FYI... I run a quad boot (OSX, FreeBSD, Debian, Win10) setup on a MacbookAir using rEFInd. Nothing annoys me more than the OSX, Linux, and Win10 updates that decide without warning to replace the boot loader on the ESP. FreeBSD was the only OS that doesn't do this (I'm fine with updating /efi/freebsd/loader.efi manually), please could we not mess about replacing boot loaders on the ESP unless explicitly asked to? On 25/03/2019 02:30, Rebecca Cran via freebsd-hackers wrote: > On 3/24/19 7:34 PM, Warner Losh wrote: > >> >> Right. We need a standard location (that maybe can be overridden, >> like you >> can with /boot, if you really want), and that's likely the first >> order of >> business. I don't think we should be second guessing, though. And we >> shouldn't be touching \efi\boot anything unless specifically >> instructed to >> do so. I'm deeply uncomfortable with guessing whether or not to do >> something... > > > I'd be wary of *not* touching \efi\boot, since both Microsoft and > Linux installs \efi\boot\bootx64.efi. And with desktop systems often > not having an UEFI Shell built in and no option to browse for a boot > loader from the BIOS, if the FreeBSD boot entry gets lost somehow > they're stuck. I discovered recently that rEFInd at least knows to > look for \efi\freebsd\loader.efi, but otherwise recovery could be > pretty tricky for people who aren't familiar with UEFI. Perhaps adding > an option to the efi-update-loader script to search for and list > potential ESPs could help, along with good documentation of efibootmgr > etc. > >