From: Valdis.Kletnieks@vt.edu
To: Steven Cole <elenstev@mesatop.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
linux-kernel@vger.kernel.org, Larry McVoy <lm@bitmover.com>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: Kernel hot-swap using Kexec, BProc and CC/SMP Clusters.
Date: Mon, 05 May 2003 14:17:57 -0400 [thread overview]
Message-ID: <200305051817.h45IHwJC003355@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Mon, 05 May 2003 12:00:15 MDT." <1052157615.2163.113.camel@spc9.esa.lanl.gov>
[-- Attachment #1: Type: text/plain, Size: 579 bytes --]
On Mon, 05 May 2003 12:00:15 MDT, Steven Cole said:
> Perhaps two uptimes could be kept. The current concept of uptime would
> remain as is, analogous to the reign of a king (the current kernel), and
> a new integrated uptime would be analogous to the life of a dynasty. The
> dynasty uptime would be one of the many things the new kernel learned
> about on booting. This new dynasty uptime could become quite long if
> everything keeps on ticking.
Make sure you handle the case of a dynasty that starts on a 2.7.13 kernel
and is finally deposed by a power failure in 2.7.39.
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2003-05-05 18:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-05 13:18 Kernel hot-swap using Kexec, BProc and CC/SMP Clusters Steven Cole
2003-05-05 14:22 ` Karim Yaghmour
2003-05-05 17:34 ` Eric W. Biederman
2003-05-05 18:00 ` Steven Cole
2003-05-05 18:17 ` Valdis.Kletnieks [this message]
2003-05-05 19:51 ` Steven Cole
2003-05-05 20:25 ` Richard B. Johnson
2003-05-05 18:16 ` Chris Friesen
2003-05-06 1:28 ` Steven Cole
2003-05-06 3:19 Stephen M. Kenton
2003-05-06 9:49 ` Eric W. Biederman
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=200305051817.h45IHwJC003355@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=ebiederm@xmission.com \
--cc=elenstev@mesatop.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--cc=torvalds@transmeta.com \
/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).