1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
»Q« wrote: |
5 |
> I based my guess that using local time causes it on the fact that the |
6 |
> system clock is set using the hardware clock (local) a few seconds |
7 |
> after the Superblock last write time is fixed during boot. And it's my |
8 |
> impression that if I wait a few hours before booting (my offset from |
9 |
> UTC is -5) no problem with the Superblock write time is detected. I |
10 |
> say 'impression' because I haven't paid close attention to that. |
11 |
> |
12 |
> But I'm just guessing; I don't mean to hijack Walter's thread. |
13 |
|
14 |
I've experienced this as well when using a local clock. I no longer do |
15 |
that as I no longer dual boot, and if you aren't dual booting with that |
16 |
evil OS, then you should use clock=UTC and this problem will go right |
17 |
away. Not sure if it's fixable with clock=local though... |
18 |
|
19 |
- -- |
20 |
Randy Barlow |
21 |
http://electronsweatshop.com |
22 |
|
23 |
But you are a chosen race, a royal priesthood, a holy nation, a people |
24 |
for his own possession, that you may proclaim the excellencies of him |
25 |
who called you out of darkness into his marvelous light. Once you were |
26 |
not a people, but now you are God's people; once you had not received |
27 |
mercy, but now you have received mercy. ~1 Peter 2:9-10 |
28 |
|
29 |
|
30 |
-----BEGIN PGP SIGNATURE----- |
31 |
Version: GnuPG v1.4.7 (GNU/Linux) |
32 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
33 |
|
34 |
iD8DBQFGZVC77So1xaF/eR8RAkn9AJ9UZ+cW2rlLymAiO9BX7RwbMC1U0wCfe3c1 |
35 |
XtYJdBglwsYWEea7NpwpMUk= |
36 |
=uKB4 |
37 |
-----END PGP SIGNATURE----- |
38 |
-- |
39 |
gentoo-user@g.o mailing list |