|
|
Sponsored Content
Special Forums
News, Links, Events and Announcements
The Unix Crash of 2036
Post 47312 by Perderabo on Friday 6th of February 2004 11:09:53 PM
02-07-2004
First of all, do not cross-post. I have deleted your second post.
The information in that link you posted is mostly garbage. I really shouldn't dignify stupidity like that with a response. But I guess that's the only way to fight ignorance.
The 5100 was wimpy computer even in it's own day. It cannot be used to correct a modern os. It can't even store a copy of a modern os.
The alleged time traveller
states that he travelled back from 2036 to correct a unix problem that will occur in 2038. There are two very well known problems that will need a solution before then, but only one can be called a unix problem and it is nearly solved.
Jan 19, 2036 is 2^31 seconds after the unix epoch and it will overflow a signed 32 bit integer. We are starting to move to 64 bit systems now. Assuming that we retire 32 bit systems by 2038, the problem is solved. HP has stated that this is their solution for HP-UX.
A second problem will arise at the same time with the NTP protocol. The NTP protocol will need to be extended in some way prior to 2036. Admittedly we don't have a definite solution yet, but their have been proposals. I'm confident that we'll settle on a solution by then.
This problem is trivial conpared to y2k. And that was a very minor problem.
But if we fumble somehow, the solution will not involve returning to 1975 to snag an old IBM 5100.
And even if it did, we could not get our computer clocks to work, but we can build a time machine? Whoa....
The information in that link you posted is mostly garbage. I really shouldn't dignify stupidity like that with a response. But I guess that's the only way to fight ignorance.
The 5100 was wimpy computer even in it's own day. It cannot be used to correct a modern os. It can't even store a copy of a modern os.
The alleged time traveller
states that he travelled back from 2036 to correct a unix problem that will occur in 2038. There are two very well known problems that will need a solution before then, but only one can be called a unix problem and it is nearly solved.Jan 19, 2036 is 2^31 seconds after the unix epoch and it will overflow a signed 32 bit integer. We are starting to move to 64 bit systems now. Assuming that we retire 32 bit systems by 2038, the problem is solved. HP has stated that this is their solution for HP-UX.
A second problem will arise at the same time with the NTP protocol. The NTP protocol will need to be extended in some way prior to 2036. Admittedly we don't have a definite solution yet, but their have been proposals. I'm confident that we'll settle on a solution by then.
This problem is trivial conpared to y2k. And that was a very minor problem.
But if we fumble somehow, the solution will not involve returning to 1975 to snag an old IBM 5100.
And even if it did, we could not get our computer clocks to work, but we can build a time machine? Whoa....
|
|
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
We have a Unix system with two hard drives. When we tried to access it this morning it had frozen, and when we rebooted it couldn't find one of the hard drives, and had quite a few bad data blocks on the other. Of course we fear the worst: that the drive is completely gone, but were not sure how... (1 Reply)
Discussion started by: Kgatliffe
1 Replies
2. UNIX for Dummies Questions & Answers
Our SUn Solaris Server has crashed second time in 2 days, reason is not known , we are trying to determine what could have gone wrong, any ideas, the power supply seems to be fine, there is no response from keyboard,monitor etc and we had to do a hot boot yesterday..
Any suggestions what could be... (9 Replies)
Discussion started by: knarayan
9 Replies
3. HP-UX
Hi,
First of all, thanks for your help. I have downloaded freeBSD to study unix
I'm here again 'cause my HP-UX 10.x has "broken". It raise this error:
----------------------------------------------------
Diagnostic System warning:
= 0x1f005000 is POWERFAILED The diagnostic logging... (1 Reply)
Discussion started by: efrenba
1 Replies
4. Solaris
Hi,
I had witnessed my Enterprise machine 2500 series crashing last weekend. What is the command that I should use to bring the system to single user mode as the system is not responding to any of the commands :confused: ...Am still living as this is a test system.. :(
System was running on... (2 Replies)
Discussion started by: sivam
2 Replies
5. HP-UX
hi friends,
i know that when there is a crash then that memory image is
put into /var/adm/crash
but if the system hangs up and if i have access to console of
that machine then how can i take the crash dump manully.
thanks (2 Replies)
Discussion started by: mxms755
2 Replies
6. Filesystems, Disks and Memory
Hi, First post. I am not to experienced in the Unix or HP-UX world but I'm learning.
We have some problem with a HP rx4640 server. During boot it states the following:
Checking for LVM volume groups and Activating (if any exist)
Volume group "/dev/vg00" has been successfully changed.
vgchange:... (7 Replies)
Discussion started by: hoff
7 Replies
7. Solaris
hi ,
i have machine that is crashed
how i can enable core dump file & how can i find it ? :confused: (4 Replies)
Discussion started by: lid-j-one
4 Replies
8. Solaris
I am supporting a server running Solaris 4.3.The server is not having ddicated system administrator and i am requred to do minor maintenance tasks.l From few days, The server is automatically crashing and i just reboot the server. I also do not see anything in /var/adm/messages that can give an... (1 Reply)
Discussion started by: asalman.qazi
1 Replies
9. SCO
Hi there.
Well i have a really bad problem with my server:
UnixWare Version 5 Release 7
The system crash :wall: and show the error:
Panic: Kernel-mode address fault on user address 0x00000004 :eek:
If anyone knows about the reason of this error please give me a help
Sorry by my english.... (3 Replies)
Discussion started by: danilosevilla
3 Replies
10. SCO
Hi,
I need help, one of our servers is down, and all data in that Server are critical:
The Scenario:
-------------
I have a computer with the next architecture:
architecture=IA32
bus_types=PCI2.10,ISA,PnP1.0
hostname=xxx.xxx.xxx (the real name is hidden)
hw_provider=Generic AT... (2 Replies)
Discussion started by: danilosevilla
2 Replies
LEARN ABOUT OSF1
dc
dc(7) Miscellaneous Information Manual dc(7) NAME
dc - serial line/mouse/keyboard SYNOPSIS
controller dc0 at ibus0 slot 0 vector dcintr DESCRIPTION
The dc serial line controller provides DECstation 2100, DECstation 3100, DECstation 5000, and DECstation 5100 computer systems with key- board, mouse, and serial communications interfaces. The serial communications interfaces on the DECstation 2100 and DECstation 3100 provide partial modem control. The serial communications interfaces on the DECstation 5000 provide full modem control. The device special file /dev/tty01 on a DECstation 5100 provides full modem control, while the remaining ports provide no modem control at all. All serial commu- nications interfaces operate at baud rates from B50 to B9600, excluding B200. The dc ports are used as follows: Usage Graphics device keyboard at 4800 BPS Mouse or tablet at 4800 BPS Communications port 1 (w/modem control)/local terminal Communications port 2 (w/modem control)/local terminal On all systems except the DECstation 5100, serial port 2 is used for the system console port in server (that is, non-graphics) configura- tions. On DECstation 5100s, the serial port labeled 3 on the back of the system is always the system console port. The serial system con- sole port always operates at 9600 BPS, 8-bits, no parity; modem control is not supported. RESTRICTIONS
Data communications equipment attached to the console serial port in server configurations must be set to 9600 BPS, 8-bits, no parity. The scc driver enforces this restriction. FILES
console terminal local terminal local terminal local terminal (DECstation 5100 only) RELATED INFORMATION
console(7), devio(7), tty(7), MAKEDEV(8) delim off dc(7)