11.09.2015 17:53, Arthur Mesh пишет:
On 9/11/15, 7:32 AM, "grub-devel-bounces+amesh=juniper....@gnu.org on behalf of Andrei
Borzenkov" <grub-devel-bounces+amesh=juniper....@gnu.org on behalf of
arvidj...@gmail.com> wrote:
10.09.2015 03:11, Arthur Mesh пишет:
Add `--enable-efi-watchdog' configure argument, which defaults to Off.
When enabled, efi watchdog will not be disabled.
Otherwise, efi watchdog will be disabled.
Please, no. This will result in incompatible binaries without any
indication at run-time that allows to distinguish between them.
That's true, but I see no way around that w/o avoiding the initial call to
disable the watchdog in the efi init routine (and Vladimir is against that
idea).
Create a command line interface to enable/disable watchdog:
efi-watchdog (enable|disable) <timeout>
Why is it not enough? You can always add it to your grub.cfg.
Well, it still leaves a window of time where the system operates w/o a watchdog.
It could be a problem if grub.cfg resides on a network file system, and is not
accessible, in which case the system would hang.
I'm fine with making it controlled by parameter passed to grub
invocation or EFI variable. We discussed parameters several times but
did not come to definitive conclusion hos interface should look like.
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
