Date: Wed, 27 Oct 2004 10:06:11 -0700 From: "Charles Oppermann" <charles@coppersoftware.com> To: "'Kevin Lyons'" <kevin_lyons@ofdeng.com>, "'Danny MacMillan'" <flowers@users.sourceforge.net> Cc: freebsd-chat@freebsd.org Subject: RE: Serious investigations into UNIX and Windows Message-ID: <20041027170335.671626B017@smtp4.pacifier.net> In-Reply-To: <417FCBDF.4040102@ofdeng.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>> Or how about the Navy ship that was rendered immobile for 3 days because the windows screen harware that ran the ship's controls cause a blue screen of death. Laughable if it wasn't so pathetic. << Well, let's look at the facts a little. The USS Yorktown was disabled for 2 hours, not 3 days. This was because an operator entered a zero into a data field, which the database software wasn't able to handle and wound up crashing. If an application performs an operation that attempts to divide by zero on UNIX or Windows, the process crashes if it doesn't set up an exception handler. The fault was entirely within the boundaries of the user mode code, not the platform. http://catless.ncl.ac.uk/Risks/19.88.html#subj1
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041027170335.671626B017>