On 18/08/2019 18.03, zb4ng wrote:
Am 18.08.19 um 15:44 schrieb Carlos E. R.:
On 17/08/2019 20.54, zb4ng wrote:
No, it doesn't.
You have to boot the system which controls grub and make it run os-prober so that it finds the actual kernel entries of the other system.
There are other ways.
You can manually edit the grub file that is intended for manual edit, and create an entry for the "vmlinuz" symlink this one is maintained by zypper.
Yeah it looks like I can use "menuentry" in /boot/grub2/custom.cfg and put the symlink in there?
Yes, that's the idea.
Or, after making sure that both installs have their own grub installed to the root partition, not to the MBR, add manually on each one (in the file intended for manual edit) an entry for the other grub, not to the kernel.
Maybe if I can't figure out grub configurationb , I'll try to add grub to my 15.1-system -(Do I have to move the existing Grub from MBR to 15.0?) - and see if they find each other.
Otherwise, I am ok with using the method mentioned in my earlier post.
This is one from me: menuentry '--> ssd-test' --id cer-ssd-001 { insmod part_gpt insmod ext2 set root='hd0,gpt3' if search --no-floppy --fs-uuid --set=root 32392d31... ; then chainloader +1 else echo Could not find this OS instance, will not boot (3) sleep 1 fi } About MBR: only one of the installed systems can use the MBR, so instead I give it to none. then I mark one partition as bootable. Works even on GPT with the proper code - linuxboot? Not sure of the package name. A generic MBR code for GPT disks. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)