Nigel Cunningham <[email protected]> writes:
> Yes, provided as you say that you don't mount the file systems involved;
> mounting them will make journalling filesystems run their recoveries,
> which will in turn make the suspend image inconsistent. It's only really
> viable if the filesystems were mounted read only to start with... I've
> just added functionality to the 2.4 version for such a case.
OK, is it possible with 2.6? The Kconfig help says you can. How is
it done?
--
M?ns Rullg?rd
[email protected]
If your filesystems were mounted readonly and the boot won't mount them
writable, you should be fine with no special precautions. Last time I
looked at 2.6 code, it didn't fix the suspend header when you use
noresume. If that's still true, you should be able to boot with the
noresume option, and then later normally.
(The 2.4 functionality I spoke of works differently, partly because it
does fix the suspend header if you use the noresume option.)
Regards,
Nigel
On Fri, 2003-09-19 at 21:45, M?ns Rullg?rd wrote:
> Nigel Cunningham <[email protected]> writes:
>
> > Yes, provided as you say that you don't mount the file systems involved;
> > mounting them will make journalling filesystems run their recoveries,
> > which will in turn make the suspend image inconsistent. It's only really
> > viable if the filesystems were mounted read only to start with... I've
> > just added functionality to the 2.4 version for such a case.
>
> OK, is it possible with 2.6? The Kconfig help says you can. How is
> it done?
--
Nigel Cunningham
495 St Georges Road South, Hastings 4201, New Zealand
You see, at just the right time, when we were still powerless,
Christ died for the ungodly.
-- Romans 5:6, NIV.