Allright, before the random flame's begin, I'll just say this, linux worshipers, don't go too hard on emm Almost three years ago the naval systems arm of major UK defence contractor BAE Systems took the decision to standardise future development on Microsoft Windows. an immediate effect was to commit BAE's joint venture CMS subsidiary, AMS, who specialise in naval Combat Management Systems, to implementing a Windows 2000-based CMS system for the new Type 45 Destroyer. But this prompted strong internal opposition from some of AMS' engineers, who had a sound background in Unix and who had, despite resource starvation and a companywide policy to standardise on Windows, been investigating open source alternatives as a foundation for future combat systems. They lost. Acting as spokesman for the concerned engineers Gerald Wilson compiled a 50 page dossier detailing the unsuitability of Windows as a foundation for a naval command system, and arguing that BAE's Unix history and expertise made open source UN*X a logical and viable way forward. The company then made him redundant. In May of this year Wilson reiterated his concerns to the board of BAE Systems at the company's AGM, pointing out that Windows is "proprietary technology owned by a foreign corporation", has "many and continuing security flaws", and is not even warranted by Microsoft itself for safety-related use. Why then, he asked, is AMS "shunning established engineering practice" by developing the Type 45's CMS on Windows. But in July of this year AMS announced, claiming as it did to be 'encouraging' open systems development, that Windows 2000 was "the current baseline console" for Type 45 development. AMS supports this with copious documentation on the AMS approach to open systems, which can be summarised as open, so long as it uses Windows. Earlier AMS had announced the deployment of Windows on submarine HMS Torbay, together with plans to retrofit Windows to Vanguard class and other attack submarines. And in case you're wondering, the Vanguard class boats carry the UK's Trident thermo-nuclear intercontinental ballistic missiles. So some people think that's a heap of responsibility for Windows to carry. As The Register has noted in previous pieces on BAE's interesting Windows plans, this is no trivial matter. Whereas most previous naval deployments of Microsoft Windows worldwide have been overhyped, and have dealt largely with non mission-critical, non-lethal installations, AMS really is committing the Royal Navy to Windows-based command, control and combat management systems. For much much more (allong with a letter from Gerald Wilson) Klicken Sie Hier
God help us all if Bill gets (even more) ambitious! Tridents are SLBMs if you want to be pedantic. Here's the responsibility Bill Gates has now:
Jeez, let's hope the OS doesn't crash... --"Weapons officer, fire missile one!" --"I can't, captain. It's still installing the latest Windows Security Updates!" --"I can't, captain. The missiles use Windows for Warships™ 5.0 and it's not backwardly compatible with Windows for Warships™ 4.11 that is running on the Master Launch Console..." --"I can't, captain. It's crashed again because of a conflict with Adobe Radar™ and the Corel DrawFire™ chaff launcher, and I need to re-boot..." Puts a new meaning to Blue Screen of Death...
Ok no need to take this out of context. Windows will not be controlling weapons systems propulsion or anything like that. That is what humans are for, pressing buttons. The windows will be used for logs, file storage etc. So the security concearns where around people hacking in to the windows system and stealing secret infromation. I somehow dont think this trident sub has wifi though so im not sure a passing war driver in a ship will be able to hack in.
oh oh i got one... 'dont forget to close all the windows before you submerge' eh? eh? wheres the exit?
Yea in Linux it would take a few hours to install the drivers for new missiles. In Windows it would have a little tool tip come up saying "new thermal nukes detected."
Or in case the driver are wrong error device 101 canot start. or another classic The drivers install wrong and the hardware goes nuts. *picturing nuke deployment at t-10 -9 -8 -7 officer- "captain the nukes are launching" Captain- "Did you try CTRL+ALT+DEL?" officer- "yes captain but she crashed" BOOOOOOOM end of civilization Now all thats left is Bill gates and the roaches. whats next?
1, Wrong drivers are not likely to install unless its user error. 2, You would press Alt+F4 to abort the missile launch, not Ctrl+Alt+Del.
1. correct drivers should automatically be selected in the first place. 2. if the app has crashed alt+f4 wont work, ctrl+alt+del -> close task...
Ur taking this way too seriously. Im shure the ships wepons system wont have anything to do with M$ windows.
I was reminded of this while reading this thread. You. All. Suck. On topic though, why the fuss about using a Windows-based system onboard a secure vessel for the documentation and storage of records? Its not secure? To be honest, anyone who can get onto a sub/ship and get enough access to the records will not be thwarted by whether they're using Windows or *nix. *n