From owner-freebsd-current@freebsd.org Sun Nov 4 23:10:44 2018 Return-Path: Delivered-To: freebsd-current@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 868EE10F09AE for ; Sun, 4 Nov 2018 23:10:44 +0000 (UTC) (envelope-from rebecca@bluestop.org) Received: from muon.bluestop.org (muon.bluestop.org [96.73.9.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DBF508C391 for ; Sun, 4 Nov 2018 23:10:43 +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 5B73531691; Sun, 4 Nov 2018 16:11:23 -0700 (MST) Received: from muon.bluestop.org ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5GIZFpac2qkt; Sun, 4 Nov 2018 16:11:23 -0700 (MST) Received: from photon.int.bluestop.org (gw.bluestop.org [96.73.9.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTPSA; Sun, 4 Nov 2018 16:11:23 -0700 (MST) From: Rebecca Cran To: freebsd-current@freebsd.org Cc: Warner Losh , Toomas Soome Subject: Re: UEFI: How to go about updating the ESP with loader.efi during installworld Date: Sun, 04 Nov 2018 16:10:41 -0700 Message-ID: <5211180.XOh7uYVVfo@photon.int.bluestop.org> In-Reply-To: References: <5091656.8gLySxXtyI@photon.int.bluestop.org> <1713323.u6MfGjpqfb@photon.int.bluestop.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Rspamd-Queue-Id: DBF508C391 X-Spamd-Result: default: False [-0.59 / 200.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[bluestop.org]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; TO_DN_SOME(0.00)[]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[bluestop.org:+]; MX_GOOD(-0.01)[cached: mail.bluestop.org]; DMARC_POLICY_ALLOW(-0.50)[bluestop.org,quarantine]; NEURAL_HAM_SHORT(-0.07)[-0.067,0]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; CTE_CASE(0.50)[]; ASN(0.00)[asn:7922, ipnet:96.64.0.0/11, country:US]; IP_SCORE(-0.01)[country: US(-0.07)] X-Rspamd-Server: mx1.freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 04 Nov 2018 23:10:44 -0000 On Sunday, 4 November 2018 15:56:25 MST Warner Losh wrote: > I think that's a really really bad idea. We should *NEVER* create them by > default. We are only sliding by on the coat-tails of compatibility by using > efi/boot/boot*.efi. We shouldn't use those at all, unless there's a > compelling reason (like BIOS bogosity) for doing so. I had no plans to > update or use those, at least by default. We should *ONLY* be using those > for *REMOVABLE* media, since that's the only place they are well defined in > the standard. Thanks, I had wrongly presumed it was in the spec for fixed storage as well given that Windows, Linux etc. creates them. Looking at the 2.7 specification I can see I was wrong and agree we should only create files in efi/freebsd. -- Rebecca