U.S. Army's Future Combat System Will Run Linux
jkastner writes "In 2001 Boeing was chosen to be the lead system integrator for the Army's Future Combat System. The bumper sticker description of this project is 'see first, understand first, act first and finish decisively,' and while Boeing's official FCS site doesn't have a lot of technical details, but you can find some good information at Global Security. To quote their page, "FCS is envisioned as a networked 'system of systems" that will include robotic reconnaissance vehicles and sensors; tactical mobile robots; mobile command, control and communications platforms; networked fires from futuristic ground and air platforms; and advanced three-dimensional targeting systems operating on land and in the air.' The Phase 2 request for proposals just appeared and the estimated price is $26 billion
through fiscal year 2009. The fact that the Army is spending billions of dollars on a project isn't anything new, but a little known fact is that the OS for FCS will be Linux (FAQ 4 here.)"
For such a system, linux is the obvious choice IMHO. Here's why: Consider the possibility of a malicious agent (possibly an insider) gaining unauthorized access to some of the systems. Because the whole thing is networked and remotely coordinated, the possibility for damage is immense. In that case, it is absolutely essential to detect the intrusion, track the attacker's footprints and minimize the damage as quickly as possible. And I would say linux wins hands down at this, because of its transparency. The main thing is not cost or ease of use or applications or any of the things that are usually considered, but having the innards of the system open for the administrator to see.
Does the military have to release their code because they are running on a GPL platform?
They would have to provide access to the code to people they distribute binaries to. Of course that is probably not the general public.
LedgerSMB: Open source Accounting/ERP
Not necessarily. There is nowhere in the GPL that forces you to give away your source to the world - it only forces you to distribute (or make easily available) the source to those that you are selling/giving the binaries.
Quoth the GPL section 3b (emphasis mine):
Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange
If Boeing distributes GPL'd code to the US Army it also must give any third party the source if they ask for it.
-- iCEBaLM
Even headline is Best battle ground for Linux.
Help fight continental drift.
Major General Smedley Butler, USMC.
I find him a bit more authoritative than the man who said "a little bit of hypocrisy is a good thing" when it comes to life and death issues.
-- "Why, Mr. Anderson, why? Why do you do it? Why get up? Why keep voting? Do you think you're voting for something?"
1 - I wholeheartedly agree with you. I work with FCS at work and if enough folks can keep from tweaking it to uselessness we might just have a decently working system.
I think most of the posters here just don't quite get it. FCS is part of the transformation process that DOD is currently going through. The reality is that the current force structure is not well suited for what are likely to be the primary threats of the first half of the 21st century.
Throw in sub-national groups (terrorists) and you have an even larger gap in the current force structure.