Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
×
Portables Hardware

Land Warrior Army Suits Simplified, Linux-ized 361

Dosco Jones writes 'The Army is drastically simplifying the makeup of its high-tech soldier ensemble, the Land Warrior, in an effort to make the system less prone to failures and easier to use,' National Defense reports. Defense Tech continues: 'After the last version of Land Warrior failed reliability tests earlier this year, the Army switched gears and decided to make the system less complex and modify the hardware to make it compatible with the new [and controversial] Stryker infantry vehicle. Changes include a more simplified data bus and a Linux-based operating system, as opposed to Windows. 'Evidence shows that Linux is more stable. We are moving in general to where the Army is going, to Linux-based OS', says the program's manager, Lt. Col. Dave Gallop."
This discussion has been archived. No new comments can be posted.

Land Warrior Army Suits Simplified, Linux-ized

Comments Filter:
  • Heh... (Score:5, Funny)

    by EvilSporkMan ( 648878 ) on Monday October 27, 2003 @06:01PM (#7323221)
    Evidence shows that Linux is more stable
    I'm sure they'll be hearing from Commander Gates about that one shortly...
    • Re:Heh... (Score:5, Funny)

      by Nighttime ( 231023 ) on Monday October 27, 2003 @06:05PM (#7323273) Homepage Journal
      Evidence shows that Linux is more stable
      I'm sure they'll be hearing from Commander Gates about that one shortly...


      Never mind that, imagine Darl trying to get his $699 licence money:

      Darl: "Oh yeah? You and whose army?"
      • > Never mind that, imagine Darl trying to get his $699 licence money:

        "Some people have told me they don't think a fat penguin really embodies the grace of Linux, which just tells me they have never seen a angry penguin charging at them in excess of 100mph. They'd be a lot more careful about what they say if they had."

        - Linus Torvalds

        Seems the Army's catching on. Darl McBride, consider that as a warning.

      • The Army does use SCO for a bunch of her computer systems, like for Field Artillery fire direction. It's kind of fun to watch people discover that backspace and delete aren't what they're used to.
    • I'm sure they'll be hearing from Commander Gates about that one shortly.

      I imagine Commander (or Darth?) Gates saying: "Alert my Star Destroyer to prepare for my arrival." :-)

      z
    • Re:Heh... (Score:4, Informative)

      by Alien54 ( 180860 ) on Monday October 27, 2003 @06:29PM (#7323497) Journal
      well the original config was:

      "Land Warrior [globalsecurity.org] Initial Capability" (LW-IC) was supposed to be the first step in a long process of networking soldiers together. Each fighter would get equipped with a small, 500 megahertz computer running Windows 2000, a radio, a customized rifle and a helmet-mounted display eyepiece. All of these would be linked together. And all that a soldier sees or says could be sent to each other or to headquarters.

      and the findings were:

      the system was deemed 'unreliable' and unlikely to survive the rigors of combat

    • Halo (Score:2, Funny)

      by Anonymous Coward
      Commander Gates - wasn't he in Halo?

      Linux is all very well, but if you want auto-aim and stuff to really piss the opposition off, I'd go into battle with an X-box strapped on my back.

      You can see the Pentagon news briefs; "we can't fight Al Qaeda because they haven't subscribed to X-box Live..."
    • Re:Heh... (Score:4, Funny)

      by mikeee ( 137160 ) on Monday October 27, 2003 @10:12PM (#7325214)
      It's not Commander Gates they're worried about, it's General Protection Fault.
  • Scary,,, (Score:5, Funny)

    by DCowern ( 182668 ) * on Monday October 27, 2003 @06:01PM (#7323224) Homepage

    Each fighter would get equipped with a small, 500 megahertz computer running Windows 2000...

    "Although it has been much improved over earlier prototypes, the system was deemed 'unreliable' and unlikely to survive the rigors of combat," National Defense says.

    The thought of Windows even being considered for such a mission critical application (i.e. keeping our boys alive) scares the bejeezus out of me... kinda brings a new meaning to "blue screen of death".

    • Re:Scary,,, (Score:5, Funny)

      by EinarH ( 583836 ) on Monday October 27, 2003 @06:22PM (#7323437) Journal
      It's cheap Karma but someone needs to do this:

      Clippy: "It looks like you are trying to press the trigger on your weapon, would you like some help?"

      1. Learn how to reload you new high tech gun with a 20 minute walk-through.
      2. Install new Patriot-skins on the hud of you display.
      3. Get help on the installing the latest Friendly Fire buffer overflow.
      4. Return home and shoot the person who made this sytem.

    • The thought of Windows even being considered for such a mission critical application (i.e. keeping our boys alive) scares the bejeezus out of me... kinda brings a new meaning to "blue screen of death".

      Like it or not, Windows does run lots of mission critical applications, the NT line always did. Maybe not as life-threateningly critical as this, but still. That they consider it is natural, and that the reject it shows that the system works!

      How many other operating systems would be under consideration? Not
      • I wonder if they considered embedded windows xp.
      • They are actually "entrusting vital systems to an OS that" they can have total control over themselves. "They are learning through experience" that win2k is not stable enough for their purposes and that the "high quality OS for free" is good enough for IBM, Dell and HP. Since DARPA has a large core of UNIX programmers Linux is pretty much the obvious choice. The initial choice for win2k probably went against the grain of DARPA developers to begin with. "Where else than in OSS land do you get anything for
    • At least its only windows 2000. Can you see it if they included clippy?

      It looks like you're trying to Flank the position. Would you like me to:

      • Lay down covering fire
      • Call in air / artillary support
      • Follow you
      • Draw their fire
    • Re:Scary,,, (Score:5, Insightful)

      by 3Suns ( 250606 ) on Monday October 27, 2003 @08:13PM (#7324333) Homepage
      The rigors of combat? Hell, it doesn't even survive the rigors of internet browsing or playing DVDs. Forget active combat!
    • Right! Imagine this:

      Jungle scene: Background battlefield noise, explosions, screams of pain;
      In the bushes: Foreground beep, booting sounds, moan of anguish.

      Wait a sec boys... hold the war! I gotta reboot...
  • Linux, eh? (Score:4, Funny)

    by Anonymous Coward on Monday October 27, 2003 @06:02PM (#7323232)
    The cost of war just went up by $699
  • I hear... (Score:5, Funny)

    by Anonymous Coward on Monday October 27, 2003 @06:03PM (#7323242)
    The Marines are going to run FreeBSD, because linux just isn't tough enough.
    • by Anonymous Coward on Monday October 27, 2003 @06:08PM (#7323307)
      The Marines are going to run FreeBSD

      Yeah, I hear that Marines aren't afraid to die.
    • Sadly (Score:5, Interesting)

      by Theatetus ( 521747 ) on Monday October 27, 2003 @06:09PM (#7323316) Journal

      Sadly, we run Windows NT. We'd also never get expensive crap like a warrior suit... hell, my deuce-gear was first issued in 1964 according to the supply ticket.

      Sure, we got the cool new camouflague that makes us look like the Waffen SS, but as far as cool crap like this, we have to wait 5 years for the Army to get tired of playing with it.

      • Sure, we got the cool new camouflague that makes us look like the Waffen SS,

        Yeah, I just noticed that. I was loitering around the Pentagon when a fellow came through in an odd camo, and I said "It's that scout from BF1942!"

        PS. I later saw some of the simulation programs the DoD uses to test battleplans for the next decade. The Navy's ran on Linux, as did the MC and Army's. The Air Force used a Solaris program. The only Microsoft(tm) system in evidence was something that ran MySQL + PHP to tally up th
      • Over in Saudi, for Desert Storm, we were issued M16s without a forward assist. You could fire one shot and then it'd jam. I guess, after that, you could swing it like a bat or throw it. Glad I took along my 1942 RemingtonRand 1911. Just loose enough to keep functioning with all the grit. 37th AeroMedical Evacuation Group (USAFR) MacDill AFB
        • Re:Sadly (Score:3, Interesting)

          by Dun Malg ( 230075 )
          Over in Saudi, for Desert Storm, we were issued M16s without a forward assist. You could fire one shot and then it'd jam. I guess, after that, you could swing it like a bat or throw it. Glad I took along my 1942 RemingtonRand 1911. Just loose enough to keep functioning with all the grit. 37th AeroMedical Evacuation Group (USAFR) MacDill AFB

          That's the Air Force for ya'. They haven't made the M-16 since the mid 60's (M-16A1 has forward assist) and the AF hasn't gotten rid of theirs yet? Of course, PT testin

  • by mr_tommy ( 619972 ) <tgrahamNO@SPAMgmail.com> on Monday October 27, 2003 @06:04PM (#7323247) Journal
    Fatal error : Could not find gunfile.dll. Please reboot your soldier. now it will be : YOU! STOP, OR I'LL SEND YOU TO /DEV/NULL/.
  • With a name like that [imdb.com], it was bound to fail!
    • Re:Stryker? (Score:5, Informative)

      by Wyatt Earp ( 1029 ) on Monday October 27, 2003 @06:17PM (#7323397)
      http://www.globalsecurity.org/military/systems/gro und/iav.htm

      "In February 2002 the Army named its new interim armored vehicle after two soldiers who received the Medal of Honor. The Stryker is named in honor of Spc. 4 Robert F. Stryker, who received the Medal of Honor for his actions during the Vietnam War, and Pfc. Stuart S. Stryker, who received the award for his actions during World War II. Both men were killed in action. They were not related."

      http://www.army.mil/cmh-pg/mohiib1.htm

      "Rank and organization. Private First Class, U.S. Army, Company E, 513th Parachute Infantry, 17th Airborne Division. Place and date: Near Wesel, Germany, 24 March 1945. Entered service at: Portland, Oreg. Birth. Portland, Oreg. G.O. No.: 117, 11 December 1945. Citation. He was a platoon runner, when the unit assembled near Wesel, Germany after a descent east of the Rhine. Attacking along a railroad, Company E reached a point about 250 yards from a large building used as an enemy headquarters and manned by a powerful force of Germans with rifles, machineguns, and 4 field pieces. One platoon made a frontal assault but was pinned down by intense fire from the house after advancing only 50 yards. So badly stricken that it could not return the raking fire, the platoon was at the mercy of German machine gunners when Pfc. Stryker voluntarily left a place of comparative safety, and, armed with a carbine, ran to the head of the unit. In full view of the enemy and under constant fire, he exhorted the men to get to their feet and follow him. Inspired by his fearlessness, they rushed after him in a desperate charge through an increased hail of bullets. Twenty-five yards from the objective the heroic soldier was killed by the enemy fusillades. His gallant and wholly voluntary action in the face of overwhelming firepower, however, so encouraged his comrades and diverted the enemy's attention that other elements of the company were able to surround the house, capturing more than 200 hostile soldiers and much equipment, besides freeing 3 members of an American bomber crew held prisoner there. The intrepidity and unhesitating self-sacrifice of Pfc. Stryker were in keeping with the highest traditions of the military service."

      http://www.army.mil/cmh-pg/mohviet2.htm

      "Rank and organization: Specialist Fourth Class, U.S. Army, Company C, 1st Battalion, 26th Infantry, 1st Infantry Division. Place and date: Near Loc Ninh, Republic of Vietnam, 7 November 1967. Entered service at: Throop, N.Y. Born: 9 November 1944, Auburn, N.Y. Citation: For conspicuous gallantry and intrepidity at the risk of his life above and beyond the call of duty. Sp4c. Stryker, U.S. Army, distinguished himself while serving with Company C. Sp4c. Stryker was serving as a grenadier in a multicompany reconnaissance in force near Loc Ninh. As his unit moved through the dense underbrush, it was suddenly met with a hail of rocket, automatic weapons and small arms fire from enemy forces concealed in fortified bunkers and in the surrounding trees. Reacting quickly, Sp4c. Stryker fired into the enemy positions with his grenade launcher. During the devastating exchange of fire, Sp4c. Stryker detected enemy elements attempting to encircle his company and isolate it from the main body of the friendly force. Undaunted by the enemy machinegun and small-arms fire, Sp4c. Stryker repeatedly fired grenades into the trees, killing enemy snipers and enabling his comrades to sever the attempted encirclement. As the battle continued, Sp4c. Stryker observed several wounded members of his squad in the killing zone of an enemy claymore mine. With complete disregard for his safety, he threw himself upon the mine as it was detonated. He was mortally wounded as his body absorbed the blast and shielded his comrades from the explosion. His unselfish actions were responsible for saving the lives of at least 6 of his fellow soldiers. Sp4c. Stryker's great personal bravery was in keeping with the highest traditions of the military service and reflects great credit upon himself, his unit, and the U.S. Army."
    • well..
      dunno.

      theres one other stryker that is 'hard'..

      http://www.jeff-stryker.com/

      though, i havent seen his films but iirc he swings both ways.
  • Linux (Score:5, Funny)

    by Anonymous Coward on Monday October 27, 2003 @06:04PM (#7323260)
    "The enemy is approaching. Fire away!"
    "I can't, sir... There's no compatible driver for this missile launcher yet!"
    • "The enemy is approaching. Fire away!"

      ...and Windows would probably launch fucking Minesweeper after an order like that.

      ...or Clippy.

      "It looks like you're about to die. Would you like to:"

      • Write a last will and testament?
      • Say a prayer?
      • Run like hell?
      • Kiss your ass goodbye?
  • by No Such Agency ( 136681 ) <abmackay@@@gmail...com> on Monday October 27, 2003 @06:05PM (#7323263)
    I recommend downgrading all versions of Soldier to the basic "naked man with stick" functionality which was immensely popular and robust for a good portion of the version history of Soldier. There'd be a lot less problems in the long run, as long as all users comply with the downgrade.
  • by Anonymous Coward
    Kind of messy in the midst of combat, having to phone Micro$oft with a soldier's product activation information, so that might be one of the reasons why the Linux choice.
  • by Dr. Bent ( 533421 ) <ben.int@com> on Monday October 27, 2003 @06:05PM (#7323274) Homepage
    ...it's all made by the lowest bidder. And by that criterion, Linux is the clear choice.
    • Actually, it's not all bid on now.

      If there is a product that is better than the others out there, or a specialized product that no one else makes the DoD can buy it outright, do a streamlined bid process or allocate money to commanders or even issue money to a soldier to make up for thier personal purchase.

      Theres a file I found in July talking about what worked and didn't work in Iraq in the equipment the soldiers used, and they covered all sorts of things, from sniper scopes, to Talkabouts to Camelback w
    • by gmcraff ( 61718 ) <gmcraffNO@SPAMyahoo.com> on Monday October 27, 2003 @07:11PM (#7323816)
      I know the parent is being funny, but here's a little less funny but more real info from the inside of the process.

      According to the Federal Acquisition Rules (FAR), the contract selection must go to those who provide "best value". "Least bid" is only appropriate when all other factors weight out equally. This assumes that the contracting office is following all the rules, or at least trying to.

      Now, these factors we're talking about are all laid out in the publications soliciting industry input or proposals. Such things as previous contractor performance, technical approach, capabilities proposed vs requirements, the proposed contractor team composition, timelines, certifications like ISO 9000 are used as criteria, or a super- or sub-set of this list. Then the source selection team, which can be very small or very large, goes through each and every one of the proposals received and weighs them up according to criteria estabilished before hand. These criteria are weighed, such as TECHNICAL and TEAM SKILLS being twice as important as any of the rest. COST is one of the factors weighed, but it has been generally accepted that the only person who weights COST to be of equal or higher weight than the other factors combined is a complete idiot because history has show this to be the recipe for a complete catastrophe and waste of taxpayers' money.

      Of course, requirements are the biggest thing in all proper acquisitions. If you don't match up to the requirements, or you can't get there in a series of upgrades or refinements, it doesn't matter how cheap you are. But the real catch is how the requirements are written. If, for example appropriate to this audience, they are written in such a way that only a particular operating system can match up, then only the proposals outlining a system built on that operating system can possibly make it past the first cut. This happens when the requirement writer can't separate his vision for HOW the thing should be built from WHAT it needs to DO. And let's face it: the requirement writer is almost certainly too close to the problem to be able to think of unique or elegant ways to solve the problem with the least resources required. He's more likely to be thinking, "I want a thing that does this, which should be like this thing I already have, only MORE SO." And if what you have is a Windows system, and that's all you know (or you're frightened by this Linux/*BSD/etc stuff), then you'll write the requirements to fit what you know.

      This isn't to say that requirement writers are particularly bad or unqualified people. Some of them are truly excellent. Most just need some training in how to stay in their lanes.

      No, the bad people are the ultraconservative, underinformed, technically no-longer-qualified information security people. They don't like anything that hasn't been previously approved by their organization. Anything new must jump through a hoops process that by the minimum timeline takes YEARS, and they'll change the process twice during your progress and require you to start over. They won't get involved in your acquisition process because they "haven't got time for that", but they have time to tell you to re-engineer the entire system after you spend four years building it because it doesn't fit in with some asinine security regulation that either didn't exist when you started, or is so outdated that it qualified for social security, and almost certainly isn't applicable to your system. You can't argue against them because that would be arguing against SECURITY, and you might as well be questioning the value of MOM and APPLE PIE in their eyes. Their simple word can cost a colonel his star, or a GS-15 his SES, so you've got to be backed up one that a) has a lot of balls; b) takes you seriously; and c) is convinced he should do the job right and the star will attend to itself; to have any chance.

      And how did I come up with these wild revelations about contracting in the government? Well the first half is straight out of t
  • Land Warrior (Score:5, Insightful)

    by Anonymous Coward on Monday October 27, 2003 @06:06PM (#7323281)
    One thing that nobody's managed to explain to me is how your average 11 Bravo is expected to carry an extra fifty-odd pounds of electronics.

    Land Warrior? I'd settle for a fucking infantry boot that wasn't the height of 1950's technology.
    • Re:Land Warrior (Score:2, Informative)

      by MystikPhish ( 218732 )
      Ummm... we already got that! [army.mil]

      Thanks for the thought, though!

      I got out in 2000, but I was still in the USMC (0311, grunt, qty. 1) when we switched from the old LPC (Leather Personnel Carrier) to the new boot. I didn't get to try the desert boot, but I really liked the ICB, the first version was a bit hot/heavy, but I have heard from buddies that it is better now.

  • So if the Army can pay $hitloads for a bunch of bolts, SCO must be positively drooling for what they can get out of the Army for a Linux licence.
  • ...do you think the government will work to thwart SCO's suit?
  • by overbyj ( 696078 ) on Monday October 27, 2003 @06:10PM (#7323323)
    The Army chooses Linux to build the soldier of the future but the Department of Homeland Security chooses Windows. Maybe the Army can protect us from the Department of Homeland Security!
  • by burgburgburg ( 574866 ) <splisken06.email@com> on Monday October 27, 2003 @06:10PM (#7323325)
    Say good-bye to the promising career of Lt. Col. Dave Gallop.

    Speech like that weakens Windows, which weakens the economy and cuts down on campaign contributions to GOP causes. W and the "Justice" Department will be having Gallop arrested as an obvious enemy combatant any second now.

    More stable. Like that's so important. It hasn't mattered to Windows for years!

  • by Idou ( 572394 ) * on Monday October 27, 2003 @06:11PM (#7323329) Journal
    Everyone knows that they are just covering up the fact that they couldn't afford to buy a REAL OS, you know, with the lack of funding the U.S. army gets and all.

    Nobody uses Linux for an other reason than its cost, which is actually more than Windows when you take in account its TCO cause windows has all those neat add ons that make life more productive, like clippy.

  • by RedA$$edMonkey ( 688732 ) on Monday October 27, 2003 @06:11PM (#7323331)
    "The minesweeper simulation did not seem to adequately train our engineers"
  • Interesting note (Score:5, Interesting)

    by UnknowingFool ( 672806 ) on Monday October 27, 2003 @06:13PM (#7323353)
    The LW SI will have a single processor. The previous LW had a dual processor, which frequently malfunctioned. Other changes include a more simplified data bus and a Linux-based operating system, as opposed to Windows. ?Evidence shows that Linux is more stable. We are moving in general to where the Army is going, to Linux-based OS,? said Gallop.

    I'll let other /.ers discuss the reliability of Linux over Windows, but an interesting note is that the original LW had 2 processors but the newer version has 1. The question is whether part of the reliability issues on 2 processors is due to Windows handling multiprocessors or simply the hassles of getting 2 processors to work together. The articles do not discuss in detail what really happened. Simplicity is however a good thing when it comes to reliability. It would be something if the stuck with a 2 processor design but made it work with Linux.

    • Re:Interesting note (Score:4, Interesting)

      by child_of_mercy ( 168861 ) <.moc.tcatoir-eht. .ta. .yobnhoj.> on Monday October 27, 2003 @06:43PM (#7323589) Homepage
      For what they say they want to do processing power needn't be excessive.

      but heat buildup could be a real problem for reliablity.

      I'd imagine passive cooling would be the order of the day too as even quiet fans, heat pumps, peltiers, or whatever would add another point of failure.

      I'm just guessing but a less powerful (in every sense) set up might have made more sense for passively cooled mobile reliability.
    • Perhaps by "dual processor" they're not refering to multiprocessing but rather redundancy. I can't see them needing a huge amount of processing power - but I can see the need for some kind of a failover mechanism in case one processor dies during combat.
  • But I guess I'm going to have to go ahead and write my own. As soon as Motorola's HC08 chips support ZigBee networking I'm going to be deploying a paintball tactical network.

    Then it's time to build the automated 20-oz paintball mortar. Let's see you wipe THAT off when no one's looking!
  • by deadlinegrunt ( 520160 ) on Monday October 27, 2003 @06:16PM (#7323387) Homepage Journal
    "You have loaded new ammo in your gun -- Please contact Microsoft for a new activation key."
  • by rikomatic ( 673311 ) <rikomatic@yaho[ ]om ['o.c' in gap]> on Monday October 27, 2003 @06:17PM (#7323391)
    The Military Analysis Network [fas.org] has a more complete description of the Landwarrior's various subsystems. Sounds like you would need a very stable OS to handle all the communications, geographic, thermal imaging, and directional software it must be running.
  • by Crashmarik ( 635988 ) on Monday October 27, 2003 @06:17PM (#7323393)
    Well I guess this contradicts Mr. Balmers comments about windows being better because there was someones job at stake. It seems when its a life at stake its time to pick linux.
  • ... RedHelmet? Although SuSE might have a leg up here on the bidding, since their logo is already green.

  • to conquer the world. Imagine beowulf of marching Penguins, armed to their teeth ...
  • by mrAgreeable ( 47829 ) on Monday October 27, 2003 @06:21PM (#7323426)
    Stryker info [global-defence.com]

    And, of course:
    Stryper info [stryper.com]
  • by SeanTobin ( 138474 ) * <byrdhuntr@hot[ ]l.com ['mai' in gap]> on Monday October 27, 2003 @06:25PM (#7323464)
    Steve: "Bill, we have a problem. It appears that not only are second world countries and small states switching to linux. The US Army is beginning to use linux in its new systems." A nervous Steve mentions.

    Shocked, Bill replies "Enough of this. Its time to begin Operation Rotanimret! Is everything in place?"

    Steve: "Yes, the worms are ready. The submarines are still running WindowsCE, and the governator of Califorenia is backing us up."

    Bill: "Excellent! Release the worm immediately. Something tells me this patch won't make it to the update servers any time soon." Bill says ending with an evil "Muhahahahaaa!"

    Steve, now sweaty under the arms reads from an emergency plan: "We had better leave immediately to the bunker. Our estimates show that we will have total control over every windows PC in the world in under 4 hours. Beginning 2 hours from now, the distruction of non-windows pc's will begin."

    Bill: Excelent. To the SUV then!

    -- Bill and Steve are on the road heading to thier secret underground bunker ---

    Bill: Do you remember where the bunker was?

    Steve: Not exactly.. I never drive anywhere myself anymore. I'm pretty sure its in this direction though. I'll just ask the car... AutoPC show me a map to the secret underground bunker.

    --BSOD--

    Bill: Damn. At least this isn't a drive-by-wire SUV. We'd really be in trouble. Give it a second to reboot.

    Bill: AutoPC show me a map to the underground bunker.

    --Map displayed showing bunker is behind them--

    Bill: Darn steve, we have to turn around. Its showing that we passed the bunker.

    --Steve turns around and begins following the map--

    Steve: Well, here we are. It must be under this penguin factory.

    Bill: Wow.. good idea. Whoever hid the secret lair under a penguin factory needs to get a bonus if they survive the nuclear winter we are about to unleash.. in 20 minutes, we need to hurry! Pull in over there.

    Steve: Ok. we're here. What the--- Bill, why is your face on the dashboard map?

    Bill: Don't know.

    AutoPC: Thank you for using AutoPC. This vehicle is being sacrificed to destroy the linux tyrany. Have a nice day!

    Bill and Steve look at each other

    --Car explodes outside the penguin factory--

    [to be continued!]

    [feel free to continue :) ]
  • In other news, Steve Ballmer has just flown to the Pentagon offering to give the Armed Forces a price match for Windows licenses compared to the less expensive (read free), more stable, GNU/Linux Competitor.

    Steve Ballmer was allegedly overheard saying, "And if that doesn't work, I'll write them a check to use my !^$&$@ software. Give me that M-16 son, I want to put a bullet in the head of that penguin."
  • As usual, the press is waiting with cameras and lights as Linux comes ashore. The enemy, Microsoft, can see the whole thing on TV, and as usual, that will not make the slightest difference to the outcome of this skirmish.

    It's called "overwhelming force."

  • Screw this (Score:3, Funny)

    by Lord_Dweomer ( 648696 ) on Monday October 27, 2003 @06:29PM (#7323493) Homepage
    I can't wait till we get powered exo-skeleton armor like from Exo-Squad. Seriously, we have the technology, why aren't they implementing it already. Anime has been at the cutting edge of this crap for years! They already have building sized mecha that can fly in space, are powered by nuclear reactors, have city-leveling weapons, AND an interface simple enough to be controlled by any hapless shy boy who happens to find himself in the cockpit during the heat of battle.

  • I know Linux is stable as a rock on my machines, but for something that lives depend on I'd expect more than a monolithic kernel. QNX is the only company that's confident enough in its OS to let it be used in life-threatening situations, so why not use it here? It can't be that it's Canadian, can it?
  • The real reason for switching away from Windows was that the error messages were doubleplusungood:

    Application "force against Iraq" has performed an illegal operation. General Protection Fault.
  • The Truth About the Kursk Disaster

    Some new information has come to light over the Kursk disaster. For those with short attention spans, the Kursk was the submarine that blew up and sank in the Artic Ocean killing all 118 on board. The Russians tried to blame the incident on a collision with an unidentified object. However, sonar tapes which recorded the blasts (a small one at first, then a much larger one two minutes later) cast doubt on these claims. A whistle blower within the Russian military has leak
  • Hmmm. Instead of thinking that MS bought it's way into the US Military, I think it's important to remember that it has existed for over two hundred years while Linux is little more than two decades old.

    So back in the 80's when the military was getting all wizbang there were two general desktop options: Sun and MS. In the end it turned out that the MS boxes were cheaper in bulk and so primary development occured on them.

    Fast forward to the present day and you have the current situation: a monolithic org
  • by Wellspring ( 111524 ) on Monday October 27, 2003 @06:55PM (#7323688)
    The army's been very good about its transformation plan. In case some /. readers haven't heard it in its full glory, here it is:

    OK, pre-9/11, the Army embarked on a very controversial plan. Basically, they looked at all the wars that we have any realistic chance of being in. Then they looked at what we have to fight them.

    The problem was this: we have oodles of heavy tanks, which pretty much kick all kinds of ass. But they can only win where they can be brought to bear. They're so heavy that they require massive transportation time and cost (not to mention a friendly port to set up in). Another problem is that while tracked vehicles can be heavier and go places that wheeled vehicles can't, they are very maintenance intensive. They need lots of fuel and spare parts, which requires still more ships or a massive airlift.

    Bottom line: unless we're fighting on the Korean penninsula or in Europe, where were pre-positioned, it would take six months to fight a war anywhere, and that's assuming we had a friendly neighbor to give us a place to set up in.

    The result was the Army transformation plan. The idea is that they would get phase out most of their heavy tank divisions, and replace them with smaller, modular formations called Brigade Combat Teams. The BCT's job would be this: assuming the Air Force can clear a drop zone, we ought to be able to put a brigade anywhere in the world, opposed or not, within 96 hours of the President saying so. Four brigades within 14 days, and more (I don't remember how many) within 90 days. That's even if we drop in the middle of a shooting enemy.

    One way we could do this was to get a vehicle that could be a little less armed and armored, and could be a little less mobile, but MUST be air-transportable. That's the Stryker. Think of it (excuse the roleplaying reference) as an Omnimech: a vehicle that is designed to be reconfigurable to do lots of different missions. So there's a communications loadout, and a tank-killer loadout and an infantry-carrier loadout, and lots more.

    Post 9/11 lessons have been mixed. On one hand, invincible tanks in Germany did us absolutely no good when we suddenly found ourselves at war in Afghanistan. On the other, when we had a year to move them to Iraq, our tanks did extremely well-- and as DefenseTech points out, absorbs fire that would have destroyed Strykers. The gripping hand is that long occupations like Iraq are better suited to Strykers, LAV's or armored Hummers than to heavy tanks and APC's.

    So, like most things, one tech isn't necessarily better or worse than another. You use whatever best fits the situation you're in. On that basis, I like the Stryker. An all-Stryker Army? No. But it is a very valuable program.

    Most American war plans in the 90's were built around the idea of a set-piece conflict with an adversary (like China, Iraq or North Korea) that while not exactly equal in technology was at least comparable. 9/11 proved that asymmetrical conflicts would also happen: conflicts where the enemy's main goal is to demoralize our political leadership because they can't defeat us militarily.

    And in those cases, we can't count on someone granting us entry, we may need to move very fast, and it might be in some remote corner of the world, far from our forces.

    Related to that is improved command and control. Many of our casualties in the Gulf War were friendly-fire, so the Army worked on reducing that, too. Vehicles can now see on a map where others in their unit are (just like in a first-person shooter like BF1942). The problem is that the equipment is still too heavy and battery-draining to be useful for infantry. Hopefully, a vehicle-run 'subnet' can help alleviate this. And running it w/ Linux will hopefully improve efficiency and reliability.

    Overall, I think the Army's on the right track with this. I'd hate to lose our heavy tank divisions-- those come in mighty handy. But a less powerful force that can actually get to the battle is better than an invincible juggernaut that is stranded somewhere else.
  • Government programs take too long to acuqire - 4-8 years for a system like that.

    meaning that by the time they actually wanted to start building the and fielding them, they couldn't buy the PIII-500's that they had speced/tested any more.

    this is a constant issue with military programs being built on COTS. For example - the DSP farms of XServes going on the subs are already obsolete - they could have used half as many G5's to do it.

    If someone wanted to change the face of military program development, come
    • They've already learnt that lesson. New aircraft are now developed in close liason with the chip manufacturers so that it is understood exactly what will be available when the plane goes into service. Technology refresh is also an integral part of the design process.

      The bit that worries me about this, is that it means we will have planes flying overhead running chips that haven't had many years of testing before being cleared for flight .

  • by Bowling Moses ( 591924 ) on Monday October 27, 2003 @06:57PM (#7323714) Journal
    All comments about the Stryker aside, maybe the Army's trying to learn something from the Navy. I'd like to think that leaving the cruiser USS Yorktown dead in the water for 2 1/2 hours due to a divide by zero error [wired.com] would motivate a switch from microsoft to something more robust. I'd also like to think asses of the dimbulbs in charge are still smarting from the cornholing courtmartial they received, but they probably got promoted instead.
  • If window crashes, you reboot, and then it's fixed. This happens fairly often, once a week or so.

    If XFree86 crashes, your entire computer freezes up and you have to ssh into the box to X11 it (alt. reboot). This happens like once every 5 years. But still, it is quite some mess to get youself out of, especially when you're fighting a war.
  • by The Gline ( 173269 ) on Monday October 27, 2003 @07:05PM (#7323783) Homepage
    If this wasn't Slashdot, it would probably be something like "Linux Now Bring Used To Kill More People Than Windows".

    [note to mods: THIS IS FUNNY]
  • Well, this is certainly one way to shave billions off of the defense budget.

    With the money they've saved on software, the Air Force can probably buy another B1. :-)
  • More info about the new and controversial infantry vehicle Stryker is available here [army.mil] and here [army.mil]. Here are two nice videos [strategypage.com] of the Stryker in action.
  • by the eric conspiracy ( 20178 ) on Monday October 27, 2003 @08:31PM (#7324451)
    This reminds me of an episode [alloftheabove.net] of Calvin and Hobbes where ole' Spiff almost doesn't make it.

  • i think... (Score:4, Insightful)

    by mr_burns ( 13129 ) on Monday October 27, 2003 @08:53PM (#7324621)
    ...the real advantage to using Linux as opposed to Windows in this instance is the ability to strip the OS down to the bare essentials required to accomplish the mission.

    Windows is the kind of OS where cramming in as many features as possible is more important than many other things. Hence, this system running Windows is likely hogging up cycles and draining battery performing tasks that aren't needed or even wanted in a battlefield.

    But with Linux you can strip it down so that every cycle is a neccessary one. Plus the NSA has plenty of experience hardening the kernel per it's whimsy.

    The Military has experience fielding unix in ground combat systems. It's been proven time and again in combat. A Linux solution (or an embedded linux solution) allows the Army to customize even the very low levels of the software in addition to the legendary reliability it enjoys in other systems.

    Windows has neither of those things and frankly is not suited to an environment where taking time to patch the OS or troubleshoot could cost you your life.
  • by denks ( 717389 ) on Monday October 27, 2003 @10:19PM (#7325269) Journal
    This all brings about the interesting question of which distro they will use:

    Gentoo: they would have the best weapons platform imaginable, but it would be functional only 1 week every month, the rest of the time would be spent compiling

    Debian: they would have the most stable / reliable system, however instead of being compatible with Stryker, it would only be compatible with a WW2 Sherman, as this is the only piece of machinery certified as stable

    Red Hat: they would have a fine piece of equipment, until they tried upgrading, then realised they also needed to upgrade their helmets. Upon upgrading their helmets they would realise that the new helmets would not work with their rifles. Upon upgrading rifles they realise that the new rifles are a version too high for their computers.

    LFS: Each soldier must get a university degree in computer science before being allowed near the equipment.

    GNU / Hurd: Soldier: "FIRE" Computer: "I cannot until you say GNU/Fire" Soldier: "OK, GNU/Fire at the enemy behind the building" Computer: "I cannot until you GNU/say GNU/Fire at GNU/the GNU/enemy behind GNU/the GNU/building...GNU"

  • by AHumbleOpinion ( 546848 ) on Monday October 27, 2003 @11:51PM (#7325866) Homepage
    Drill Instructor: "This is the seven inch combat knife, affectionately known as the KABAR. It has zero electronics and zero moving parts. It is the most reliable weapon you will every carry."

    Guys, it ain't the OS. Environmental, maintenance, electronic, and embedded application issues are far more likely to cause problems. The OS issue may be a red herring. The article seems to indicate that the original Land Warrior dual CPU hardware was flaky and is being replaced by a piece of hardware from a different project with a single CPU, simplified bus, and is already running Linux. It's not clear if WinNT is really to blame. Recall the initial speculation regarding the Navy's USS Yorktown incident. Many gleefully blamed WinNT, eventually folks talked to the Chief Engineer on board at the time and the actual software developer and found out that it was not WinNT, it was a debug version of application software that was at fault.

    Personally, I'd wager that Linux was simply a better fit (size, overhead) for the "other" embedded application. Or maybe the team was more experience with Unix than Windows. Switching the Land Warrior over to Linux to maintain commonality with other systems would justify the change as well.
  • by digital photo ( 635872 ) on Tuesday October 28, 2003 @12:44PM (#7329879) Homepage Journal

    don't get me wrong, I love tech, but what prevents someone from DDOS's our soldiers?

    This network performs intel in both directions. What prevents the soldiers from either having their signal blocked or worse, having their communication systems overwhelmed by data flooding and/or debilitating noise from their headsets?

    [joke]Or worse yet... be distracted by streaming music and live porn video feeds..[/joke]

To be awake is to be alive. -- Henry David Thoreau, in "Walden"

Working...