07.11.2015 21:54, Arbiel (gmx) пишет:
In Ubuntu OSs, at least those I feel comfortable with, $recordfail is used to remember the failure of a boot process. It is set by grub.cfg and probably reset after grub has released control to the booted OS. At least, as it cannot be reset by the grub "boot" command, which does not know anything about it, it has to be released somewhere down the control chain. The fact that it is not reset at boot time means that the preceding boot process has failed, and some specific action can then be taken.
The only affect it has is to present boot menu even if otherwise disabled, so in principle it is safe to leave. But still ...
bor@bor-Latitude-E5450:~/src/topgit-master$ grep -rw recordfail /etc/init.d /etc/init.d/grub-common: grub-editenv /boot/grub/grubenv unset recordfail bor@bor-Latitude-E5450:~/src/topgit-master$
Regarding grubenv, and the fact that in some circonstances save_env will fail, does not appear in the documentation, at least the one I just accessed a few minutes ago at http://www.gnu.org/software/grub/manual/grub.html. No mention of any write restriction on some file systems or file organisations prevents the various system designers.
Well, documentation has to be written by someone. Send patches. No need to write treatise, even small additions, fixes and clarifications are helpful.
_______________________________________________ Help-grub mailing list [email protected] https://lists.gnu.org/mailman/listinfo/help-grub
