From owner-freebsd-current@freebsd.org Sun Nov 4 23:36:34 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 732BE10F1653 for ; Sun, 4 Nov 2018 23:36:34 +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 B25A38D24A; Sun, 4 Nov 2018 23:36:33 +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 547EC316BD; Sun, 4 Nov 2018 16:37:13 -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 tySfd-PlknkP; Sun, 4 Nov 2018 16:37:13 -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:37:13 -0700 (MST) From: Rebecca Cran To: freebsd-current@freebsd.org Cc: Warner Losh , Allan Jude Subject: Re: UEFI: How to go about updating the ESP with loader.efi during installworld Date: Sun, 04 Nov 2018 16:36:31 -0700 Message-ID: <1905693.uJW0cDvVUg@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: B25A38D24A X-Spamd-Result: default: False [-1.97 / 200.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; R_DKIM_ALLOW(-0.20)[bluestop.org]; NEURAL_HAM_MEDIUM(-0.78)[-0.785,0]; 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:+]; DMARC_POLICY_ALLOW(-0.50)[bluestop.org,quarantine]; MX_GOOD(-0.01)[cached: mail.bluestop.org]; NEURAL_HAM_SHORT(-0.66)[-0.659,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:36:34 -0000 On Sunday, 4 November 2018 16:07:17 MST Warner Losh wrote: > Finally, I have a /dev/efi/esp pseudo label support coded up for geom > (along with /dev/efi/boot for the putative root device). There's some > issues with it, so I set it aside some time ago to work on other higher > priority things. We could assume that if there's a filesystem mounted on > /dev/efi/esp, we should update the boot blocks there. We could, by default, > mount it as /efi. A weaker test, though one also in keeping with tradition, > would be to only install into /efi if it's a directory, and it's also a > mount point. that would preserve the status quo and not even need my > /dev/efi/esp code so would work out better from a number of assumptions > point of view. I wonder if we could coordinate our efforts and push to get this finished off in the next few months? I've been pushing my changes to https://github.com/bcran/freebsd/tree/efi-esp-generation . -- Rebecca