[Info-vax] 2038 32-bit time_t overflow, was: Re: DCL Output Parsing, Compatibility, and Terrible User Interfaces

[Johnny Billquist]

On 2018-12-02 15:39, Bill Gunshannon wrote:
> On 12/2/18 7:21 AM, Johnny Billquist wrote:
>> On 2018-11-28 21:19, Bill Gunshannon wrote:
>>> So you mean my Ultrix-32 systems will enter the same twilight zone
>>> as my RSTS systems. :-)
>>
>> I haven't looked at Ultrix-32, but if you say so...
> 
> It's pretty much vanilla SYSV with a few BSD accretions. Got to have
> the problem.  And I have never seen source made available.  Plus, it
> is not covered by the license that freed older Unix versions so not
> likely to be able to fix it.  Unless someone decided to try to do it
> with ADB.  Good luck with that!!

I know Ultrix is. :-)
I just assumed that you had then checked what time_t was defined as, and 
I have not.
I'll try and locate the information unless someone beats me to it.

>>> I left Ultrix-11 out of this as I have the source so I can fix it
>>> when the time comes.  :-)
>>
>> Ultrix-11 seems like a high probability of having the problem. Time to 
>> start fixing. :-)
> 
> No doubt, but I was able to Y2K it, so anything is possible.  Maybe
> even make it run on my VAX instead of Ultrix-32.  After all, Unix is
> Unix.

Yeah... Right... And a VAX is not a PDP-11...

> Hmmmm...  Wonder if anyone is looking at fixing BSD 2.11?

I haven't. But I just checked, and time_t is a signed long, so 2038, 
here we come...

   Johnny

-- 
Johnny Billquist                  || "I'm on a bus
                                   ||  on a psychedelic trip
email: bqt at softjar.se             ||  Reading murder books
pdp is alive!                     ||  tryin' to stay hip" - B. Idol