[linuxrebe1]

I'm curious if they're proposal will be capable of handling multi-os boots. I know grub can, I can have Linux and windows and possibly even a third OS if I want. I am concerned that red hats solution the well-intended, may be rather myopic, and be commercial only. What I failed to understand, is what problem this solves for systems that I probably only reboot once or twice a year. (Given that it only works with Linux only systems)

[FredFS456]

You can switch OS's using the UEFI menu instead. It's not always convenient, depending on your UEFI implementation, however.

[bootsmann]

The issue it solves, according to the talk, is that grub presents a fairly big attack surface for something that is sparsely maintained and that could be done in the kernel, which has a lot of active devs.

[ack_complete]

Yeah, look at Windows 10 if you want to see how this can be done poorly. Its boot menu works by booting Windows 10 first and then restarting the computer if you choose another OS. This includes going all the way through POST again. Took something like two minutes end-to-end to get to Windows 7.

[zamadatix]

I'm not sure I experienced the same with the Windows boot loader so maybe that behavior was something case specific instead of intended?

[ack_complete]

Not sure, there might have been a fast path if you were booting to another Windows 10 install. The old legacy Windows Boot Manager also doesn't have the issue since it's much simpler and it executes in faux text mode before the OS boots.

[kasabali]

That's the default behavior

[fuzzfactor]

If you Bcdedit, that is known as "Standard" bootmenupolicy, which is touch-screen compatible and it has to reboot in order to reach an alternative OS selection other than the current bootmgr default.

If you bcdedit to be "Legacy" bootmenupolicy, you can select any OS from its simple non-touch text-based NT6 multiboot menu and it will boot right away without need for repost.