http://bugzilla.suse.com/show_bug.cgi?id=1156441 http://bugzilla.suse.com/show_bug.cgi?id=1156441#c8 Fabian Vogt <fvogt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(fvogt@suse.com) | --- Comment #8 from Fabian Vogt <fvogt@suse.com> --- (In reply to Michael Chang from comment #7)
Think it twice, I am still reluctant to patch grub2-install as the potential conflict in usage of /boot/grub2/grubenv with other application that expects it to be otherwise, like symlink or such.
grubenv should be managed by grub only, if other tools break it later that's IMO a bug in those tools. As long as grub2-install only creates grubenv with env_block if it didn't exist before, I do not see any problem here.
Shouldn't the application whichever requires the /boot/grub2/grubenv to run holds the responsibility to initialize it ? What's the difficulty doing that ?
I've got three reasons: 1. grubenv is a core feature of grub, which should always be available anyway 2. Only grub2-install knows where and how (btrfs vs. non-btrfs) to initialize it 3. How should applications do that? The rpm's %post script might not even run on the target system. This is the case for kiwi image builds for instance.
Thanks for your patience.
-- You are receiving this mail because: You are on the CC list for the bug.