Linked by Thom Holwerda on Wed 12th Dec 2012 21:47 UTC
Permalink for comment 545001
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
More Features »
Sponsored Links



Member since:
2012-02-03
If you have something like, let's say an aircraft flight computer, or anything that needs to be 100% reliable, you don't want to make any changes to the hardware or software design unless it's absolutely necessary to prevent the reliability being affected by software changes, or even bugs in the hardware (embedded chips for military/avionics applications tend to be older models which have been refined to get rid of errata detected during production for mainstream markets)
This leads to all sorts of problems - There was a rumour a few years ago that NASA was buying up stocks of original IBM PCs (and clones) off eBay because it needed some 8088s for some testing equipment for the space shuttle, and it couldn't get them anywhere else. The folks who manufacture and support the F-22 Raptor jet have the problem whereby the onboard computers use i960s, and the development suite only runs on VAX/VMS.
But I doubt any of the above run Linux, these chips were probably kept in production for 15 years to support things that predated Linux.
Edited 2012-12-13 10:56 UTC