1 posted on
01/03/2016 5:05:34 PM PST by
ShadowAce
To: rdb3; Calvinist_Dark_Lord; JosephW; Only1choice____Freedom; amigatec; Ernest_at_the_Beach; ...
2 posted on
01/03/2016 5:05:47 PM PST by
ShadowAce
(Linux - The Ultimate Windows Service Pack)
To: ShadowAce; AdmSmith; AnonymousConservative; Berosus; bigheadfred; Bockscar; cardinal4; ColdOne; ...
Hey, Al Gore's first invention!
3 posted on
01/03/2016 5:11:15 PM PST by
SunkenCiv
(Here's to the day the forensics people scrape what's left of Putin off the ceiling of his limo.)
To: ShadowAce
4 posted on
01/03/2016 5:12:36 PM PST by
Stentor
(#Mummers lives matter.)
To: ShadowAce
2038. Most are not ready, but the big boys are.
5 posted on
01/03/2016 5:12:39 PM PST by
soycd
To: ShadowAce
I hate UNIX. Men should have their testicular bits in working order.
6 posted on
01/03/2016 5:14:10 PM PST by
West Texas Chuck
(OBAMA: Fundamentally Twerking America)
To: ShadowAce
How much is that in dog years?
7 posted on
01/03/2016 5:17:29 PM PST by
1rudeboy
To: ShadowAce
1451870344
Time marches on!
To: ShadowAce
Speaking of breaking, Unix time runs into a problem at 03:14:07 UTC on 19 January 2038. The 2038 epochalypse will occur when the Unix time counter overflows the limits of the 32-bit integer data type (at 2,147,483,647 seconds). Time will just rollover to 0 and start again. I doubt there will be very many 32 bit computers in 2038. Besides, we already went through this exact problem with VMS back in the 90's. It's no big deal.
9 posted on
01/03/2016 5:27:33 PM PST by
SeeSharp
To: ShadowAce
1,500,000,000 UNIX = Friday 14-Jul-2017 02:40:00 UTC = Thursday 13 July 2017 22:40 ET
10 posted on
01/03/2016 5:32:14 PM PST by
Lonesome in Massachussets
(Islam is the greened eyed monster that doth mock the meat it feeds upon.)
To: ShadowAce
As much as people enjoy bashing Windows I sure don’t miss Unix at all. And I’m a late comer to Unix. Started using it in 1999 when I started my engineering career in aviation and manufacturing with Unigraphics. It was hard enough knowing aeronautical engineering let alone the IT experience needed to operate Unix machines.
To: ShadowAce
I can't believe nobody caught this:
> ...the Unix time counter overflows the limits of the 32-bit integer data type (at 2,147,483,647 seconds). Time will just rollover to 0 and start again.
NO IT WON'T. The integer is SIGNED, meaning the "time" will jump to the negative limit of the 32-bit two's-complement, which is roughly the evening of Dec 13, 1901. It won't be Jan 1, 1970 for another 69 years.
Right?
12 posted on
01/03/2016 5:51:23 PM PST by
dayglored
("Listen. Strange women lying in ponds distributing swords is no basis for a system of government.")
To: ShadowAce
13 posted on
01/03/2016 5:52:15 PM PST by
COBOL2Java
(I'll vote for Jeb when Terri Schiavo endorses him.)
To: ShadowAce
21 posted on
01/03/2016 8:21:37 PM PST by
Lx
(Do you like it? Do you like it, Scott? I call it, "Mr. & Mrs. Tenorman Chili.")
To: ShadowAce
The time keeps chugging on and the user has to adjust for daylight savings time and gime zone.
22 posted on
01/04/2016 5:47:51 AM PST by
Mike Darancette
(CA the sanctuary state for stupid.)
FreeRepublic.com is powered by software copyright 2000-2008 John Robinson
