http://bugzilla.suse.com/show_bug.cgi?id=1167780 http://bugzilla.suse.com/show_bug.cgi?id=1167780#c1 Fabian Vogt changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |snwint@suse.com Flags| |needinfo?(snwint@suse.com) --- Comment #1 from Fabian Vogt --- @snwint: As perl-Bootloader maintainer, would it be possible to have some autodetection whether to update/install grub2/grub2-efi? If not, I'll try to refactor the snippet in jeos-firstboot which adjusts LOADER_TYPE on JeOS and shove it into a systemd firstboot service in a subpackage. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1167780 http://bugzilla.suse.com/show_bug.cgi?id=1167780#c3 --- Comment #3 from Steffen Winterfeldt --- Or even a new LOADER_TYPES var in sysconfig that holds a list of loaders. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1167780 http://bugzilla.suse.com/show_bug.cgi?id=1167780#c5 --- Comment #5 from Steffen Winterfeldt --- It's the long standing debate why there's a grub2-efi at all. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1167780 http://bugzilla.suse.com/show_bug.cgi?id=1167780#c7 --- Comment #7 from Steffen Winterfeldt --- Having three variants like grub2, grub2-legacy, grub2-efi might be more logical to begin with. grub2 would imply some autodetection and the other two are for enforcing something else. But as said, a lot of people will have some opinion here. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1167780 http://bugzilla.suse.com/show_bug.cgi?id=1167780#c9 --- Comment #9 from Steffen Winterfeldt --- grub2-auto looks weird to me. In any case, to have a new LOADER_TYPE you'd have to get the involved parties together to have a chat. Going for grub2 (= auto) and, e.g. grub2-xxx with xxx = something related to those grub2 subpackage names looks more natural to me. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1167780 http://bugzilla.suse.com/show_bug.cgi?id=1167780#c12 --- Comment #12 from Fabian Vogt --- (In reply to Steffen Winterfeldt from comment #10)

But if you want a specialized solution just for microos and are sure no-one else will look at LOADER_TYPE: supporting grub2-auto on the pbl side just means adding scripts in /usr/lib/bootloader/grub2-auto that delegate to their grub2 resp grub2-efi counterpart.

Then I'd just use the jeos-firstboot snippet to set it based on the type of the first boot. Otherwise I'd have to maintain a pbl script forever, just for MicroOS. It's also possible that someone installs yast on microos, so I can't even be sure that LOADER_TYPE isn't read by anything else. (In reply to Neil Rickert from comment #11)

Just a note on this.

I have Tumbleweed installed on an external USB drive, for booting with either MBR/BIOS booting or UEFI booting. Installing that way works (the install succeeds) even if the installer is booted with UEFI.

This would be a use case for having both targets installed, but with one important difference: "--removable". If efivarfs is available, "grub2-efi" with SECURE_BOOT=yes would not install into /EFI/BOOT but /EFI/opensuse and create a boot entry for it. -- You are receiving this mail because: You are on the CC list for the bug.

https://bugzilla.suse.com/show_bug.cgi?id=1167780 https://bugzilla.suse.com/show_bug.cgi?id=1167780#c15 --- Comment #15 from Steffen Winterfeldt --- Looking at the original problem: you set up an image and boot it with a boot loader that does not match the stored type. And then want pbl to update the 'correct' boot config. 'correct' being the loader last used, assuming you never change your mind in the future. Wouldn't it be more straightforward to have a systemd service run the first time that adjusts the loader type (or maybe even always)? Or simply disallow legacy booting. BTW, aren't you aiming for systemd-boot for micro-os anyway in the future? -- You are receiving this mail because: You are on the CC list for the bug.