I'm not sure how one can compare Y2K with Meltdown and Spectre. We know
there was a point when Y2K would become a problem. That was 1/1/2000...
Meltdown and Spectre are different. Millions of computers and maybe
even more devices and embedded systems are affected today. We have no
time
The big difference is that was mostly resolved via software. Intel issue is
much harder.
On Jan 5, 2018 11:48 PM, "Steve Litt" <sl...@troubleshooters.com> wrote:
> On Fri, 05 Jan 2018 11:27:38 -0700
> Eric Oyen <eric.o...@icloud.com> wrote:
>
> > oh boy.
On Fri, 05 Jan 2018 11:27:38 -0700
Eric Oyen <eric.o...@icloud.com> wrote:
> oh boy. This sounds like another Y2K problem, only this one has some
> reality about it and real consequences.
Y2K was completely real, and would have had real consequences if our
society hadn't taken three
> Original Message
>Subject: Re: OT: Major Intel Memory Vulnerability - worse than Y2K?
>Local Time: January 5, 2018 12:35 PM
>UTC Time: January 5, 2018 7:35 PM
>From: eric.o...@icloud.com
>To: Main PLUG discussion list <plug-discuss@lists.phxlinux.org>
&
c — You don’t think Y2K had consequences?
> :)
>
> It just happened to be a raft of stupid bugs that the industry dealt with in
> time.
> I was coding around Y2K bugs as early as 1979, as were lots of other people,
> just matter of factly planning on Y2K, but some of the older and
So, Eric — You don’t think Y2K had consequences?
:)
It just happened to be a raft of stupid bugs that the industry dealt with in
time.
I was coding around Y2K bugs as early as 1979, as were lots of other people,
just matter of factly planning on Y2K, but some of the older and more primitive
> Cars are a problem. We all expect our 60 year old 1957 Chevies to keep
> running. In 2038 a 60 year old car will be a 1978: Not an unreasonable
> expectation.
>
> By 2038 they can gain 29 years by redefining epoch-start as 1999
> instead of 1970. By 2067 technology will be so advanced that there
l programs defined a date as pic99 and that's a
problem regardless of int size. But presumably for y2k they increased
that to pic, and that's good til New Years Eve .
> It's seems like it's not so much the desktops and servers
> we have to worry about, but all the 32 bit em
>How many bits that are used for time has little to do with how many bits
> the processor has. There is still plenty of software that has their
> time hard coded to use 32bits even if it's running on a 64bit processor.
> It's seems like it's not so much the desktops and servers we have to
>
things that may last in excess of 20 years.
The next 20 years should be a wild ride.
On 2017-12-27 04:54, Matthew Crews wrote:
Man, Y2K seems like at eternity ago. I knew back then that nothing
world-ending was going to happen, but I expected there to be major
hiccups. Thankfully there were only
>> Matthew Crews <mailingli...@mattcrews.com> wrote:
>>
>> > Man, Y2K seems like at eternity ago. I knew back then that nothing
>> > world-ending was going to happen, but I expected there to be major
>> > hiccups. Thankfully there were only minor hiccups
How many bits that are used for time has little to do with how many bits
the processor has. There is still plenty of software that has their
time hard coded to use 32bits even if it's running on a 64bit processor.
It's seems like it's not so much the desktops and servers we have to
worry
:17 -0500
> Matthew Crews <mailingli...@mattcrews.com> wrote:
>
> > Man, Y2K seems like at eternity ago. I knew back then that nothing
> > world-ending was going to happen, but I expected there to be major
> > hiccups. Thankfully there were only minor hiccups since everyone
&
On Wed, 27 Dec 2017 06:54:17 -0500
Matthew Crews <mailingli...@mattcrews.com> wrote:
> Man, Y2K seems like at eternity ago. I knew back then that nothing
> world-ending was going to happen, but I expected there to be major
> hiccups. Thankfully there were only minor hiccups
Man, Y2K seems like at eternity ago. I knew back then that nothing world-ending
was going to happen, but I expected there to be major hiccups. Thankfully there
were only minor hiccups since everyone worked their butts off on correcting Y2K
bugs.
The year 2038 problem might be a similar result
a whimper in Olympia Washington, and all had a good night.
>
> Thanks,
> Alex.
>
> Sent from my Samsung Galaxy S8+
>
> On Dec 25, 2017 06:38, <techli...@phpcoderusa.com> wrote:
> Hi All,
>
> Y2K was 18 years ago. Do you remember where you were? I do.
>
in Olympia Washington, and all had a good
night.
Thanks,
Alex.
Sent from my Samsung Galaxy S8+
On Dec 25, 2017 06:38, <techli...@phpcoderusa.com> wrote:
> Hi All,
>
> Y2K was 18 years ago. Do you remember where you were? I do.
>
> I had just gotten off a large Y2K pro
, bugs, bugs and more bugs Dept.
On Dec 25, 2017, at 6:38 AM, techli...@phpcoderusa.com wrote:
> Hi All,
>
> Y2K was 18 years ago. Do you remember where you were? I do.
>
> I had just gotten off a large Y2K project and my wife and I did some
> prepping... Looking back we did n
My fix for y2k was to push it off for 20 years.
There were no dates before 1921 in the data, so the 2 digit year below 21
was treated as 2001-2020 so I have 2 more years before it becomes a problem.
Luckily those computers aren't running any more.
Merry Christmas Everyone.
On Dec 25, 2017 6
Hi All,
Y2K was 18 years ago. Do you remember where you were? I do.
I had just gotten off a large Y2K project and my wife and I did some
prepping... Looking back we did not do enough given the potential for
catastrophic failure.
We stayed up all night glued to the TV watching as each
20 matches
Mail list logo
