Linked by Thom Holwerda on Sun 9th Jul 2017 08:59 UTC
BeOS & Derivatives

time_t now uses 64-bit on 64-bit systems. This fixes the year 2038 bug for 64-bit Haiku, so we can continue to run it after 2038. This breaks the ABI, so all the 64bit packages were rebuilt.

As Michel points out in the comments, this means Haiku'll be good until 4 December 292277026596, about in time for the beta release.

Order by: Score:
Linux desktop?
by Isolationist on Sun 9th Jul 2017 09:29 UTC
Isolationist
Member since:
2006-05-28

Will 292277026596 be the year of the Linux desktop though? </tongueInCheek>

Reply Score: 2

RE: Linux desktop?
by judgen on Sun 9th Jul 2017 09:50 UTC in reply to "Linux desktop?"
judgen Member since:
2006-07-12

Haiku is not linux in any way. It uses gcc, but thet is about it.

Reply Score: 4

RE[2]: Linux desktop?
by Isolationist on Sun 9th Jul 2017 12:37 UTC in reply to "RE: Linux desktop?"
Isolationist Member since:
2006-05-28

I think you missed the point.

Reply Score: 1

RE[3]: Linux desktop?
by aaronb on Sun 9th Jul 2017 15:21 UTC in reply to "RE[2]: Linux desktop?"
aaronb Member since:
2005-07-06

What was the point?

Reply Score: 3

RE[4]: Linux desktop?
by Isolationist on Sun 9th Jul 2017 15:26 UTC in reply to "RE[3]: Linux desktop?"
Isolationist Member since:
2006-05-28

Read the post

Reply Score: 1

RE[4]: Linux desktop?
by CATs on Mon 10th Jul 2017 07:46 UTC in reply to "RE[3]: Linux desktop?"
CATs Member since:
2017-06-09

You definitely missed the point. No one ever implied Haiku is Linux.

Reply Score: 2

RE[5]: Linux desktop?
by Isolationist on Mon 10th Jul 2017 12:10 UTC in reply to "RE[4]: Linux desktop?"
Isolationist Member since:
2006-05-28

Exactly that.

Reply Score: 2

RE[5]: Linux desktop?
by aaronb on Mon 10th Jul 2017 16:37 UTC in reply to "RE[4]: Linux desktop?"
aaronb Member since:
2005-07-06

Hence the question...
(we may have hit the dry "humour" limit early)

Edited 2017-07-10 16:50 UTC

Reply Score: 2

RE[6]: Linux desktop?
by Isolationist on Mon 10th Jul 2017 19:22 UTC in reply to "RE[5]: Linux desktop?"
Isolationist Member since:
2006-05-28

That's my last attempt at humour on here ;)

Reply Score: 2

RE[7]: Linux desktop?
by aaronb on Mon 10th Jul 2017 20:00 UTC in reply to "RE[6]: Linux desktop?"
aaronb Member since:
2005-07-06

Oh no, I welcome to a future "dry-humour-off" when Haiku gets its first release candidate! (-:

Reply Score: 2

RE: Linux desktop?
by Soulbender on Tue 11th Jul 2017 06:37 UTC in reply to "Linux desktop?"
Soulbender Member since:
2005-08-18

Probably going to happen the same year as Windows server in the cloud.

Reply Score: 2

RE[2]: Linux desktop?
by darknexus on Tue 11th Jul 2017 17:00 UTC in reply to "RE: Linux desktop?"
darknexus Member since:
2008-07-15

Probably going to happen the same year as Windows server in the cloud.

Unfortunately, that one's already here and is growing rather than staying at 0.0001% as it deserves.

Reply Score: 2

2038
by Treza on Sun 9th Jul 2017 22:00 UTC
Treza
Member since:
2006-01-11

They had to fix it before the release of the V1 final, planned for 2039.

Reply Score: 5

RE: 2038
by The123king on Sun 9th Jul 2017 22:49 UTC in reply to "2038"
The123king Member since:
2009-05-28

I like your optimism

Reply Score: 5

RE: 2038
by BlueofRainbow on Mon 10th Jul 2017 11:45 UTC in reply to "2038"
BlueofRainbow Member since:
2009-01-06

From what I understand, fixing the Y2038 issue required "breaking" the Application Binary Interface (ABI).

The fix was applied to Haiku-64bit. All applications included in the nightly build were recompiled.

The fix was not applied to Haiku-32bit as this would break compatibility with the BeOS applications still in circulation. It is quite possible that BeOS it-self (and by extension Zeta) have the same issue.

Reply Score: 2

RE[2]: 2038
by JLF65 on Mon 10th Jul 2017 17:21 UTC in reply to "RE: 2038"
JLF65 Member since:
2005-07-06

They'll need to eventually make two ABIs for 32-bit. One will be backwards compatible to allow running old programs that won't break due to the bug; the other will have a minor change to the ABI only affecting the bug. The easiest way to deal with the bug after 2038 would be to have the time freeze right before the date that wraps around. So old 32-bit programs would get the same date from then on, while 32-bit programs compiled with the new ABI will get the proper date.

Dealing with two ABIs for 32-bit shouldn't be much of a hassle - both MacOS and Windows have done that a number of times, going as far as to have "FAT" binaries that handle both in the same executable. It's a kludge, but some problems can only be effectively dealt with by a kludge.

Reply Score: 2

Burn...
by fretinator on Mon 10th Jul 2017 13:47 UTC
fretinator
Member since:
2005-07-06

As Michel points out in the comments, this means Haiku'll be good until 4 December 292277026596, about in time for the beta release.

Puh-lease get those folks some Aloe Vera!

Reply Score: 2