From owner-freebsd-current@freebsd.org Mon Mar 30 03:22:02 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 EB73426FF3F for ; Mon, 30 Mar 2020 03:22:02 +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 48rHnM1Mgsz4Cwh; Mon, 30 Mar 2020 03:21:57 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: from mail-qk1-f169.google.com (mail-qk1-f169.google.com [209.85.222.169]) (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 164A31A27; Mon, 30 Mar 2020 03:21:49 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-qk1-f169.google.com with SMTP id i6so17626701qke.1; Sun, 29 Mar 2020 20:21:49 -0700 (PDT) X-Gm-Message-State: ANhLgQ2gmFOreLWGXpvej07/ZfcfEsiQV4bAjD82h32LdBn5deSOa744 ODP6YnINsMhH/N36UmXLvp6DWej6KBUVoCBdiJ0= X-Google-Smtp-Source: ADFU+vvJNCzoQGz2CWagtnxYTnHYGhSENr/1Xag9kZMxptlDJp9WX8PXc4L8v9fbWwYzUC1qtlUoAKH8MHlHjDG8SUQ= X-Received: by 2002:a05:620a:1301:: with SMTP id o1mr9690542qkj.34.1585538508348; Sun, 29 Mar 2020 20:21:48 -0700 (PDT) MIME-Version: 1.0 References: <18df34fe-6256-6e68-ead5-481e83a501fe@freebsd.org> <4C050E22-E571-47ED-87A1-FE1BAC69A073@bsdio.com> In-Reply-To: <4C050E22-E571-47ED-87A1-FE1BAC69A073@bsdio.com> From: Kyle Evans Date: Sun, 29 Mar 2020 22:21:37 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: When will the FreeBSD (u)EFI work? To: Rebecca Cran Cc: Nathan Whitehorn , "Simon J. Gerraty" , 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 03:22:03 -0000 On Sun, Mar 29, 2020 at 10:16 PM Rebecca Cran wrote: > > > > On Mar 29, 2020, at 9:11 PM, Nathan Whitehorn wrote: > > > > 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. > > But at the moment how often do users mount the ESP and update loader.efi on it? So it seems it rarely _needs_ to be updated at the moment. > The interpreter developer in me wants this to be more frequent than it probably is. =-) Right now, we have to plan on optionally supporting any new features that we end up adding to the interpreter itself (e.g. lua C modules). I can think of one at the moment that will be joining us in the coming months -- while a bad example because this particular module will only be presented if the system supports it, it'd be nice to not have to have optional shims for old loaders for years on end.