Tux Enlisted for U.S. Defense Program
An anonymous reader writes "Linux is a key part of the Army's massive $200B FCS (Future Computing System) initiative, it seems. RTOS vendor LynuxWorks was chosen to provide the OS for 18 weapons platforms under development, because its LynxOS-178 real-time OS can run Linux binaries -- including the "common operating environment" that Boeing is developing for FCS."
As far as I know, the Royal Navy is still considering NT for the Type 45 - maybe this will help to change their mind.
expect a sharp ramp up in anti Linux/FOSS lobbying from Microsoft via supposedly worried parties... all worried about the US's defence being trusted to a "commie OS" written by "hacker"s and other "hippy" malcontents...
Donald 'Duck' Dunn: We had a band powerful enough to turn goat piss into gasoline.
No, it's a real-time OS that can run Linux binaries. Linux isn't really a real-time OS, although there's been a lot of hackery recently to change this.
Wouldn't it piss off SCO no end if someone produced a scorun app?
They already did, and as I remember SCO were mighty pissed off.
Well, BSODs are pretty much a thing of the past, at least unless you have a defective hardware.
That said, when Windows is used where formerly an embedded OS is used, there is a tendency not to do a very good job stripping out all the stuff that's not needed. Since you aren't going to be patching things that much in the field, this could lead to known security holes on deployed systems for a long time. It may not matter, indeed usually the excuse is that it won't matter, but sometimes the unforseen happens. It's not unheard of for "embedded" versions of windows to have problems like windows file sharing turned on. The hardware engineers don't think like sysadmins.
This problem is not intrinsic to Windows; I've seen the same thing recently on a box that controlled an under vehicle scanner. It used stock SUSE with an old verison of BIND and samba, trhe3 works. The customer wanted to connect it via wireless to a central guard station. This was a bad idea. The security holes in the box are harmless as long as it is stand alone, but on a network they are huge liabilities.
At least with Linux, you can go the Linux from scratch route, which minimizes you exposure to security holes in ancient software.
Post may contain irony: discontinue use if experiencing mood swings, nausea or elevated blood pressure.
Thinking about this for a minute...
1 0/1312 50&mode=thread5 /04/10/1392 50&mode=thread
What we're REALLY talking about is blue-sky, no immediate payback, research. That is, research with a true eye to the future, not the next quarter or two, the kind of research that got us where we are today. That's the realm of deep pockets and minimal (or at least enlightened/tolerant) oversight - by stockholders or congressmen. That's also the kind of research that has been all-but-destroyed in the US by beancounting, be it corporate finance types, stockholder expectations, Congress, etc.
The US could well be moving in to an era where the only true research, the long-range stuff, goes "black" - "I could tell you, but then I'd have to kill you."
For another perspective, see:
http://technocrat.net/article.pl?sid=05/04/
Then combine it with the fact that there are others who DO see the value of long-term research:
http://technocrat.net/article.pl?sid=0
The living have better things to do than to continue hating the dead.