From: Pavel Machek <pavel@ucw.cz>
To: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
Cc: Ben Nizette <bn@niasdigital.com>, linux-kernel@vger.kernel.org
Subject: Re: RFC: Self-snapshotting in Linux
Date: Wed, 16 Apr 2008 13:12:37 +0200 [thread overview]
Message-ID: <20080416111237.GA32432@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <da08e304-eb95-4ace-a069-de1a57b86e9f@e39g2000hsf.googlegroups.com>
> Ben Nizette wrote:
> > On Wed, 2008-04-16 at 16:44 +0800, Peter Teoh wrote:
> > > Essentially, to reiterate the key idea: able to snapshot the current
> > > kernel+userspace permanent.....restore from another snapshot....and
> > > then switch back again if needed etc.....will the implementation be
> > > difficult...if not impossible????
> > >
> >
> > As I see it the main thing is that VMWare doesn't have to worry about
> > trying to put hardware in to (and pull out of) low power modes. VMWare
> > hardware is never left in an undefined state by poorly written drivers
> > etc.
> >
> > I think hibernation is about what you want; snapshotting as you describe
> > it should fall down for about the same reasons
>
> I guess there is the hardware / drivers issue. I would like to claim
> I've found hibernation to be reliable but unfortunately that's not
> 100% true.
So debug it, it is open source after all. Or at least file a bugs.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-04-16 11:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
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
2008-04-16 8:44 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
2008-04-16 18:31 ` Greg Freemyer
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=20080416111237.GA32432@atrey.karlin.mff.cuni.cz \
--to=pavel@ucw.cz \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=bn@niasdigital.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
all inboxes | Powered by JetHome®