lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 16 Apr 2008 19:49:07 +1000 From: Ben Nizette <bn@...sdigital.com> To: Peter Teoh <htmldeveloper@...il.com> Cc: LKML <linux-kernel@...r.kernel.org>, Kernel Newbies <kernelnewbies@...linux.org> Subject: Re: RFC: Self-snapshotting in Linux 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 :-) --Ben. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists