All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Newall <davidn@davidnewall.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Failover Kernel
Date: Tue, 03 Mar 2009 13:59:55 +1030	[thread overview]
Message-ID: <49ACA433.5050400@davidnewall.com> (raw)
In-Reply-To: <49AC0799.5060306@turknet.net.tr>

Tarkan Erimer wrote:
> the point is not to make boot when crash occured. The idea is to take
> control when a crash occured by backup kernel without any need to reboot.

It sounds like you want everything to just continue running.  I don't
see how that can be done.  All of those in-kernel tables and structures
would need to be migrated, and it follows, because there was a crash,
that any of them might have been corrupted.  Worse, you want this to
save you when you try running a new kernel which crashes, and being a
new kernel, it follows that any of those structures could be different;
it might not be possible to create equivalent structures for different
kernel versions.

If you're at all concerned at keeping the computer running, and I think
that's your goal, then I think the best you can do is reset the
hardware, boot an alternate kernel and restart applications as appropriate.

  reply	other threads:[~2009-03-03  3:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-26  8:58 Failover Kernel Tarkan Erimer
2009-02-26 16:03 ` Willy Tarreau
2009-02-27 15:25   ` Tarkan Erimer
2009-02-26 17:02 ` Diego Calleja
2009-02-27 15:32   ` Tarkan Erimer
2009-02-27 15:50     ` Lubomir Rintel
2009-03-02 16:21       ` Tarkan Erimer
2009-03-03  3:29         ` David Newall [this message]
2009-03-04  8:29           ` Tarkan Erimer
2009-03-06  1:10             ` david
2009-03-09 12:35               ` Tarkan Erimer

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=49ACA433.5050400@davidnewall.com \
    --to=davidn@davidnewall.com \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.