[Bug 1226676] Installation: kdump reports an error if systemd-boot has been selected for bootloader
https://bugzilla.suse.com/show_bug.cgi?id=1226676 https://bugzilla.suse.com/show_bug.cgi?id=1226676#c9 Jiri Bohac <jbohac@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(aplanas@suse.com) --- Comment #9 from Jiri Bohac <jbohac@suse.com> --- (In reply to Alberto Planas Dominguez from comment #8)
Another way would be for kdump to look for the kernels elsewhere.
I prefer this option. Now suse-module-tools-scriptlets knows about BLS and sdbootutil, that is used to install a new kernel, update initrd and create boot entries. For BLS the responsibility of synchronizing all the boot related stuff is moving into sdbootutil, that under the hood uses the data provided by bootctl, that is the real canonical source of information
canonical but for one loader only? That's not really what I'm looking for. I really like the output of pbl --default-settings Any chance this will work with systemd-boot? On a systemd-boot system it prints: Option --default-settings not available for systemd-boot. I would really like to have a truly universal way to give me a reasonable default kernel without caring which boot loader is being used. Until now this has been /boot/vmlinuz. Is there future in pbl, or something similar that would provide this information? -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com