From owner-freebsd-current@freebsd.org Mon Mar 30 03:11:27 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 6FFD526F8A3 for ; Mon, 30 Mar 2020 03:11:27 +0000 (UTC) (envelope-from nwhitehorn@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 48rHYB39q2z48C8; Mon, 30 Mar 2020 03:11:26 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from comporellon.tachypleus.net (unknown [IPv6:2605:e000:1314:5ea:997:9b2d:670b:d84d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: nwhitehorn/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id D9F6018F1; Mon, 30 Mar 2020 03:11:17 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Subject: Re: When will the FreeBSD (u)EFI work? To: "Simon J. Gerraty" Cc: Kyle Evans , Rebecca Cran , Tomoaki AOKI , FreeBSD Current , bsd-lists@bsdforge.com 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> <675a41c7-46c1-f548-b285-e5ede55db76a@freebsd.org> <16728.1585537356@kaos.jnpr.net> From: Nathan Whitehorn Message-ID: <18df34fe-6256-6e68-ead5-481e83a501fe@freebsd.org> Date: Sun, 29 Mar 2020 20:11:16 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 MIME-Version: 1.0 In-Reply-To: <16728.1585537356@kaos.jnpr.net> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US 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 03:11:27 -0000 On 2020-03-29 20:02, Simon J. Gerraty wrote: > Nathan Whitehorn wrote: >> It's basically this that has been the problem: we need a way to manage >> updates of the EFI loader in this situation, which we don't currently >> have. The ESP needs to be mounted at a standard point, >> installworld/freebsd-update/etc. need to know to replace files there, we >> need to fall back cleanly on older systems, etc. The original (failed -- > Actually if you are doing secure boot, the *last* thing you want is to > update /efi/boot with an unsigned update. > > So I would think it should be done as a unique operation - do you don't > do it accidentally. > > At least that's how I'm handling it for embedded devices. > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > The problem then is that we have treated loader as a continuously-updatable part of the OS, like the kernel, and the update system and development process assumes they get updated in sync. -Nathan