From owner-freebsd-current@freebsd.org Sun Nov 4 21:41:35 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 9550910EDBBE for ; Sun, 4 Nov 2018 21:41:35 +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 0B82088F9C for ; Sun, 4 Nov 2018 21:41:35 +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 AE124315C2; Sun, 4 Nov 2018 14:42:14 -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 ZdlFhAupho7T; Sun, 4 Nov 2018 14:42:14 -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 14:42:14 -0700 (MST) From: Rebecca Cran To: freebsd-current@freebsd.org Cc: Toomas Soome Subject: Re: UEFI: How to go about updating the ESP with loader.efi during installworld Date: Sun, 04 Nov 2018 14:41:33 -0700 Message-ID: <1713323.u6MfGjpqfb@photon.int.bluestop.org> In-Reply-To: References: <5091656.8gLySxXtyI@photon.int.bluestop.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Rspamd-Queue-Id: 0B82088F9C X-Spamd-Result: default: False [-0.07 / 200.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[bluestop.org]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_SPAM_SHORT(0.45)[0.455,0]; MIME_GOOD(-0.10)[text/plain]; IP_SCORE(-0.01)[country: US(-0.07)]; RCVD_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[bluestop.org:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[bluestop.org,quarantine]; MX_GOOD(-0.01)[cached: mail.bluestop.org]; 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]; FREEMAIL_CC(0.00)[me.com] 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 21:41:35 -0000 On Sunday, 4 November 2018 14:36:13 MST Toomas Soome wrote: > it is reasonable to have efi/freebsd directory, the efi/boot/bootx64.efi is > hard one of course. But then again, it is problem only when we can not > setup EFI bootmanager variables ? the bootx64.efi is default when bootmgr > is not set up. Yes, I think we should only create efi/boot/boot{x64,ia32,aa64,arm}.efi if it doesn't already exist in which case we're likely the only OS on the system. -- Rebecca