Andrei Borzenkov composed on 2020-05-08 17:23 (UTC+0300):
Stefan Seyfried wrote:
Carlos E. R. composed:
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*.
Or employ <https://old-en.opensuse.org/Bugs/grub#How_does_a_PC_boot_.2F_How_can_I_set_up_a_working_GRUB.3F> using generic MBR code. On most systems I have a primary partition whose primary purpose is hosting a bootloader, in most cases, Grub Legacy, but not unusually the original multiboot loader, IBM Boot Manager. This primary partition with boot flag is admin managed, which requires trivial effort, in the Grub Legacy case via use of symlinks in stanzas loading kernels/initrds directly instead of chainloading. Mine contain also chainloading and configfile stanzas for convenient access to previous kernels/initrds. Because Fedora doesn't create any symlinks to its current kernels' initramfses, those installations require admin effort not applicable to openSUSE, Mageia or Debian & its derivatives for the direct load stanzas. -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org