Date: Mon, 25 Jun 2018 12:18:44 +0300 From: Konstantin Belousov <kostikbel@gmail.com> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: Warner Losh <imp@bsdimp.com>, "freebsd-arch@freebsd.org" <arch@freebsd.org> Subject: Re: UEFI Plans / Shifts -- RFC Message-ID: <20180625091844.GC2430@kib.kiev.ua> In-Reply-To: <19341.1529917294@critter.freebsd.dk> References: <CANCZdfoMZXJu2nRbAtLTPc1B4YWWbxsHQjX31zOo%2B8mDwMAQuA@mail.gmail.com> <19341.1529917294@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jun 25, 2018 at 09:01:34AM +0000, Poul-Henning Kamp wrote: > -------- > In message <CANCZdfoMZXJu2nRbAtLTPc1B4YWWbxsHQjX31zOo+8mDwMAQuA@mail.gmail.com> > , Warner Losh writes: > > >So here's my open questions: > >(1) Do I need to parse boot.conf? > > I can't see how it would add any value on top of UEFI and reading it > will just keeping old workarounds alive another decade for no good reason. An obvious values is to have serial console earlier than loader.conf is parsed. At least on typical desktop motherboards which do not have serial bios redirection, this is important.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180625091844.GC2430>