Micrsoft Flaw Causes Airport ShutDown


A bug in a Microsoft system compounded by human error was ultimately responsible for a three-hour radio breakdown that left hundreds of aircraft aloft without guidance on Tuesday, according to a report in the

http://software.silicon.com/applications/0,39024653,39124122,00.htm

This was also listed on SlashDot

My favorite post for this article:


Having to shutdown a system to maintain it's uptime is first a ridiculous idea.

Second, it took several years to find that bug because most windows machines never made it to that 49.7 days and if they did the users just assumed it was the normal because it is considered normal for windows to "lock up", freeze or whatever.

Third, replacing unix, known for it's stability, with any variant of windows (known for instability) in a system where peoples lives are at stake and then having this happen, the guys at LAX who decided to do this should be fired because they just risked a lot of lives and cause massive delays for travellers. In a political situation they would have to resign.

I remember a similar story about a aegis class cruiser stuck out in the ocean for three days because they decided to use windows. "Yea, that will work great during a war.."

*sigh* Microsoft has good lobby power and hires a fleet of sales people to keep selling their shod-ware that really should just be kept to mom and pop living rooms.

But then, this is the opionion of a guy who works only with linux and is sitting on an uptime on an openmosix cluster-leader (that also is my dev box) that looks like this:
19:03:06 up 319 days, 5:20, 3 users, load average: 1.28, 0.73, 0.37

eat your heart out LAX.. you got punk'd

Posted: Tue - September 21, 2004 at 06:14 PM      

©