Hi. On Wed, 2005-07-20 at 20:54, Hiroyuki Machida wrote: > Hi, > > > With this function, system needs to mount read-write file systems on > every boot cycle, due to avoid inconsistency between FS and memory. > How did you address this problem? Did kernel check RW FS remained as > mounted on boot up or hibernate time ?
You're right. We don't seek to address this problem, just document clearly that filesystems in use when creating the image need to be mounted readonly. You can of course mount another filesystem read/write while the system is up. > I think I need to discuss with you at San Jose at the beginning of > this year. Yes, I think we did meet. Nice to talk to you again. Regards, Nigel > > Regards, > Hiroyuki Machida > > Nigel Cunningham wrote: > > Hi. > > > > We've had this feature in Suspend2 for a couple of years and I can > > confirm that the approach works, provided that the on-disk filesystem > > remains unchanged throughout this. (Useful mainly for kiosks etc). > > > > This is not to say that I've reviewed the code below for correctness. > > > > Regards, > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ -- Evolution. Enumerate the requirements. Consider the interdependencies. Calculate the probabilities. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
