Work Progressing on Army's Future Combat Systems
El_Oscuro brings us a Washington Post update on the progress of Future Combat Systems, the U.S. Army's Linux-based operating environment that has been under development for several years. The project, which currently surpasses 63 million lines of code, has received criticism for having a scope greater than that which the Army can manage. Since the program's inception, integration of commercial applications has increased the amount of code, but has also saved the developers time and money.
"Boeing and the Army said they chose not to use Microsoft's proprietary software because they didn't want to be beholden to the company. Instead, they chose to develop a Linux-based operating system based on publicly available code. Boeing's Schoen said that it is designing software so that if soldiers lose their connection, the software will automatically "heal itself," retrieving the information within seconds without rebooting."
Damn, I was looking forward to zombie soldiers.
Love many, trust a few, do harm to none.
Yes. It does run Linux.
Seven Days with Ubuntu Unity
software will automatically "heal itself," retrieving the information
Anthropomorphizing technology is rather misleading... especially in this case, "when death is on the line!"
So by avoiding Windows, no BSOD on the battlefield. But instead we risk a Colonel Panic? (sorry)
__ Someday, but not this morning, I'll finally learn to use the preview button.
As I recall, the computer very much wanted to play chess, not war. In a beautiful commentary on human stupidity and aggression it was the person who forced the computer to play war. It was the point of the movie.
db
I am literally 3000 tokens away from the chaotic crossbow --Stephen
Now the troops can compile Gentoo while on duty. Hopefully, it'll be finished when they get home.
Don't mind the extra X. Alex
General: "Where are my tanks!?"
Tech Officer: "Coming sir, we're having some dependency problems..."
Seven Days with Ubuntu Unity
I'd love to see a software license that says something to the effect of "This software will not be used to wage war or to kill any humans".
Just ssh user@host uptime.
SSH does not perform a real "login" (in the sense of allocating a pty and writing in utmp) when specifying a remote command to execute. Thus, havin zero users loggged in is normal in that case. Try it yourself.
If anything goes wrong with the project, they could always say it's General Protection's Fault.
Take Nobody's Word For It.
torrent plz
See www.defensetech.org, search for FCS, and prepare for a long, long read.
Perhaps it's time for them to upgrade to Reason 2.0.
OK.
...limited. I'm sure *some* things will find its way back out, but in practice, if a hack needs to be made on the code to make things work in an actual theater of operations, I wouldn't count on it appearing outside in the real world anytime soon.
The software in question will never see the public Internet because it's all classified Secret and above. Well, the data and operating environment are. The kernel itself will be unclass but FOUO, most likely, so that could conceivably be contributed back out if something interesting were in it. My guess is that there won't be. Military systems, even the classified variety, tend to be very vanilla by commercial standards and rarely have interesting features. It is how they are deployed that makes them redundant or otherwise suitable for their task.
So expecting contributions back will be kind of
This isn't the first military program to use Linux as a basis, btw. Force XXI Battle Command, Brigade and Below (FBCB2) uses a RTOS optimized kernel for its work, having converted from Solaris.
That said, DA has a huge Microsoft ELA contract which everyone is pushed towards. So I don't expect a lot of OSS innovation from the Army.
HBI's Law: Frequency of calling others Nazis is directly correlated with the likelihood of the accuser being Communist.
Now there's a useful metric. It says so much about quality and reliability.
Genesis 1:32 And God typed
By the sounds of it, i'd say this was written by someone who sat in on a "Future Combat Systems for Dummies" presentation. I'd imagine the "healing" process is equivalent to services restarting themselves when they fail.
There are 2 types of people in this world. Those who understand ternary and those who don't.
I don't know if the wording is intentional or not, but it seems "open sourcing" is a logical progression on the original concept of "second sourcing", and intentional or not, it should benefit both the US military and the American people as much as that that first concept did benefit the US military and the American people in the past.
...ofcourse parent is right, but this type of argument is usually spoken when the discussion is not nearly at that level.
It quenches any discussion , because no one dares to disagree.
If parent want's to partake in a discussion, try to counter the argument with something more sensible and wise - on the same level as the argument-giver.
Slashdot: stuff for news, nerds that matter, matter for news, stuff that nerd
The thing about FCS is that, when early versions of it have been tried in our present war, soldiers have found that the extra computerization is often not worth the weight of the computer. It seems to me that if the Army is going to be spending billions of dollars developing anything, they ought to be looking for a way to detect hidden explosives. FCS doesn't do a damn thing to aid against insurgencies whose primary weapon is the booby trap.
This is my sig.
We're not talking about being able to save a word document here. In order for the soldiers on the ground to have full situational awareness and ability to command, there is a lot of data that has to get from here to there. If you have a direct link from here to there, great. If that link goes down, but the software detects that sending it over this packet radio, then that fiber, bouncing it off the other satellite and downlinking it to the stryker will get it there, it should auto-reroute it that way. I think that's what they mean by "self-healing". Kind of like the original internet was designed-- on steroids... imagine if it had incorporated routing information for every FIDOnet, HAM radio, telephone, and carrier pigeon in the country.
E pluribus unum
For anyone who wonders why a lot of military software projects (but not all) turn to crap, as the parent posters allude to, read War Upon The Map.
IMHO, This is the most insightful paper into the deep interworkings of DoD politics and how it influences software design. I've experienced this myself and what the parent posters say does not surprise me in the least.
Now, does the Linux kernel never crash? Does it never have bugs? Of course it does, but it's open source, so you get a whole bunch of developers all over the world looking into the transparent inner workings of the operating system to figure out *why*, and fix it immediately.
Regarding drivers, yes, crappy drivers are a big reason that both Windows and Linux can crash. However, that's why Linux developers (and most Linux users) push strongly for open source drivers - so that they can fix the crappy drivers and make them work correctly.
We have over 10x military budget of the next country, China. This cannot end well.
Very recent article:
http://www.tomdispatch.com/post/174884/chalmers_johnson_how_to_sink_america
The radio interview is here:
http://antiwar.com/radio/2008/01/24/chalmers-johnson-3/