“the committed support for Oracle Solaris until at least 2037”
Conversation
Notices
-
Embed this notice
Joel Michael (jpm@aus.social)'s status on Thursday, 15-May-2025 07:03:51 JST Joel Michael
- Haelwenn /элвэн/ :triskell: likes this.
-
Embed this notice
Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Thursday, 15-May-2025 07:04:47 JST Haelwenn /элвэн/ :triskell:
@jpm Huh… I thought Sun fixed the 2038 bugs in it's era of Solaris. feld likes this. -
Embed this notice
Joel Michael (jpm@aus.social)'s status on Saturday, 17-May-2025 05:42:43 JST Joel Michael
So, I probably should explain this, because there’s multiple levels to this joke.
The first level is the 2038 problem, when the “traditional” 32-bit signed time_t rolls over which is going to cause at least as much chaos as Y2K prior to 2000.
The second level is that Solaris has been 64-bit capable since the release of Solaris 7 in 1998, and 64-bit only since Solaris 11 in 2011, so it shouldn’t be a problem anyway.
The third level is the “Solaris Binary Guarantee” which states that a binary compiled for previous versions of Solaris will run unmodified on future versions. However, this means that binaries compiled for Solaris 10 and earlier may be 32-bit, using 32-bit time_t.
So, yes, but no, but yes. Maybe.
Haelwenn /элвэн/ :triskell: likes this.