Re: uspend to Disk - Kernel 2.6.4 vs. r50p

[Rob Landley <rob@landley.net>]

On Sunday 09 May 2004 16:49, Pavel Machek wrote:
> Hi!
>
> > > If you suspend, mount
> > > your filesytems, do some work and then resume, you are probably going
> > > to do some pretty nasty corruption. Just don't do that.
> > >
> > > But this problem is shared by swsusp, swsusp2 *and* pmdisk.
> >
> > I know.  I also know that ext2 (and derivatives) have both "last mounted"
> > and "last written to" datestamp fields (other filesystems probably do as
> > well, but I don't use 'em) and it would be really nice to check those as
> > matching what they were when you suspended, and abort the resume if they
> > don't match...
>
> Well, feel free to code that, that will allow us to kill few
> warnings... Or rather tone them down. It is still "dont do that"
> situation.

I'll add it to my endless to-do pile, but don't hold your breath.

> > > > Sigh.  I _really_ don't have time for this right now.  I wonder if it
> > > > would be possible to just send Patrick some money?
> > >
> > > He's out of time, so money is not likely to help. Sending some money
> > > to Nigel might do the trick ;-).
> >
> > His code isn't the one I've gotten to work yet... :)
>
> 2.4 version should be rather easy to get going...
> 									Pavel

The last time I booted a 2.4 kernel was 2003.  Every time Nigel's code is 
mentioned, 2.4 is also mentioned.  I could also downgrade to 2.2 and debug a 
version written for that, too.  It makes about as much sense to me...

I'll try again when 2.6.6 comes out, as usual...

Rob