looks like a bug in win 95/98 crashes a system that has been up more than
49 days -- but no one finds it because they always crash long before that
anyway.
http://www.zdnet.com/zdhelp/stories/main/0,5594,2238939-3,00.html
Isn't there something similar in Linux? Except the limit is a bit over a
On Thu, Apr 08, 1999 at 04:14:07PM -0700, Henry Kingman wrote:
Isn't there something similar in Linux? Except the limit is a bit over a
year?
I could be wrong, but I think this bug had to do with your uptime
wrapping around. Your machine wouldn't crash, it just wouldn't know
how long it had
henry harrumphed,
Isn't there something similar in Linux? Except the limit is a bit over a
year?
A bit more than that. The date rolls over in 2038 on 32 bit unices.
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 8 Apr 1999 20:12:37 -0400, Ian Peters wrote:
I could be wrong, but I think this bug had to do with your uptime
wrapping around. Your machine wouldn't crash, it just wouldn't know
how long it had been up.
Like I said, though, I could be
Richard E. Hawkins Esq. wrote:
henry harrumphed,
Isn't there something similar in Linux? Except the limit is a bit over a
year?
A bit more than that. The date rolls over in 2038 on 32 bit unices.
Would that be called a Y2.038K bug in Linux slanguage?
On Thu, 8 Apr 1999, Richard E. Hawkins Esq. wrote:
Isn't there something similar in Linux? Except the limit is a bit over a
year?
A bit more than that. The date rolls over in 2038 on 32 bit unices.
Wrong limit. There's a counter in some MS-written systems (which includes
OS/2, as I
Just to add my two cents, I had a Linux box up and running for 457 days
lately. Didn't show any alarming symptom. And no, it didn't crash then.
I just rebooted it myself.
Isn't there something similar in Linux? Except the limit is a bit over a
year?
A bit more than that. The date rolls
7 matches
Mail list logo
