All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Peter Teoh <htmldeveloper@gmail.com>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: RFC: Self-snapshotting in Linux
Date: Thu, 17 Apr 2008 11:33:53 +0200	[thread overview]
Message-ID: <20080417093353.GC7314@elf.ucw.cz> (raw)
In-Reply-To: <804dabb00804160821n4872c65fh44f2c07ead67fc49@mail.gmail.com>

On Wed 2008-04-16 23:21:05, Peter Teoh wrote:
> Thank you for your reply.
> 
> Just some questions...
> 
> On 4/16/08, Pavel Machek <pavel@ucw.cz> wrote:
> > > Sorry if this is a a crazy idea.....just be forewarned....
> >  >
> >  > First, I would like to make a reference to VMWare's snapshot (name not
> >  > important, emphasize the idea) feature - hopefully u are familiar with
> >  > it.   This is a feature whereby u can freeze the entire OS (kernel +
> >  > userspace application running) and then later reload itself next time,
> >  > continuing where it left off, without reboot from ground zero.
> >  >
> >  > Next, can I ask, is such a feature useful in Linux?   Ie, able to
> >  > restart the kernel + userspace application from where u left off, the
> >  > last time round.    Not JUST the normal suspend/resume feature, but
> >  > more important able to CHOOSE among the different available images
> >  > for
> >  > u to resume on.   Eg, u want to freeze the current 2.6.25-rc6
> >  > kernel,
> >
> >
> > Could we use english on this list?
> >
> >  Anyway, hibernate, cp /dev/root /somewhere/root.1; cp /dev/swap
> >  /somewhere/swap.1
> >
> 
> The current userspace suspend actually saved the entire state of the
> memory (which applications are oepne/closed) into the swap area,
> right?

> So the 2nd line above of backingup the swap should allow us to restore
>  back state of the userspace applications later - correct?

Yes, but you need to match memory state with filesystem state...
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  parent reply	other threads:[~2008-04-17 10:00 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-16  8:44 RFC: Self-snapshotting in Linux Peter Teoh
2008-04-16  8:49 ` eric miao
2008-04-16  9:49 ` Ben Nizette
2008-04-16 10:33 ` Scott Lovenberg
2008-04-16 11:14 ` Pavel Machek
     [not found]   ` <804dabb00804160821n4872c65fh44f2c07ead67fc49@mail.gmail.com>
2008-04-17  9:33     ` Pavel Machek [this message]
2008-04-16 18:31 ` Greg Freemyer
     [not found] <ajbvb-3Ur-21@gated-at.bofh.it>
     [not found] ` <ajcri-65w-13@gated-at.bofh.it>
2008-04-16 10:27   ` Alan Jenkins
2008-04-16 11:12     ` Pavel Machek
2008-04-16 13:50       ` Alan Jenkins
2008-04-17  9:32         ` Pavel Machek
2008-04-19 16:42           ` Alan Jenkins
2008-04-17  0:55     ` Nigel Cunningham
2008-04-17  7:48       ` Alan Jenkins
     [not found] ` <ajd42-7Gt-49@gated-at.bofh.it>
2008-04-16 11:02   ` Alan Jenkins
2008-04-16 15:06     ` Peter Teoh
2008-04-16 16:21       ` Disconnect
2008-04-16 19:50       ` Vivek Goyal
     [not found]         ` <48065C64.7010808@gmail.com>
2008-04-16 20:10           ` Scott Lovenberg
2008-04-16 20:25           ` Vivek Goyal
2008-04-17  2:09             ` Scott Lovenberg
2008-04-17  6:23           ` Peter Teoh
2008-04-17  8:43             ` Alan Jenkins
2008-04-17 16:01               ` Scott Lovenberg

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=20080417093353.GC7314@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=htmldeveloper@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 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.