Y2K.38

Remember the Y2K?

System call conversion for year 2038:
https://lwn.net/Articles/643234/

This works has been ongoing and will have something incorporated in kernel 4.18.x

The Y2K panic was a lot of fun! Yours truly was one tasked to find and put in remedies (if necessary) for a particular million-line-of-code software system :))

-bodhi
===========================
Forum Wiki
bodhi's corner

bodhi Wrote:
-------------------------------------------------------
> The Y2K panic was a lot of fun!


Definitely :) Its teh Y2k bug and my inveterate fiddling with PC's that got me the job in IT.... (I had a real job before then :)))))))) )

bodhi Wrote:
-------------------------------------------------------
> The Y2K panic was a lot of fun! Yours truly was one tasked to find and put in remedies (if necessary) for a particular million-line-of-code software system :))
>
I believe such a panic only affected Windows OS users. I never bothered with it and was sort of disappointed that it never happened on any of my Linux desktop computers.

habibie Wrote:
-------------------------------------------------------
> bodhi Wrote:
> -------------------------------------------------------
> > The Y2K panic was a lot of fun! Yours truly was
> one tasked to find and put in remedies (if
> necessary) for a particular million-line-of-code
> software system :))
> >
> I believe such a panic only affected Windows OS
> users. I never bothered with it and was sort of
> disappointed that it never happened on any of my
> Linux desktop computers.


Nope.... any and every 16bit sytsem or 16bit coded software

https://en.wikipedia.org/wiki/Year_2000_problem

Gravelrash Wrote:
-------------------------------------------------------
> habibie Wrote:
> -------------------------------------------------------
> > bodhi Wrote:
> >
> -------------------------------------------------------
> > > The Y2K panic was a lot of fun! Yours truly
> was
> > one tasked to find and put in remedies (if
> > necessary) for a particular
> million-line-of-code
> > software system :))
> > >
> > I believe such a panic only affected Windows OS
> > users. I never bothered with it and was sort of
> > disappointed that it never happened on any of
> my
> > Linux desktop computers.
>
>
> Nope.... any and every 16bit sytsem or 16bit coded software
>
> https://en.wikipedia.org/wiki/Year_2000_problem
>
IIRC, Linux started out in 1992 with a 32-bit OS.

> I never bothered with it and was sort of
> disappointed that it never happened on any of my
> Linux desktop computers.

You’re a masochist :)))

-bodhi
===========================
Forum Wiki
bodhi's corner

habibie Wrote:
-------------------------------------------------------
> Gravelrash Wrote:
> -------------------------------------------------------
> > habibie Wrote:
> >
> -------------------------------------------------------
> > > bodhi Wrote:
> > >
> >
> -------------------------------------------------------
> > > > The Y2K panic was a lot of fun! Yours truly
> > was
> > > one tasked to find and put in remedies (if
> > > necessary) for a particular
> > million-line-of-code
> > > software system :))
> > > >
> > > I believe such a panic only affected Windows
> OS
> > > users. I never bothered with it and was sort
> of
> > > disappointed that it never happened on any of
> > my
> > > Linux desktop computers.
> >
> >
> > Nope.... any and every 16bit sytsem or 16bit
> coded software
> >
> > https://en.wikipedia.org/wiki/Year_2000_problem
> >
> IIRC, Linux started out in 1992 with a 32-bit OS.

It does not matter how many bit. If your code expected that date is always 19xx then it will crash when the calendar wraps around at new years eve Y2K.

Similarly, the international dateline problem with 180 degree wrap around would cause avionics software still under testing, ie buggy, to go crazy at that crossing :)

For Y2K, if you have updated your Linux system a few days before, then you wont see the bug in the OS itself. Same thing for Windows.

But if you use an application that has not been defensively coded with these typical problems in mind, then the possiblity of crashing is always there at that time and place.

-bodhi
===========================
Forum Wiki
bodhi's corner



Edited 1 time(s). Last edit at 06/12/2018 08:52PM by bodhi.

bodhi Wrote:
-------------------------------------------------------
> > I never bothered with it and was sort of disappointed that it never happened on any of my Linux desktop computers.
>
> You’re a masochist :)))
>
TBH, I really was very disappointed that the Y2K did not happen to any of my Linux desktop computers. I sure would like to find out what that would have done. Alas, you don't always get what you want. If you think being honest is a masochist and better than dishonest, then be it.

bodhi Wrote:
-------------------------------------------------------
> It does not matter how many bit. If your code expected that date is always 19xx then it will crash when the calendar wraps around at new years eve Y2K.
>
Yes and it does. For instance, the 16-bit OS runs out of bits to handle the date and wraps around @ NY eve of Y2K.

> For Y2K, if you have updated your Linux system a few days before, then you wont see the bug in the OS itself. Same thing for Windows.
>
I don't recall I had to do this on any of my Linux desktop computer. Again, I really was very disappointed that Y2K never happened to any of my Linux desktop computers.

> But if you use an application that has not been defensively coded with these typical problems in mind, then the possiblity of crashing is always there at that time and place.
>
I sure would like to know which application (preferably an open-source) you talked about that had such a Y2K problem. TBH, I sure would like to look at the source code of it.

we had to deal with lots of cobol code :)

habibie,

Quote

> You’re a masochist :)))
>
TBH, I really was very disappointed that the Y2K did not happen to any of my Linux desktop computers. I sure would like to find out what that would have done. Alas, you don't always get what you want. If you think being honest is a masochist and better than dishonest, then be it.

It's a joke :)

Quote

Gravelrash Wrote:

we had to deal with lots of cobol code :)

That's said it all :)

-bodhi
===========================
Forum Wiki
bodhi's corner

bodhi Wrote:
-------------------------------------------------------

> That's said it all :)

It was a memorable time, 1999 up until New Years. I was in IRC with Brit friends and knew 5 hours earlier nothing broke over there, so all was going to be good. Capped of a year of patching all the Windows machines I could for University volunteer group AITP, and meeting a lot of damsels in distress along the way. And ever since, the damsels who stuck with Microsoft have been 80% distress free! Ba doom shhh. The Linux girls have rectangle glasses and a cat.

=========
-= Cloud 9 =-

JoeyPogoPlugE02 Wrote:
-------------------------------------------------------
> bodhi Wrote:
> -------------------------------------------------------
>
> > That's said it all :)
>
> It was a memorable time, 1999 up until New Years.
> I was in IRC with Brit friends and knew 5 hours
> earlier nothing broke over there, so all was going
> to be good. Capped of a year of patching all the
> Windows machines I could for University volunteer
> group AITP, and meeting a lot of damsels in
> distress along the way. And ever since, the
> damsels who stuck with Microsoft have been 80%
> distress free! Ba doom shhh. The Linux girls have
> rectangle glasses and a cat.

Heady days :))

-bodhi
===========================
Forum Wiki
bodhi's corner