As I said, what's in there now is a hack. A kernel parameter would be
an improvement. For the purposes of suspend/resume, it's preferable to
have a safe algorithm which determines the offset between the system
clock and the RTC. The old algorithm needs to read the RTC after the
suspend event is caught (but before the kernel allows/denys the
suspend). The problem is that the Dell Inspiron 3200 slows down the
system even before the kernel can allow the suspend event. This makes
the RTC measurement take several seconds.
Even without the Inspiron problem, you get up to 1 second error. This
accumulates for every suspend/resume cycle. Close and open your laptop
10 times a day and you lose 10 seconds a day. Stephen is working on a
better measurement algorithm.
The only place I'm aware that the kernel needs to know the timezone is
this case with suspend/resume. So aside from this, I don't see a need
for the kernel to know the timezone. Hm. Although I vaguely remember
something about SMB and timestamps. Stupid M$. Probably a good reason
for pushing SMBFS into user space. It's not really that important
anyway </flamebait>.
Regards,
Richard....
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/