From: Arthur Mesh <amesh@juniper.net>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH] Remove unconditional disablement of the watchdog
Date: Wed, 9 Sep 2015 08:53:00 -0700 [thread overview]
Message-ID: <20150909155300.GK87550@juniper.net> (raw)
In-Reply-To: <55EF0FE0.4060207@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 702 bytes --]
On Tue, Sep 08, 2015 at 09:42:08AM -0700, Vladimir '??-coder/phcoder' Serbinenko wrote:
> This patch will break any current config on systems with watchdog.
That's true.
> You need to ensure that:
> a) watchdog timeout is plenty to load config file even on very slow
> netboot systems.
Is there a way to achieve that programaticly and not defeat the purpose
of the watchdog? I tend to think the answer is no.
> b) disable watchdog if the config didn't opt-in to have the watchdog.
How about we leave the disabling of watchdog as is today, and instead
provide means to re-enabling it via cfg?
Thanks!
--
Arthur Mesh <amesh@juniper.net>
Juniper Networks
+1 408 936-4968
[-- Attachment #2: Type: application/pgp-signature, Size: 648 bytes --]
prev parent reply other threads:[~2015-09-09 16:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 14:51 [PATCH] Remove unconditional disablement of the watchdog Arthur Mesh
2015-09-08 16:42 ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-09-09 15:53 ` Arthur Mesh [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150909155300.GK87550@juniper.net \
--to=amesh@juniper.net \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).