On Fri, May 8, 2020 at 4:45 PM Stefan Seyfried <stefan.seyfried@googlemail.com> wrote:
Am 08.05.20 um 13:58 schrieb Carlos E. R.:
Thus, in a multiboot environment there are two possibilities:
- grub is updated on all bootable partitions to keep track of the actual kernels that exist in every other bootable (Linux) partition.
- Just have one entry per bootable partition using the symlink. No need to update them each time there is a kernel update on another Linux partition.
There is at least a third possibility for working multiboot: * install each OS's bootloader (does not need to be grub, can be ntldr or whatever) into its own boot partition * have one "first stage boot loader" that only chainloads these bootloaders from the other partitions. Install that boot loader into the MBR.
Yes. This is the only sane way to multiboot. This is actually what original os-prober was about - it chainloaded foreign OS *bootloader*. It is unfortunate that later os-prober was misused to parse foreign OS bootloader configuration instead.
* activate the windows partition (important, or windows will sooner or later fail horribly with updates)
Never again worry about an error in one distribution's GRUB setup causing all other multiboot installations fail to boot. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org