linux-kernel - TuxOnIce 3.1

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Tue, 16 Mar 2010 11:57:03 +1100
From:	Nigel Cunningham <ncunningham@...a.org.au>
To:	tuxonice-announce@...ts.tuxonice.net,
	pm list <linux-pm@...ts.linux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>, lwn@....net
Subject: TuxOnIce 3.1

Hi all.

Almost a year since TuxOnIce 3.0 was announced, I'm pleased to announce 
a 3.1 release.

In the intervening period, lots of work has been done on the code. The 
major new features are:

- Support for LZO compression (deflate will also work, but it's slooow!)
- New sysfs entry making the sys_sync call in the freezer optional.
- Support for using swap AND file storage in the same image.
- Support for striped storage (swap priorities are now honoured and
   there's a new sysfs entry to set the priority of file storage).
- Binary signature now available through a sysfs entry (requires updated
   hibernate script).
- UUID support. This uses a simple table of UUID and filesystem
   signature offsets as the basis for scanning partitions for a TuxOnIce
   signature at resume time without the need for the resume= parameter.
   If more than one partition is used for storing the image, UUIDs will
   also be used for finding those partitions. This lets one user who had
   flakey device detection resume first time, every time, instead of
   having to reboot until the order is the same as that seen when
   hibernating. (New kernel commandline param: uuid_debug=1).
- (Extending the UUID support) Add support for checking last mount times
   of filesystems, and refusing to resume if a filesystem has been
   mounted since we hibernated. At the time of writing, we only know how
   to find these times for ext filesystems. (Note that the bytes don't
   need to be a mount time; they just need to be guaranteed to change
   if the filesystem is mounted in the meantime).
- We now display what storage from which devices was used in the image.
- Give an estimate of time remaining (text userui only at the moment).
- Reworked code which decides where the data will be loaded at resume
   time. Especially on machines with large amounts of memory, this will
   result in a signficant speed improvement in this phase of a cycle.

This release will be followed by updates to the hibernate script and 
userui so that they work without issue with 3.1 Once that's done, I 
intend to start focusing on seeking to improve the existing in-kernel 
implementation.

Regards,

Nigel
--
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/