Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 29 Mar 2020 22:21:37 -0500
From:      Kyle Evans <kevans@freebsd.org>
To:        Rebecca Cran <rebecca@bsdio.com>
Cc:        Nathan Whitehorn <nwhitehorn@freebsd.org>, "Simon J. Gerraty" <sjg@juniper.net>,  Tomoaki AOKI <junchoon@dec.sakura.ne.jp>, FreeBSD Current <FreeBSD-current@freebsd.org>, bsd-lists@bsdforge.com
Subject:   Re: When will the FreeBSD (u)EFI work?
Message-ID:  <CACNAnaFkKbQ9zGkjLWHL0NV2v=GPY9B0uSD6niA%2B-iwKv-zkqw@mail.gmail.com>
In-Reply-To: <4C050E22-E571-47ED-87A1-FE1BAC69A073@bsdio.com>
References:  <18df34fe-6256-6e68-ead5-481e83a501fe@freebsd.org> <4C050E22-E571-47ED-87A1-FE1BAC69A073@bsdio.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Mar 29, 2020 at 10:16 PM Rebecca Cran <rebecca@bsdio.com> wrote:
>
>
> > On Mar 29, 2020, at 9:11 PM, Nathan Whitehorn <nwhitehorn@freebsd.org> 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.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACNAnaFkKbQ9zGkjLWHL0NV2v=GPY9B0uSD6niA%2B-iwKv-zkqw>