At 09:05:01.75 on 19-OCT-2011 in message
<CAA6-MF8+SqOqz33T8=n18e3ag7vx7avb9hpd53rljjos27e...@mail.gmail.com>, Janne
Johansson <icepic...@gmail.com> wrote:
>2011/10/19 Bruce Drake <br...@zectro.com>
>
>> I found mention of a possible move to 64 bit time_t back in 2005 and 3.9
>> was mentioned, but I see it hasn't happened. Is there a plan, like for
>> instance making all platforms, even 32 bit 64 bit time_t, like I think
>> NetBSD have tried/trying to do?
>> Can some one give a brief list of what needs to change, forgetting about
>> ports, like UFS etc. that would be greatly appreciated.
>>
>> A lot of protocols?
>Its of no use if my machine knows it is Jan-1-2040 today if the HTTP
>cache-expires says "you may cache this until Jan-1-1904" or the ntpd thinks
>UTC is at 1904 and I'm a "bit" off.
You seem to be saying that applications need to be patched before
the underlying operating system (OS) can be considered. But isn't the OS
responsible for providing the "glue" (e.g. time-related include files and
libraries) with which applications are built? (This is coming from a casual
user, so if I made the wrong inference from your statement, I'm happy to be
corrected.)
>
>--
> To our sweethearts and wives. May they never meet. -- 19th century toast
>
Regards,
Mike
