Status of 2038 bug on IRIX?

IRIX and IRIX software discussion including open source and commerical offerings.
Forum rules
Any posts concerning pirated software or offering to buy/sell/trade commercial software are subject to removal.
robespierre
Posts: 1578
Joined: Mon Sep 12, 2011 2:28 pm
Location: Boston

Re: Status of 2038 bug on IRIX?

Unread postby robespierre » Thu May 19, 2016 1:48 pm

And then find that any binary times that were stored by applications give completely wrong values...
This type of fix is simply not possible IMHO.
:PI: :O2: :Indigo2IMP: :Indigo2IMP:

User avatar
jan-jaap
Donor
Donor
Posts: 4939
Joined: Thu Jun 17, 2004 11:35 am
Location: Wijchen, The Netherlands
Contact:

Re: Status of 2038 bug on IRIX?

Unread postby jan-jaap » Thu May 19, 2016 2:09 pm

Also the conversion to human readable time would be broken. For example, I can set an IRIX 4.x system to the correct date (19th of May 2016), but the DOW will be one day off, it will tell me it's Friday or Wednesday (I forgot) when today is really Thursday. Likely something related to leap years.
:PI: :Indigo: :Indigo: :Indy: :Indy: :Indy: :Indigo2: :Indigo2: :Indigo2IMP: :Octane: :Octane2: :O2: :O2+: Image :Fuel: :Tezro: :4D70G: :Skywriter: :PWRSeries: :Crimson: :ChallengeL: :Onyx: :O200: :Onyx2: :O3x02L:
To accentuate the special identity of the IRIS 4D/70, Silicon Graphics' designers selected a new color palette. The machine's coating blends dark grey, raspberry and beige colors into a pleasing harmony. (IRIS 4D/70 Superworkstation Technical Report)

User avatar
ClassicHasClass
Donor
Donor
Posts: 2109
Joined: Wed Jul 25, 2012 7:12 pm
Location: Sunny So Cal
Contact:

Re: Status of 2038 bug on IRIX?

Unread postby ClassicHasClass » Thu May 19, 2016 4:14 pm

I never claimed such an approach this would be devoid of side effects, but I'd rather have wrong values than the OS going berserk. At Y2038 I don't think we're going to care too much about wrong values. If someone's got a better way, this is the thread.

As far as the conversion to human readable time, effects like that would be lessened by using something that was the same calendar. 28 years would also be at least an integral number of leap years away.
smit happens.

:Fuel: bigred, 900MHz R16K, 4GB RAM, V12 DCD, 6.5.30
:Indy: indy, 150MHz R4400SC, 256MB RAM, XL24, 6.5.10
:Indigo2IMP: purplehaze, 175MHz R10000, Solid IMPACT
probably posted from Image bruce, Quad 2.5GHz PowerPC 970MP, 16GB RAM, Mac OS X 10.4.11
plus IBM POWER6 p520 * Apple Network Server 500 * RDI PrecisionBook * BeBox * Solbourne S3000 * Commodore 128 * many more...

User avatar
japes
Donor
Donor
Posts: 1006
Joined: Thu Nov 08, 2007 4:35 pm
Location: Lynnwood, WA

Re: Status of 2038 bug on IRIX?

Unread postby japes » Thu May 19, 2016 6:01 pm

I feel like you'd be less broken by turning off network time and setting the date back. Programmers can't be trusted to use time_t consistently. Software would be broken that didn't use the provided libraries for time and date. Interoperability with files and private network protocols would be broken. You could never catch all the dates stored in files and databases.

Sometimes the simple solution is the best. It would be great to fix the libraries, I just think software would be subtly broken in excited ways if you change the implementation.

[/sarcasm]Wait for IRIX 7.0 to come out with 64 bit time_t and update your software.[/sarcasm]
:O3000: :Fuel: :Tezro: :Tezro: :Octane2: :Octane: :Octane: :Indigo: :Indigo: :Indigo: :Indigo: :O2: :1600SW: :O2: :1600SW: :1600SW: :Indigo2: :Indigo2: :Indigo2: :Indigo2: :Indigo2IMP: :Indy: :Indy: :Indy: :Indy: :O3x0: :O3x02L: :O3x02L:

User avatar
ClassicHasClass
Donor
Donor
Posts: 2109
Joined: Wed Jul 25, 2012 7:12 pm
Location: Sunny So Cal
Contact:

Re: Status of 2038 bug on IRIX?

Unread postby ClassicHasClass » Fri May 20, 2016 12:27 am

Well, in this scheme, I *would* be setting the date back (at least the 32-bit time value so that it won't overflow for a while longer); I'm just changing the epoch. But yeah, there certainly is that risk with software that doesn't use the OS for this purpose.

Another option might be set the date back and have some sort of patched /bin/date or menu bar clock or etc. so that at least the time and date look right, and maybe even a patched ntpdate for some sort of time synchronization.
smit happens.

:Fuel: bigred, 900MHz R16K, 4GB RAM, V12 DCD, 6.5.30
:Indy: indy, 150MHz R4400SC, 256MB RAM, XL24, 6.5.10
:Indigo2IMP: purplehaze, 175MHz R10000, Solid IMPACT
probably posted from Image bruce, Quad 2.5GHz PowerPC 970MP, 16GB RAM, Mac OS X 10.4.11
plus IBM POWER6 p520 * Apple Network Server 500 * RDI PrecisionBook * BeBox * Solbourne S3000 * Commodore 128 * many more...

User avatar
ClassicHasClass
Donor
Donor
Posts: 2109
Joined: Wed Jul 25, 2012 7:12 pm
Location: Sunny So Cal
Contact:

Re: Status of 2038 bug on IRIX?

Unread postby ClassicHasClass » Fri May 20, 2016 9:25 am

For OS X, you can also relink a binary after it's built (install_name_tool), so I could have a patched libSystem.B.dylib, set the time value back, and have those apps that don't barf pointed to the new libSystem with a new epoch. Then non-standard apps will be back in time and apps that do use the BSD library calls will be correct.

The OS 9 epoch, of course, is totally different and I have to check if Carbon uses the OS 9 epoch. (I suspect it does.)
smit happens.

:Fuel: bigred, 900MHz R16K, 4GB RAM, V12 DCD, 6.5.30
:Indy: indy, 150MHz R4400SC, 256MB RAM, XL24, 6.5.10
:Indigo2IMP: purplehaze, 175MHz R10000, Solid IMPACT
probably posted from Image bruce, Quad 2.5GHz PowerPC 970MP, 16GB RAM, Mac OS X 10.4.11
plus IBM POWER6 p520 * Apple Network Server 500 * RDI PrecisionBook * BeBox * Solbourne S3000 * Commodore 128 * many more...


Return to “IRIX and Software”

Who is online

Users browsing this forum: No registered users and 3 guests