On Mon, Feb 1, 2016 at 11:55 AM, Hans de Faber <hans.defaber@gmail.com> wrote:

Hello everybody, On my efi desktopsystem I have a multiboot environment with 3 flavours of opensuse and win10. 1. opensuse 13.2 the previous 2.leap42.1 the workhorse 3. tumbleweed the future 4. win10 for flightgear 5. system rescue disk

I set my efiboot variable always to leap42 the workhorse for everyday. Each installation is a complete install and has its own boot (grub) environment, unchanged.

Problem: After a kernel update the grub.cfg of the non updated versions point to the purged kernel

Question: Why points grub.cfg to a specific kernel an not to the logical link vmlinuz and initrd ?

Entry for "other" installed distributions are create by os-prober; they are simply textual copies from grub.cfg of "other" distribution made during grub-mkconfig run. After you changed grub.cfg in "other" distribution, you need to refresh "local" grub.cfg to pick up changes. You may consider using "master" bootloader that simply starts grub for each installed distribution and disabling os-prober in each. That way each grub is guaranteed to show updated menu. Another possibility would be to import grub.cfg for each distribution dynamically. I have not played with it, but this may work as long as "other" grub.cfg does not hardcode device locations anywhere. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org