On Mon, 18 Sep 2000 11:42:50 -0400, Chris Nandor wrote:
>>But the OS's idea of the epoch is global!
>
>No, it isn't! On Mac OS, I can change my epoch by changing my time zone.
>If it is harcoded into Config.pm, I am fucked.
This is bad. That system is broken. ;-) I guess that it's the same
situ
At 13:23 +0200 2000.09.20, Bart Lateur wrote:
>This surely was a bad design decision from the hardware guys. Very
>shortsighted.
I don't know if it has anything to do with the hardware clock. It has to
do with what the Mac OS API returns for seconds since epoch. The
difference from GMT, or the
Bart Lateur <[EMAIL PROTECTED]> writes:
> This is bad. That system is broken. ;-) I guess that it's the same
> situation on MS-DOS, since there the hardware clock is usually set to
> local time. It could even happen on Win32?!?
> This surely was a bad design decision from the hardware guys. Very
On 20 Sep 2000 13:03:22 -0700, Russ Allbery wrote:
>It's not a hardware problem; the hardware clock just keeps a time. It has
>no concept of time zones.
I thought later on that I wrote this the wrong way. What I ment was: the
guys who did the interface to the hardware.
>It's a software problem
