[Bug 913336] Re: grub-common recreates /etc/grub/grubenv

[Richard Laager]

This patch is not sufficient, as grub-install calls grub-editenv
/boot/grub/grubenv create unconditionally. I've attached another patch
which stops grub-install from creating grubenv when /boot/grub is on
ZFS.

If we care about the possible use case of an admin who doesn't want
grubenv, further work will be required; otherwise it'll come back on
every GRUB package upgrade. However, this use case isn't covered now, so
I'd hate to see the ZFS fix held up on that.

** Patch added: "zfs-no-grubenv.patch"
   https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/913336/+attachment/2665403/+files/zfs-no-grubenv.patch

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/913336

Title:
  grub-common recreates /etc/grub/grubenv

Status in “grub2” package in Ubuntu:
  Confirmed

Bug description:
  /etc/init.d/grub-common and /etc/pm/sleep.d/10_grub-common call grub-
  editenv to clear the recordfail setting to indicate that the system
  booted or awoke successfully. They call grub-editenv, which creates
  the grubenv file if it doesn't exist.

  If the admin has deleted the grubenv file intentionally because they
  don't want grub writing to the filesystem, this behavior is annoying.
  If the admin has deleted the file because grub does not have write
  support for the root filesystem, then this behavior breaks booting;
  someone has to hit a key on the console for the machine to boot.

  The attached patch fixes this. However, I'm not sure what is supposed
  to create /boot/grub/grubenv originally. If it's the init script, then
  some further changes will be required.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/913336/+subscriptions