| 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: <20090510053820.GF1363@ucw.cz> Date: Sun, 10 May 2009 07:38:21 +0200 From: Pavel Machek <pavel@....cz> To: Shannon McMackin <smcmackin@...il.com> Cc: linux-kernel@...r.kernel.org, tuxonice-devel@...ts.tuxonice.net Subject: Re: [TuxOnIce-devel] [RFC] TuxOnIce Hi! >>> To summarise disadvantages: >>> >>> - only core has 8000 LoC >>> - it does stuff that can be easily done in userspace >>> (and that todays distros _do_ in userspace). >>> - it duplicates uswsusp functionality. >>> - compared to [u]swsusp, it received little testing >>> >> >> To summarise advatages - for me tuxonice is the only hibernation method that works. >> (Till now I've had 3 machines - no one of them able to resume with in-kernel swsusp.) >> > Just to add my 2 cents as a user of TOI. Every distro and release I've > tried has one major issue with kernel hibernation. Upon resume when > hibernating large images, there's a residual footprint in swap. Every > further hibernation creates a larger footprint, to the order of an > additional 5-7% each time. Nobody has ever cared in any forum to > explain why or how I might change that. Maybe you should explain why it is a 'major issue'? (Use swapoff -a; swapon -a to 'cure' it). 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