Date: Fri, 18 Jan 2019 08:12:24 -0700 From: Warner Losh <imp@bsdimp.com> To: Kurt Jaeger <pi@opsec.eu> Cc: Rebecca Cran <bcran@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: UEFI, loader.efi and /boot.config Message-ID: <CANCZdfp=EkKKA%2ByBzMMUu01sjAV71g4XQxgeh8JWDvA%2B%2BngZww@mail.gmail.com> In-Reply-To: <20190118074802.GA54920@home.opsec.eu> References: <etPan.5c413a8a.7a8e2073.13b3@freebsd.org> <20190118074802.GA54920@home.opsec.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jan 18, 2019, 12:49 AM Kurt Jaeger <pi@opsec.eu wrote: > Hi! > > > With a recent change I made for UEFI, we now install loader.efi onto the > ESP and don???t run boot1. That means that /boot.config is no longer read, > and so console settings need to be put in /boot/loader.conf > > Which change is that ? > Moving from boot1.efi to loader.efi. loader.efi never looked at it. loader.efi honors the uefi env vars to set the console which replaces the old way. Warner > I was wondering if people will expect /boot.config to still be read and > so code should be added to loader to continue to parse it, or if > loader.conf can be considered the correct place and boot.config forgotten > about? > > I have quite a few systems using /boot.config, but can cope if I know > about this. > > -- > pi@opsec.eu +49 171 3101372 One year to go ! > _______________________________________________ > 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" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfp=EkKKA%2ByBzMMUu01sjAV71g4XQxgeh8JWDvA%2B%2BngZww>