From: Thomas Tuttle <thinkinginbinary@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Preserving uptime with kexec?
Date: Mon, 31 Jul 2006 08:59:13 -0400 [thread overview]
Message-ID: <20060731125913.GA27083@phoenix> (raw)
[-- Attachment #1: Type: text/plain, Size: 635 bytes --]
Like many people, I like to brag about how great my uptime is. But like
many other people, I like to keep my kernel up-to-date with the latest
and greatest from kernel.org. I recently discovered the magic of kexec,
which allows me to switch kernels without rebooting for real.
Unfortunately, kexec resets my uptime when it runs.
Would anyone be interested in fixing this, and/or would anyone be
interested in *me* writing a patch for it? I don't know if it violates
some contract where uptime is counted from the kernel boot, but it seems
like, for consistency's sake, it should count from the last hardware
boot.
--Thomas Tuttle
[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]
next reply other threads:[~2006-07-31 12:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-31 12:59 Thomas Tuttle [this message]
2006-07-31 14:12 ` Preserving uptime with kexec? Valdis.Kletnieks
2006-07-31 15:46 ` Nick Warne
2006-07-31 16:28 ` Jan Engelhardt
2006-07-31 16:40 ` Nick Warne
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=20060731125913.GA27083@phoenix \
--to=thinkinginbinary@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox