Hi,
Unfortunately in its current form s2disk causes the access time of the resume
device special file to be updated after the suspend image has been created,
which is potentially dangerous.
We can fix this by mounting a tmpfs, creating the special device file on it
and using this file for the sus
Jason Lunz scripst:
> Yes, it works just fine. I've been running a laptop with dm-crypt on
> swap and root for months now - only /boot is unencrypted.
That's cool -- more I am thinking about that more I don't understand how
is something like that possible. Suspend writes to (then encrypted with
/d
