http://bugzilla.opensuse.org/show_bug.cgi?id=1190567 http://bugzilla.opensuse.org/show_bug.cgi?id=1190567#c4 --- Comment #4 from Ludwig Nussel <lnussel@suse.com> --- (In reply to Marcus Schaefer from comment #3)
First question why ?
The OS moves to /usr and /usr only. Those symlinks are only created for compatibility until the tooling around bootloaders is adopted.
So this is not only about kiwi, this causes issues to anybody who installs the kernel outside of the target and deploy to target later.
Only if a separate /boot is used which is not the default setup as it doesn't work well with snapshots. Anyway any image builder needs to take special precautions for getting an image to boot. Means calling scripts to copy eg grub to the right location and creating a suitable initrd. The kernel is part of the boot process so now becomes another aspect to consider.
Is there an opportunity to recall the kernel post such that we can at least recall on target such that the code you have becomes effective ?
So far not but could be done easily if there's need for it (ie looping over /usr/lib/modules/*/vmlinuz). How does kiwi install the bootloader? Calling into perl-Bootloader? Might be possible to add code there too. -- You are receiving this mail because: You are the assignee for the bug.