I'd like to know why an explicit create is necessary for you, as 'grub-editenv /boot/grub/grubenv unset recordfail' will create the environment block implicitly, as verified from the code and demonstrated here:
$ rm -f grubenv $ grub-editenv grubenv unset recordfail $ ls -l grubenv -rw-r--r-- 1 cjwatson cjwatson 1024 2009-10-01 16:17 grubenv
Where did you make your change? I put this line above '... unset recordfail' in /etc/init.d/grub-common:
[ -s /boot/grub/grubenv ] || rm -f /boot/grub/grubenv
I'd like to know why an explicit create is necessary for you, as
'grub-editenv /boot/grub/grubenv unset recordfail' will create the
environment block implicitly, as verified from the code and demonstrated
here:
$ rm -f grubenv
$ grub-editenv grubenv unset recordfail
$ ls -l grubenv
-rw-r--r-- 1 cjwatson cjwatson 1024 2009-10-01 16:17 grubenv
Where did you make your change? I put this line above '... unset d/grub- common:
recordfail' in /etc/init.
[ -s /boot/grub/grubenv ] || rm -f /boot/grub/grubenv