| 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
| ||
|
Message-ID: <20070503151408.GC3866@ucw.cz> Date: Thu, 3 May 2007 15:14:09 +0000 From: Pavel Machek <pavel@....cz> To: Jeremy Fitzhardinge <jeremy@...p.org> Cc: Matthew Garrett <mjg59@...f.ucam.org>, Linus Torvalds <torvalds@...ux-foundation.org>, "Rafael J. Wysocki" <rjw@...k.pl>, Pekka J Enberg <penberg@...helsinki.fi>, Nigel Cunningham <nigel@...el.suspend2.net>, LKML <linux-kernel@...r.kernel.org> Subject: Re: Back to the future. Hi! > > While that would certainly be nifty, I think we're arguably starting > > from the wrong point here. Why are we booting a kernel, trying to poke > > the hardware back into some sort of mock-quiescent state, freeing memory > > and then (finally) overwriting the entire contents of RAM rather than > > just doing all of this from the bootloader? Doing it from the bootloader sounds attractive... but it is lot of work. I'm essentially using linux as a bootloader. Patch for grub welcome. > Sure, you could make suspend generate a complete bootable kernel image > containing all RAM. Doesn't sound too hard to me. You know, from over > here on the sidelines. Ah, so we have a volunteer :-). Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html - 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