From owner-freebsd-current@freebsd.org Sun Nov 4 21:32:13 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 3276F10ED424 for ; Sun, 4 Nov 2018 21:32:13 +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 AE469887CA for ; Sun, 4 Nov 2018 21:32:12 +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 5BFA9315B3 for ; Sun, 4 Nov 2018 14:32:52 -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 S1623TRSMMaR for ; Sun, 4 Nov 2018 14:32:52 -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 for ; Sun, 4 Nov 2018 14:32:52 -0700 (MST) From: Rebecca Cran To: freebsd-current@freebsd.org Subject: Re: UEFI: How to go about updating the ESP with loader.efi during installworld Date: Sun, 04 Nov 2018 14:32:11 -0700 Message-ID: <15282432.vxEf1mJfsr@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: AE469887CA X-Spamd-Result: default: False [-0.03 / 200.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[bluestop.org]; FROM_HAS_DN(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[text/plain]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; TO_DN_NONE(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; RCVD_COUNT_THREE(0.00)[4]; NEURAL_SPAM_SHORT(0.49)[0.489,0]; DKIM_TRACE(0.00)[bluestop.org:+]; 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]; 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 21:32:13 -0000 On Sunday, 4 November 2018 14:25:26 MST Allan Jude wrote: > I wouldn't depend on the /etc/fstab entry existing. I am not sure I want > installworld randomly fobbing around in my EFI partition. Especially if, > for example, my EFI/BOOT is not FreeBSD, but rEFInd or something. I tend to agree. I have work planned in the near future to teach FreeBSD that EFI/BOOT may _not_ be FreeBSD and to play nice with other bootloaders, whether that be reFIND, GRUB, Windows etc. But yes, the big difference with this is there's much more code in loader.efi than we currently put in the bootblocks with boot0cfg or "gpart bootcode" and we might run into problems if we don't at least warn users that they'll need to update it. -- Rebecca