Messages in this thread | | | Date | Fri, 16 Dec 2005 13:40:39 +0100 | From | Pavel Machek <> | Subject | Re: swsusp: documentation fixes |
| |
Hi!
> > @@ -328,4 +326,10 @@ init=/bin/bash, then swapon and starting > > usually does the trick. Then it is good idea to try with latest > > vanilla kernel. > > > > +Q: How can RH ship a swsusp-supporting kernel with modular SATA > > +drivers? > > > > +A: Well, it can be done, load the drivers, then do echo into resume > > +file from initrd. Be sure not to mount anything, not even read-only > > +mount, or you are going to loose your filesystem same way Dave Jones > > +did. > > Quick solution to this - store the root filesystem's dev_t in the image > header. If it's mounted when doing the sanity check, refuse to resume.
Yep, we could do that. But it is not 100% solution (you could have some non-root filesystem mounted, and corrupt that one), anyway, and I'd rather keep people from using it than complicating swsusp even more. u-swsusp is going to make this obsolete, anyway, and can do any sanity checks it wants to. Pavel -- Thanks, Sharp! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |