From owner-freebsd-current@freebsd.org Mon Mar 30 02:10:16 2020 Return-Path: Delivered-To: freebsd-current@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 673ED26CB5A for ; Mon, 30 Mar 2020 02:10:16 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48rGBX4BDZz3FT4 for ; Mon, 30 Mar 2020 02:10:11 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-qv1-f41.google.com (mail-qv1-f41.google.com [209.85.219.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id B01E51187 for ; Mon, 30 Mar 2020 02:10:03 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-qv1-f41.google.com with SMTP id c28so8161269qvb.10 for ; Sun, 29 Mar 2020 19:10:03 -0700 (PDT) X-Gm-Message-State: ANhLgQ3XriyMPZ1w1uf80xqsMYksp4jzEax0k9U3+CMAsmKDwPxjl8h8 8wW6pUK3jJjdSGNU4hqnmZXqsbgJjPnaT/4HuQc= X-Google-Smtp-Source: ADFU+vu+o0PdX/4BujdpqvC8/CXOxbkz3pYSjI9VZDu7XDoXQ3yeef2IMxxYZ+9pcB3aD/TPAAsoWrQa+Lx+JRdtkXQ= X-Received: by 2002:a05:6214:12c1:: with SMTP id s1mr9469007qvv.150.1585534202657; Sun, 29 Mar 2020 19:10:02 -0700 (PDT) MIME-Version: 1.0 References: <318FDBAF-448F-4C55-A9A8-69D71A73E43B@me.com> <344e85545cfc47c9835fc5918e5b1dc1@udns.ultimatedns.net> <20200329211137.012a8fd62b58525b027bcfb6@dec.sakura.ne.jp> <40bacb99-d463-cbad-3ccf-b3ddd6856d10@bsdio.com> In-Reply-To: <40bacb99-d463-cbad-3ccf-b3ddd6856d10@bsdio.com> From: Kyle Evans Date: Sun, 29 Mar 2020 21:09:51 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: When will the FreeBSD (u)EFI work? To: Rebecca Cran Cc: Tomoaki AOKI , FreeBSD Current , bsd-lists@bsdforge.com Content-Type: text/plain; charset="UTF-8" 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: Mon, 30 Mar 2020 02:10:16 -0000 On Sun, Mar 29, 2020 at 6:19 PM Rebecca Cran wrote: > > On 3/29/20 6:11 AM, Tomoaki AOKI wrote: > > > > > 3. based solution looks good to me. > > > > IMHO, assuming /efi/bootx[64|32].efi is boot1.efi or loader.efi > > or EFI environment pointing to either one is properly used, > > > That's another thing: we should be installing loader.efi as > \efi\boot\bootx64.efi (as well as \boot\freebsd\loader.efi) since it's > entirely possible to lose the Boot Manager entry and end up with an > unbootable system as a result. Unfortunately people have had bad > experiences with other operating systems overwriting bootx64.efi and > don't believe we should do that. > I have mixed feelings about this -- symlinks don't exist on FAT, right? So then the maintenance overhead goes up, as you can always replace \EFI\FreeBSD\ bits, but you need to make sure \EFI\BOOT components are actually 100% without-a-doubt yours before you replace them. I'd be in favor of installing to \EFI\BOOT\... as well if and only if the file doesn't already exist, assuming we can figure out how to make it not a maintenance nightmare -- which I suspect would just mean that we have some tool that users use to update the ESP rather than instructing them to examine/replace files manually. Thanks, Kyle Evans