john titor dead?

Spider if'n you're gonna go around giving Fox Network and so forth those kinda eye-deahs, Ah'm just gonna have to hurt ya wif' Banshee's chair move-thingy (as soon as she teaches it to me and as soon as I lift enough weights so I can throw a chair.)

See, now you've done it, that chair throwing thing is gonna end up in the movie now! See it's not all my fault

Honestly though this is a real typical move of people who hoax, they just don't know when to leave well enough alone.

SpiderTitor.

This news does not impress me. All this time traveling thing, covered with full mystery, I just cannot make out the sense. I believe, it is a big hoax, and some fall for those tricks.

how can a fake dude die?

how can a fake dude die?

Yeesh, take your pick buddy. Fake sleeping pills, fake gunshot wound to the head, fake car accident, fake accidental death do to imaginary auto-erotic asphyxiation.

The choices are limitless.

Could have been a fake shoot out with other fake time travelers.

Fakerj

Originally posted by Spiderj

how can a fake dude die?

fake gunshot wound to the head

Would that be with blanks?

LOL> im glad we got that cleared up

surely fake... this fake guy wanted to be famous with all that bull, but he didn't make it.

I have my opinion about JT and everything related, but I wana to add that UNIX bug is real, and it's not just made up.

small script can show you how real that problem is.

This is the standard linux server with RH on it, nothing special.

------------------------------------------------------------------

root@sinope [/]# uptime
11:23pm up 388 days, 8:57, 1 user, load average: 1.08, 0.97, 1.56
root@sinope [/]# uname -a
Linux sinope.XXXXXX.com 2.4.18-27.7.xsmp #1 SMP Fri Mar 14 05:52:30 EST 2003 i686 unknown
root@sinope [/]#
root@sinope [/]# ./2038.pl
Tue Jan 19 03:14:01 2038
Tue Jan 19 03:14:02 2038
Tue Jan 19 03:14:03 2038
Tue Jan 19 03:14:04 2038
Tue Jan 19 03:14:05 2038
Tue Jan 19 03:14:06 2038
Tue Jan 19 03:14:07 2038
Fri Dec 13 20:45:52 1901
Fri Dec 13 20:45:52 1901
Fri Dec 13 20:45:52 1901
root@sinope [/]#
------------------------------------------------------------------

As you can see, script is trying to go paste Tue Jan 19 03:14:07 2038, but bad thing happen.

Code in script is next:
-------------------------------------------------------------------------
#!/usr/bin/perl
#
# I've seen a few versions of this algorithm
# online, I don't know who to credit. I assume
# this code to by GPL unless proven otherwise.
# Comments provided by William Porquet, February 2004.
# You may need to change the line above to
# reflect the location of your Perl binary
# (e.g. "#!/usr/local/bin/perl").
# Also change this file's name to '2038.pl'.
# Don't forget to make this file +x with "chmod".
# On Linux, you can run this from a command line like this:
# ./2038.pl
use POSIX;
# Use POSIX (Portable Operating System Interface),
# a set of standard operating system interfaces.
$ENV['TZ'] = "GMT";
# Set the Time Zone to GMT (Greenwich Mean Time) for date calculations.
for ($clock = 2147483641; $clock < 2147483651; $clock++)
[
print ctime($clock);
]
# Count up in seconds of Epoch time just before and after the critical event.
# Print out the corresponding date in Gregrorian calendar for each result.
# Are the date and time outputs correct after the critical event second?
-------------------------------------------------------------------------

Regards,
Ivan

what would happen if that script is run on a machine without a realtimeclock(RTC)?

Well, yes, we know the Unix bug is real. But it doesn't DO anything other than mess with your dates.

I have at home (on my network) a couple of old non-Y2K compliant computers. They are running just fine (fileserver), except the date stamp isn't reliable. That's no big deal.

And just as we don't use Windows 95 any more, by 2036 we won't be using 32 bit Unix.

This is the standard linux server with RH on it, nothing special.

-snip-

As you can see, script is trying to go paste Tue Jan 19 03:14:07 2038, but bad thing happen.

Please keep in mind that linux came from minix, and not from the BSD or SysV flavors of UNIX (i'm talking the kernel here, not userland tools. we all know linux uses many bsd tools in it's userland). I should hope the bug wouldn't be reproduced on purpose within a fresh codebase. I'm fairly certain that if you grep through the kernel source you'll find some comments related to a work around for that bug.

Also, most current revisions of UNIX do have means to get around this as well- the problem is the thousands of systems still running OS revisions from 10-15 years ago (it's far more common that anyone would think). There *will* be systems that break from this bug.



[edit on 15-7-2004 by negativenihil]

I have at home (on my network) a couple of old non-Y2K compliant computers. They are running just fine (fileserver), except the date stamp isn't reliable. That's no big deal.

Yes, but you're not a financial instituion, who has to calculate things like interest based on the date. If the system's date is wrong, the calculation will be wrong.

I can promise you, there *will* be 32bit UNIX systems in service in 2036.

maybe but there is a good chance we will be above 32-bit by then.

Originally posted by Asclepius
maybe but there is a good chance we will be above 32-bit by then.

if by "we" you mean consumers, sure it's happening already with Intel and AMD's latest processors. Consumers upgrade hardware and software at a MUCH faster pace than most large buisnesses.

Originally posted by negativenihil

Originally posted by Asclepius
maybe but there is a good chance we will be above 32-bit by then.

if by "we" you mean consumers, sure it's happening already with Intel and AMD's latest processors. Consumers upgrade hardware and software at a MUCH faster pace than most large buisnesses.

lol. im well aware its already out there. im jsut assuming it will be out as the standard platform at least.

Originally posted by Spiderj

how can a fake dude die?

Yeesh, take your pick buddy. Fake sleeping pills, fake gunshot wound to the head, fake car accident, fake accidental death do to imaginary auto-erotic asphyxiation.

The choices are limitless.

Could have been a fake shoot out with other fake time travelers.

Fakerj

Sounds kinky

13 Monkeys... I mean, come on already. Bruce Titus goes back in time, discovers he can help humanity, and dies while his adolescent self still lives...

All we need is some time spanning nemesis. Maybe the Time Lord (Doctor Who) could stop by. Yeah! And Titus reveals his time car was actually a TARDIS!

Originally posted by Asclepius
maybe but there is a good chance we will be above 32-bit by then.

Linux already supports 64-bit.

Also, I did a WHOIS lookup of the IP provided within that quote (bet all you busy titor-flamers didn't think of that immediately, did ya ) and this is what I got:

OrgName: BellSouth.net Inc.
OrgID: BELL
Address: 575 Morosgo Drive
City: Atlanta
StateProv: GA
PostalCode: 30324
Country: US

Atlanta, Georgia is where this individual seems to be. Titor notes that he lives in central Florida. Although the states are close, I doubt they would maintain much contact with eachother. Any thoughts?

Originally posted by Blackout

Originally posted by Asclepius
maybe but there is a good chance we will be above 32-bit by then.

Linux already supports 64-bit.

im aware. wasn't there also a 64-bit version of XP??? I know Longhorn will have 64-bit but i can't remember if there was a 64-bit XP

There is a 64-bit XP.

www.microsoft.com...

Anywho, let's not get off topic.