[Bug 1226122] TW installation with bootloader not managed leaves /boot/ empty when suse-module-tools-scriptlets not installed instead of sdbootutil-rpm-scriptlets
https://bugzilla.suse.com/show_bug.cgi?id=1226122 https://bugzilla.suse.com/show_bug.cgi?id=1226122#c58 --- Comment #58 from Alberto Planas Dominguez <aplanas@suse.com> --- (In reply to Mario Guzman from comment #57)
After reading up on sdbootutil I see it would be very bad for multi boot environments such as mine.
I cannot help with the installer, but I think I can help with sdbootutil. I am not a multiboot user, so I am lacking a lot of insight here too. I have some initial questions: 1) What is particularly bad about sdbootutil in multiboot environments? It takes care of installing the boot loader (that must be user commanded) and creating the entries for the distribution. 2) In a multiboot system, who is expected to create the boot entries? sdbootutil is doing this because it is not easy to decide the snapshot that should be used to extract the kernel from 3) How can sdbootutil help? -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com