From owner-freebsd-arch@freebsd.org Mon Mar 25 02:30:17 2019 Return-Path: Delivered-To: freebsd-arch@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 02694154E6EC for ; Mon, 25 Mar 2019 02:30:17 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 70435736FD for ; Mon, 25 Mar 2019 02:30:16 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: by mailman.ysv.freebsd.org (Postfix) id 311F0154E6E9; Mon, 25 Mar 2019 02:30:16 +0000 (UTC) Delivered-To: arch@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 1F971154E6E8; Mon, 25 Mar 2019 02:30:16 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [65.103.231.193]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id ABFCA736FC; Mon, 25 Mar 2019 02:30:15 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.bluestop.org (Postfix) with ESMTP id B5856C0B40; Sun, 24 Mar 2019 20:31:17 -0600 (MDT) Received: from muon.bluestop.org ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 8FBvfxhnXHbK; Sun, 24 Mar 2019 20:31:17 -0600 (MDT) Received: from photon.int.bluestop.org (unknown [65.103.231.197]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTPSA; Sun, 24 Mar 2019 20:31:17 -0600 (MDT) Subject: Re: Adding a new efi-update-loader script: need help understanding Makefile.inc1 for "make installworld" To: Warner Losh Cc: Konstantin Belousov , FreeBSD Hackers , "freebsd-arch@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> From: Rebecca Cran Message-ID: <4cdd585b-2469-fb19-9ac6-5d0af7b9f607@bluestop.org> Date: Sun, 24 Mar 2019 20:30:13 -0600 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:60.0) Gecko/20100101 Thunderbird/60.5.3 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Rspamd-Queue-Id: ABFCA736FC X-Spamd-Bar: ------ X-Spamd-Result: default: False [-6.97 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; REPLY(-4.00)[]; NEURAL_HAM_SHORT(-0.97)[-0.969,0] X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Mar 2019 02:30:17 -0000 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. -- Rebecca Cran