On Mon, Sep 25, 2006 at 11:41:29AM -0400, Jason Lunz wrote:
> On Mon, Sep 25, 2006 at 08:22:09AM +0200, Stefan Seyfried wrote:
> > - What happens if i suspend with a "timing enabled" s2disk and resume with a
> > "pre-timing-enabled" resume? (Somebody updates the package but forgets to
> > run m
On Mon, Sep 25, 2006 at 08:22:09AM +0200, Stefan Seyfried wrote:
> - What happens if i suspend with a "timing enabled" s2disk and resume with a
> "pre-timing-enabled" resume? (Somebody updates the package but forgets to
> run mkinitrd).
> Will it just fail (invalid header) or will it cause tota
On Fri, Sep 22, 2006 at 10:30:04AM -0400, Jason Lunz wrote:
> On Fri, Sep 22, 2006 at 03:48:20PM +0200, Pavel Machek wrote:
> > Well, it did not apply (reject) and did not compile when applied
>
> I was working against the debian uswsusp 0.2 package - i'll use cvs next
> time. sorry.
>
> > (missi
On Fri, Sep 22, 2006 at 03:48:20PM +0200, Pavel Machek wrote:
> Well, it did not apply (reject) and did not compile when applied
I was working against the debian uswsusp 0.2 package - i'll use cvs next
time. sorry.
> (missing swsusp.h changes). I fixed it up, but please check it after
> me...
I
Hi!
> Print s2disk benchmarks. The image writeout time is saved in the
> swsusp_info header during suspend, then statistics are printed during
> resume about elapsed time and image load/store speed for writeout,
> readin, and total.
Well, it did not apply (reject) and did not compile when applied
Print s2disk benchmarks. The image writeout time is saved in the
swsusp_info header during suspend, then statistics are printed during
resume about elapsed time and image load/store speed for writeout,
readin, and total.
---
resume.c | 24 +++-
suspend.c | 11 +++
