Commentary

Paul McDougall
Editor At Large, InformationWeek  

Apple Bans Nuclear Plants From Running 'Leopard' OS

While researching a story about Apple letting users run Leopard in a virtualized environment, I came across some interesting language in the software's license agreement. Who knew you can't use Leopard to run a nuclear power plant, or a 747?

While researching a story about Apple letting users run Leopard in a virtualized environment, I came across some interesting language in the software's license agreement. Who knew you can't use Leopard to run a nuclear power plant, or a 747?The end user license agreement for the server version of Leopard, aka OS X 10.5, contains this list of restrictions.

Leopard is "not intended for use in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control systems, life support machines or other equipment in which the failure of the Apple software could lead to death, personal injury or severe physical or environmental damage."


More Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Apple is concerned about environmental damage? Didn't Greenpeace just discover that the iPhone is loaded with nasty chemicals?

Anyhow, it seems Apple CEO Steve Jobs just doesn't want the liability that might arise if Leopard were to be installed in, say, the radar system that tracks planes going in and out of JFK airport.

I'm not sure if the EULAs for previous versions of the Mac OS contain these restrictions, but I'm sure the blogosphere will let me know.

By imposing these limits, is Jobs just doing his, uh, job and protecting Apple shareholders from lawsuits filed by the victims of, say, a meltdown at a nuclear plant that was running Macs?

Or is he wimping out?

I mean, what if Microsoft and all the Linux and Unix vendors imposed the same restrictions. On what software would the nation's critical infrastructure run -- BeOS?


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links