From: Dave Jones <davej@redhat.com>
To: Pau Garcia i Quiles <pgquiles@elpauer.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [IDEA] Poor man's UPS
Date: Sun, 21 May 2006 15:38:03 -0400 [thread overview]
Message-ID: <20060521193803.GG8250@redhat.com> (raw)
In-Reply-To: <200605212131.47860.pgquiles@elpauer.org>
On Sun, May 21, 2006 at 09:31:30PM +0200, Pau Garcia i Quiles wrote:
> A short description would be "continuous system hibernation". Say you are
> running Firefox, writing an e-mail in mutt and compiling the next X.org
> release. The power goes off, your computer crashes or something happens and
> you lose everything you were doing (yes, sadly you haved saved your e-mail as
> a draft yet).
>
> The "continuous hibernation" is some kind of memory snapshots taken, say,
> every 5 minutes. The next time your system starts after a crash, it'd say "oh
> oh, looks like something went wrong" and offer you a list of the last N (for
> instance, 4) snapshots and you can recover your system to the very same state
> it was before power went off or your dog unplugged your CPU. It might even
> ask you which individual applications you want to start from that snapshot:
> maybe you don't want to start Quake 3.
>
> Provided the implementation is fast enough and you have a large hard drive, it
> might even allow you to say: "I want to restore the system to the same stage
> it had on Monday, 11.04PM"
>
> That's it. Please, shoot at the idea not at the idealist :-)
One problem is that the on-disk state may not match the state
of the running programs on resume, which could lead to all sorts
of bad things happening.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-05-21 19:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-21 19:31 [IDEA] Poor man's UPS Pau Garcia i Quiles
2006-05-21 19:38 ` Dave Jones [this message]
2006-05-21 19:46 ` Michael Buesch
2006-05-22 8:19 ` Avi Kivity
2006-05-22 10:54 ` Jan Engelhardt
2006-05-21 22:40 ` Christian Trefzer
2006-05-22 13:04 ` Jan Knutar
2006-05-22 13:29 ` linux-os (Dick Johnson)
2006-05-22 15:25 ` Christian Trefzer
2006-05-22 15:54 ` linux-os (Dick Johnson)
2006-05-22 19:34 ` Christian Trefzer
2006-05-22 15:13 ` Christian Trefzer
2006-05-22 15:40 ` Alan Cox
2006-05-22 15:48 ` Christian Trefzer
2006-05-22 16:15 ` Matthias Schniedermeyer
2006-05-22 19:40 ` Christian Trefzer
2006-05-22 19:45 ` Avi Kivity
2006-05-23 2:02 ` Martin J. Bligh
2006-05-22 19:46 ` Nuri Jawad
2006-05-22 22:40 ` Christian Trefzer
2006-05-22 17:05 ` Jeff V. Merkey
2006-05-21 23:02 ` Neil Brown
2006-05-22 0:08 ` Chris Wedgwood
2006-05-22 0:23 ` Neil Brown
2006-05-22 1:29 ` Björn Steinbrink
2006-05-22 1:44 ` Neil Brown
2006-05-22 9:29 ` Pavel Machek
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=20060521193803.GG8250@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pgquiles@elpauer.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