Date: Sat, 16 Dec 2017 10:31:35 -0500 From: Eric McCorkle <eric@metricspace.net> To: Warner Losh <imp@bsdimp.com> Cc: "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org>, Warner Losh <imp@freebsd.org>, Allan Jude <allanjude@freebsd.org> Subject: Re: loader.efi architecture for replacing boot1.efi Message-ID: <23c05735-4046-a41f-676c-877d9f07d5f8@metricspace.net> In-Reply-To: <CANCZdfo3Q_z1%2BO=VqUNcvPnyL%2BMFDnzzv5GWKbPdu8O-ZsQPyQ@mail.gmail.com> References: <1fa7edde-6ac0-1d4f-e75a-503b23a5d4dc@metricspace.net> <CANCZdfpJm9MjxvO4dPy7qZ4jjot44yAMj7NhaY_MQ5z7WVbd9A@mail.gmail.com> <46af04dd-8f74-b9dc-3d3a-343f022129ed@metricspace.net> <CANCZdfrpi3JTDxo17RBiLdZ=UjdPF3FgpqwmBepZ=8k5-P0F2g@mail.gmail.com> <CANCZdfr0=WzVkUb85o2aUT3eA7EAAx4MCnQy6gk8XdeJvb9tsA@mail.gmail.com> <ef64c1b9-024d-dce9-d620-c47ab7921fd6@metricspace.net> <CANCZdfo3Q_z1%2BO=VqUNcvPnyL%2BMFDnzzv5GWKbPdu8O-ZsQPyQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/16/2017 00:49, Warner Losh wrote: > CD/DVD booing won't break. We'll still load a kernel from them. No > boot.config needed for this case (though it might be for others). How is that possibly going to work for a liveDVD on a random system? People expect it to "just work" (meaning, it correctly guesses the kernel, then loads it). I can see it working with boot.config (which I'd be fine with), but if we don't search the CD drives, there's no way it can work. > But for now, loader.efi has got to work whether installed > in a boot1/loader (legacy) configuration, or installed directly to the > ESP. Otherwise, there's going to be a lot of unhappy people out there. > > Correct. My proposed behavior will do just that, and if we get it wrong > by default (a) you can be explicit with boot variables or (b) you can > type something into the OK prompt, which you didn't have before. No, I'm talking about people with existing installations, which still have both boot1 and loader.efi. A change this big needs to be phased in over time, which means both modes of operation need to be supported for a while. > As for the fallback search, it's just that: a fallback mechanism. Its > job is to make a sane guess as to where to find the system, but > ultimately it's not doing anything the user can't do themselves. And it > will only run if the EFI vars aren't set anyway, so it can't possibly > interfere with any of that. > > > And the fallback mechanism of typing what you want is wrong because? Because every single person out there with an install is going to suddenly have to type, and that's going to lead to a whole bunch of people saying we broke loader. > But it's job isn't to guess. If we don't know for sure what to boot, it's > our job to fail so the next OS in the list gets a shot at booting. That won't happen though. If loader fails to find an installed system, it drops out to a prompt, but it doesn't exit. Given that, it makes sense to make an effort at finding an installed system.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?23c05735-4046-a41f-676c-877d9f07d5f8>