This is easier with rEFInd than with systemd-boot because the latter can only launch programs from the partition on which it resides, and Linux kernels don't ordinarily reside on that partition under Ubuntu.
A final twist on this is that the Linux kernel can function as its own EFI boot loader, so if you use a pure boot manager, you can omit GRUB2 entirely when booting Ubuntu.
CONFIGURE WINDOWS 10 LOADER INSTALL
If you install either of these tools, it will become your primary boot manager, and it will then hand off control to either the Windows boot loader or a Linux boot loader. Both GRUB2 and the Windows boot loader perform both tasks, but some programs perform just one task or the other.) You don't say why you prefer the Windows boot manager to GRUB2, so I can only guess at what you might like however, my suspicion is that you be interested in gummiboot (now called systemd-boot) or my own rEFInd. (A boot manager presents a menu with a list of OS boot options a boot loader loads a kernel into memory and executes it. Technically, what you're interested in is a boot manager, not a boot loader. That said, there are alternatives to both GRUB2 and the Windows boot loader.
CONFIGURE WINDOWS 10 LOADER HOW TO
Most Ubuntu users run GRUB2 as their primary boot loader, and have little knowledge of how to configure the Windows boot loader. This can be done (or so I hear), but you should ask about it on a Windows forum, since that's fundamentally a Windows question, not an Ubuntu question. What you're asking for, then, is how to make the Windows boot loader the primary boot loader - that is, the one whose menu you see when the computer starts up.
To boot Windows from GRUB2, GRUB2 launches the Windows boot loader and to boot Ubuntu (or any Linux distribution) from the Windows boot loader, it launches GRUB2. Ordinarily, you'll use both GRUB2 and the Windows boot loader, because GRUB2 cannot launch a Windows kernel directly and the Windows boot loader cannot launch a Linux kernel directly.
0 kommentar(er)
