-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 »Q« wrote: > I based my guess that using local time causes it on the fact that the > system clock is set using the hardware clock (local) a few seconds > after the Superblock last write time is fixed during boot. And it's my > impression that if I wait a few hours before booting (my offset from > UTC is -5) no problem with the Superblock write time is detected. I > say 'impression' because I haven't paid close attention to that. > > But I'm just guessing; I don't mean to hijack Walter's thread.
I've experienced this as well when using a local clock. I no longer do that as I no longer dual boot, and if you aren't dual booting with that evil OS, then you should use clock=UTC and this problem will go right away. Not sure if it's fixable with clock=local though... - -- Randy Barlow http://electronsweatshop.com But you are a chosen race, a royal priesthood, a holy nation, a people for his own possession, that you may proclaim the excellencies of him who called you out of darkness into his marvelous light. Once you were not a people, but now you are God's people; once you had not received mercy, but now you have received mercy. ~1 Peter 2:9-10 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGZVC77So1xaF/eR8RAkn9AJ9UZ+cW2rlLymAiO9BX7RwbMC1U0wCfe3c1 XtYJdBglwsYWEea7NpwpMUk= =uKB4 -----END PGP SIGNATURE----- -- [EMAIL PROTECTED] mailing list
