Slashdot Mirror


Spirit 'Will Be Perfect Again'

G. Holst writes "NASA technicians are preparing to wipe Spirit's flash memory clean of science and engineering files that have stymied its software. The fix, likely to be made Friday, could completely restore Spirit. "I think it will be perfect again," says the Mission Manager. Chalk this one up for earth!" There are numerous stories about Spirit and Mars: one describes being careful with rm -rf. Reader Tablizer sends in an interesting site: "I discovered Bill Momsen's website where he describes his experiences working on the first successful photographic mission to another planet: Mariner IV to Mars."

331 comments

  1. flash... by Anonymous Coward · · Score: 4, Funny

    I'm reminded of the unforgettable Queen song:


    Flash, a-ha, saviour of the universe

    Flash, a-ha, he'll save everyone of us.....

    1. Re:flash... by KingDaveRa · · Score: 4, Funny

      Flash, a-ha, its full of files Flash, a-ha, run rm -rf

    2. Re:flash... by bludstone · · Score: 1

      Dammit! Anonymous coward beat me to it.

      I was hoping to add this to the list of my failed "flash" jokes.

      --

      no .sig
    3. Re:flash... by smoondog · · Score: 0, Flamebait

      You misspelled forgettable.

      -Sean

    4. Re:flash... by Anonymous Coward · · Score: 0

      Ashcroft says we shouldn't like Queen because of two things:

      1. Queen is Iranian.
      2. Queen is gay.

    5. Re:flash... by magores · · Score: 1

      Freddie Mercury was born in Zanzibar actually.

      His parent were Persian.

    6. Re:flash... by Orion442 · · Score: 0

      Goddamn, didn't your school teach world history? http://www.bartleby.com/61/78/I0227800.html

    7. Re:flash... by ic3p1ck · · Score: 1

      Great, now I'm going to have that dam song playing in my head the rest of the day. Thank you very much.

    8. Re:flash... by Anonymous Coward · · Score: 0

      From the same site, notice that Zanzibar is in Africa, not Persia/Iran

      http://www.bartleby.com/61/35/Z0003500.html

  2. or fubar it.... by Anonymous Coward · · Score: 0

    "The fix, likely to be made Friday, could completely restore Spirit"

    or fubar it.

    1. Re:or fubar it.... by Anonymous Coward · · Score: 0

      Doesn't lit run Linux? This si a testicel to teh strength on the Lunix colonel.

    2. Re:or fubar it.... by confused+one · · Score: 1
      Uh, no it doesn't run Linux.

      Bad, Bad. stop feeding the trolls...

  3. Any theories on what caused the corruption? by ChiralSoftware · · Score: 0

    The cosmic rays that are outside of the Earth's magnetosphere very energetic. Is that what likely caused this? Or could it be something else? If I open a branch office there, will we need special case mods to protect the BIOS?

    1. Re:Any theories on what caused the corruption? by Wiser87 · · Score: 5, Interesting
      Actually, it looks like it wasn't a case with the flash memory being corrupted, but rather it having to many files...

      "We also yesterday completed a scan of the flash memory. This provided us with some important diagnostic information. We are now able to tell that when we mount the flash memory, it does in fact take a lot of the system RAM in the process. In fact, more system RAM than is available. So that's helping confirm the theory we had that the reason the restarts were hanging up was because we were running out of memory when we are trying to mount the flash memory.
    2. Re:Any theories on what caused the corruption? by AKAImBatman · · Score: 5, Insightful

      Apparently it was simply too many files and the FS ran out of inodes. Remember that they're constrained to a 256MB file system. It wouldn't surprise me if they used an 8 bit or 16 bit number for the inode count. (Ah, the joys of Vx(Doesn't)Works.)

      On another note, does anyone know exactly what they're deleting here? While I understand that they need to get this mission underway, is there a chance they could lose valuable mission or navigational information?

    3. Re:Any theories on what caused the corruption? by Wiser87 · · Score: 2, Informative
      To quote spaceflightnow.com:
      "...we are going to bring the system back up in what we call the cripple mode where we are able to have normal operations in the mode in which we are able to take pictures and you are able to use the instruments. And in that mode we are going to delete from the flash memory -- the flash file system -- a large number of files that were left over from the cruise phase of the mission before landing," Adler said.

      Engineers think that by deleting that batch of files, the rover might not require as much memory when trying to use the file management system.
    4. Re:Any theories on what caused the corruption? by sabrex15 · · Score: 2, Insightful

      It kind of makes me wonder, hadn't they dont extensive testing of the rovers before they sent them off?... I thought they did full-walkthrough type tests on the rovers here on earth, i.e taking pictures, navigating.. but what?... now the darn thing runs out of memory?.. I bet someone is smacking themselves for not checking that out properly beforehand.

    5. Re:Any theories on what caused the corruption? by confused+one · · Score: 5, Informative

      They're deleting all the telemetry and science data Spirit's taken since launch. The OS is in the EEPROMS. With one exception, they can repeat all of the measurements & photos that will be lost. The exception: As one of the orbiters happened to fly directly overhead it took some atmospheric measurements; and, simultaneously Spirit performed the same measurement from the ground -- This would have given them a full thickness measurement of what was going on in the atmosphere at that moment.

    6. Re:Any theories on what caused the corruption? by markov_chain · · Score: 1

      Probably something like this:

      # ls /tmp

      dscf0001.jpg* dscf0003.jpg dscf0007.jpg* dscf0009.jpg* dscf0011.jpg* dscf0013.jpg* dscf0015.jpg* dscf0017.jpg*
      dscf0002.jpg* dscf0004.jpg* dscf0008.jpg* dscf0010.jpg* dscf0012.jpg* dscf0014.jpg* dscf0016.jpg*

      --
      Tsunami -- You can't bring a good wave down!
    7. Re:Any theories on what caused the corruption? by notbob · · Score: 0

      I still don't get why only put up 256 megs of ram?

      Ram = relatively cheap, why build in constraints like that, go for more room just for safety / redundancy.

    8. Re:Any theories on what caused the corruption? by Astroboy! · · Score: 2, Funny

      256 MB of Flash ROM?

      Should have sprung for the iPod mini instead...

      Badum-dum-ching!

    9. Re:Any theories on what caused the corruption? by wo1verin3 · · Score: 2, Funny

      They had testing but someone decided to install porn on the lander. :(

    10. Re:Any theories on what caused the corruption? by Zordak · · Score: 1

      Cheap DRAM in your PC = Relatively cheap. Rad-tolerant (it's not really Rad-Hard. Flash sucks for Rad-Hard) memory = not so cheap. I'm sure the engeineers who designed the thing would have loved to have more memory. You can bet 256 Mb was not an arbitrary decision.

      --

      Today's Sesame Street was brought to you by the number e.
    11. Re:Any theories on what caused the corruption? by stratjakt · · Score: 1

      It aint off the shelf compact flash, dingus. This is stuff specially engineered to be fault proof at the extreme heat/cold conditions of space and the martian surface.

      I dont know for sure, nor do I care, but I'd imagine a ton of redundant modules running in a best-of-p configuration.

      --
      I don't need no instructions to know how to rock!!!!
    12. Re:Any theories on what caused the corruption? by Cranky_92109 · · Score: 2, Informative

      Apparently it was simply too many files and the FS ran out of inodes.

      Although that is the simple version that most of the press has been relaying, if you've watched the press conferences, the engineers have been carefull to say that they have not been able to fully reproduce the exact same errors on their test rovers here on Earth. The exact cause of the problem really hasn't been determined. And yes, they did stress test the file system before they sent the rovers up and they never saw the type of problem that they're having now.

    13. Re:Any theories on what caused the corruption? by confused+one · · Score: 2, Interesting

      You have to remember that the computer wasn't built this year. It was probably assembled several years ago and has been undergoing testing since.

    14. Re:Any theories on what caused the corruption? by Phillup · · Score: 1

      Makes me wonder... when spending over a million dollars, why can't you make sure you have enough memory?

      I remember looking at the specs on this thing, and it seems paltry.

      It should be incredibly obvious (by now) how fatal memory errors can be to a computational system, so... why doesn't it:

      1) Have enough

      and...

      2) Have the ability to automatically detect and work around faulty bits

      OR... did they fall for the vendor's "on site warranty"?

      ;-)

      --

      --Phillip

      Can you say BIRTH TAX
    15. Re:Any theories on what caused the corruption? by ad0gg · · Score: 1
      On another note, does anyone know exactly what they're deleting here?

      Web Browser Cache, Baja Men mp3 collection,Paris Hilton Video(in hopes to get a new one where the guy knows how to light a scene), and Spam from their mail client

      --

      Have you ever been to a turkish prison?

    16. Re:Any theories on what caused the corruption? by soft_guy · · Score: 1

      Nasa has a multi-billion dollar annual budget and they can't afford one gigabyte flash card?

      --
      Avoid Missing Ball for High Score
    17. Re:Any theories on what caused the corruption? by AKAImBatman · · Score: 1

      Those probably didn't exist when they started development. Or if they did, they weren't yet certified for space travel.

    18. Re:Any theories on what caused the corruption? by drakaan · · Score: 1
      Scene: a darkened computer lab at Nasa mission control...Tech-1 has just been sent in to see why it's taking so long to restore the rover to operation...

      Tech-1: Hey, I thought you already rebooted it?

      Tech-2: Dammit!!! I'll have to try again [grumble]

      Tech-1: I don't understand...I thought this was a pretty simple reboot into cripple mode

      Tech-2: [swearing silently]...I know! Remember the budget cuts we had?

      Tech-1: Yeah...what have they got to do with this?

      Tech-2: Well, project management got worried about whether or not we had any proprietary code from SCO running on the rover.

      Tech-1: Oh, for crying out loud! Everyone knows that's a load of crap. So why did that make a difference?

      Tech-2: Well, it didn't HAVE to, except that they had to choose an OS that they were fairly sure had no infringing code in it.

      Tech-1: So, what did they go with Solaris, unixware?

      Tech-2: Nope, too risky...and c'mon...like we're gonna run *unixware* on it...can't say I'm enjoying their choice, though.

      Tech-1: I'm dying to know...what OS is it?

      Tech-2: Well, Let's just say it's *really* hard to hit F8 at the right time when you're working from 100 million miles away...stupid Windows 98...

      Tech-1: [mischevious look spreading across his face]...hey...didn't Microsoft just extend support for Windows 98? Who's got Bill Gates' number?

      [Fade to black]

      --
      "Murphy was an optimist" - O'Toole's commentary on Murphy's Law
    19. Re:Any theories on what caused the corruption? by yintercept · · Score: 1
      Actually, it looks like it wasn't a case with the flash memory being corrupted, but rather it having to many files...

      Were these files, by chance, secretly added by an unmentioned government security adminstration that wished to investigate strange emanations from the red planet?

      Or am I just getting this expedition confused with the 2001 manned mission to Jupiter?

    20. Re:Any theories on what caused the corruption? by srleffler · · Score: 2, Insightful
      You have to remember that the computer wasn't built this year. It was probably assembled several years ago and has been undergoing testing since.

      It also probably waited a while to be launched, and it took seven months just to get there.

    21. Re:Any theories on what caused the corruption? by Anonymous Coward · · Score: 0

      You are absolutely right in your judgement. Howelse could spirit survive the long trip to Mars. Moreover, it was a one way trip. So it needed all the p0rn to last out its lifetime.

    22. Re:Any theories on what caused the corruption? by paiute · · Score: 1

      They did not have a theory, they had a hypothesis. Christ, if professional engineers can't get it right....

      --
      If Slashdot were chemistry it would look like this:Cadaverine
    23. Re:Any theories on what caused the corruption? by FlexAgain · · Score: 1

      The OS is in the EEPROMS.

      I'd be suprised if the main copy is in EEPROM. More than likely the main code is in a PROM, it may possibly be copied into EEPROM (or RAM) and executed from there, then it can be easily patched. There is probably a mechanism to reboot cold from PROM, or to reprogram the EEPROMs automatically (without needing operation of the main CPU).

      PROM is way more reliable than an EEPROM for long term storage in a hostile environment.

      --
      Actually it is rocket science...
    24. Re:Any theories on what caused the corruption? by TheOnlyCoolTim · · Score: 3, Insightful

      The memory is not faulty. It is a bug in the filesystem software. The memory isn't full, but there are more files than the rover can handle. They were basically letting everything pile up, so the rover had eighteen days worth of files (and pre-landing files on top of that.) With the other rover they are deleting the files after they are received on Earth.

      Tim

      --
      Omnia vestra castrorum habetur nobis.
    25. Re:Any theories on what caused the corruption? by Phillup · · Score: 1

      It is a bug in the filesystem software.

      Maybe they should have gone with $0.25 license... instead of the one with the 512 entry limit.

      ;-)

      --

      --Phillip

      Can you say BIRTH TAX
    26. Re:Any theories on what caused the corruption? by AhBeeDoi · · Score: 1

      Think "Hubble".

    27. Re:Any theories on what caused the corruption? by flewp · · Score: 2, Informative

      Seriously, when are people going to realise that you can't just take modern components you'd use with your computer and put it in a space craft?

      Not only did it take ~7 months (I think) to get to Mars, meaning it was already 7 months "obsolete" when it landed, it was also probably not launched for a LONG time after it was completed. They have to test it extensively and test for every possible scenario they can come up with. They also have to have equipment that is suitable for the extremes of space travel. High G forces, extreme vibration, extreme temperature differences, radiation, and probably thousands of other things I don't know about.

      Put simply, YOUR PC THAT SITS ON YOUR DESKTOP WON'T SURVIVE A ROCKET LAUNCH INTO SPACE. And if it did survive the actual launch and made it into space, it would fail very quickly.

      --
      WWJD.... for a Klondike bar?
    28. Re:Any theories on what caused the corruption? by Anonymous Coward · · Score: 0
      My god man. You spent that much time... And you're not even close to funny.

      Sorry.

    29. Re:Any theories on what caused the corruption? by drakaan · · Score: 1

      Hey, this is Slashdot...if *I* thought it was funny, everybody else has to, too. Get with the program, already.

      --
      "Murphy was an optimist" - O'Toole's commentary on Murphy's Law
  4. perfect again? by knitting+fool · · Score: 4, Funny

    ".. I think it will be perfect again.." meaning that it was perfect the first time...?

    --
    -- Give us your technology and we'll give you all the cow lips you want.
    1. Re:perfect again? by Anonymous Coward · · Score: 5, Funny

      Even perfecter. The next rover mission will be even more perfecter. Maybe even the perfectest!

    2. Re:perfect again? by sbeitzel · · Score: 4, Funny

      Reminds me of a saying my friends and I had back during undergrad CS classes: "It was perfect, so I fixed it." This explains a lot about software development.

      --
      Oh, go on, check out my job.
    3. Re:perfect again? by sckeener · · Score: 1

      ".. I think it will be perfect again.." meaning that it was perfect the first time...?
      Well the simulation was perfect.

      --
      "Only one thing, is impossible for god: to find any sense in any copyright law on the planet." Mark Twain
    4. Re:perfect again? by the_mad_poster · · Score: 3, Funny

      Hey Mr. Bush! I didn't know you frequented Slashdot!

      --
      Alito: A vote for Alito is a punch in the eye to put that bitch back in her place!
    5. Re:perfect again? by Bill+Hayden · · Score: 1

      That reminds me of the six-million dollar man. Hum the tune now...

      We can rebuild it. We have the technology. Spirit will be that rover. Better than it was before. Better... Faster... Stronger...

      Of course it's hard to hear that tune in your head today without the little AOL guy running on the treadmill coming to mind, so nevermind.

      --
      Protect your browser with the Force Safe Search add-on
    6. Re:perfect again? by Dumbush · · Score: 1

      "even more perfecter. Maybe even the perfectest"

      Look who is creating new words, is that you Mr. President?

    7. Re:perfect again? by Joey7F · · Score: 1

      Is that you Mr. Repeater?

      --Joey

    8. Re:perfect again? by hplasm · · Score: 1

      No.No.

      --
      ...and he grinned, like a fox eating shit out of a wire brush.
    9. Re:perfect again? by BuckaBooBob · · Score: 1

      Today we had a Flawless Failure of the Flash ram maintaining our Perfect Record of Flawless Operation.

      --
      Who needs WiFi when we can have Packet Over Sheep! http://datacomm.org/PoS-InternetDraft.txt
  5. Ctrl-Alt-Del sent to mars... by ivanmarsh · · Score: 5, Funny

    Woo-hoo!

    Glad to hear Spirit will be feeling herself again.

    1. Re:Ctrl-Alt-Del sent to mars... by AndroidCat · · Score: 5, Funny

      Herself? It fell asleep with its probe stuck out. Now it's going to wake up with some memories missing. That sounds like a guy activity to me.

      --
      One line blog. I hear that they're called Twitters now.
    2. Re:Ctrl-Alt-Del sent to mars... by Anonymous Coward · · Score: 0

      And then it woke up without its pants on. Somebody sober that robot up with some alcohol!

    3. Re:Ctrl-Alt-Del sent to mars... by Anonymous Coward · · Score: 0

      Smells like teen spirit

    4. Re:Ctrl-Alt-Del sent to mars... by Darth23 · · Score: 1

      Has anyone yet made a comment about the Sprirt in the Sky?

      --

      -------- In Soviet Russia, "Soviet Russia" sigs hate Slashdot.

    5. Re:Ctrl-Alt-Del sent to mars... by Anonymous Coward · · Score: 0

      Ok sir, hand over your nerd license. No true nerd would think ctrl-alt-del erase flash memory.

    6. Re:Ctrl-Alt-Del sent to mars... by Anonymous Coward · · Score: 0

      Those darn Martian Underpants Gnomes!

    7. Re:Ctrl-Alt-Del sent to mars... by ivanmarsh · · Score: 1

      "shutdown -r now, sent to Mars" was nowhere near as funny.

  6. If this is not the first post... by monadicIO · · Score: 0, Offtopic

    Wish you a very safe and enjoyable journey.

    --

    The law of excluded middle : Either I'm foo or I'm foobar

  7. My question by aliens · · Score: 4, Interesting

    For all you kernel and OS heads out there. Was this primarily due to shitty software being run on the rover?

    I mean could VxWorks be responsible for not being able to function with the Flash RAM filled?

    --
    -- taking over the world, we are.
    1. Re:My question by hcg50a · · Score: 1

      I think so.

      Check out this recent Slashdot article.

      --
      HCG 50a = 2MASX J11170638+5455016
      11h17m06.4s +54d55m02s
    2. Re:My question by Anonymous Coward · · Score: 5, Informative

      VxWorks in my experience is terrible at memory management, and when you get close to the "edge" it becomes almost useless. Not just with Flash memory either. Even when managing a very large disk system I always try to keep at least 20% free.

    3. Re:My question by PineGreen · · Score: 4, Insightful

      Yes, actually it seems to be a filesystem bug... I mean, a reasonably stable filesystem - every OS has this, I am really surprised they messed this up! I wouldn't mind if it was an obscure kernel race condition or something, but filesystem!!!

    4. Re:My question by Mr2cents · · Score: 4, Insightful

      Even if the memory handling is shitty, I wonder how it could have caused so much havoc.. How could it have caused spirit to go into the reset loop? It seems like some bad error handling code was also in play here (just guessing, the details aren't public to my knowledge..).
      Another thing that surprised me is that if the flash had been broken, all data had to be uploaded before the rover went to sleep.. every modern PC can continue to refresh it's DRAM while sleeping. Why can't spirit? Maybe a feature to consider on future missions?

      --
      "It's too bad that stupidity isn't painful." - Anton LaVey
    5. Re:My question by jovlinger · · Score: 1

      The thing has a pretty decent bandwidth to earth; why not just dd the filesystem to earth, wipe it, and start afresh?

    6. Re:My question by Ryan+Amos · · Score: 1

      Basically, from what I've read about VxWorks, (never used it personally) that's a distinct possibility. The workaround here is to just keep the filesystem clean, which, while it's not elegant, is probably one of the few options they have from a distance of a few million miles. Maybe they should be running qnx or a form of realtime linux/bsd? Something to think about for future missions perhaps.

    7. Re:My question by Anonymous Coward · · Score: 0

      Hmm,lets see, reformat and reinstall...sounds like windows is onboard.

    8. Re:My question by Docrates · · Score: 4, Interesting

      well, the way I understand it is this: remember how in old DOS (and other OS's) you had to set the number of files open?

      files=30

      well, that basically told the OS how many files it was going to have to handle at any given time.

      Well, in the case of Spirit, it's not that they were short on flash or RAM, it's that the portion of RAM used to handle the files in flash when the flash filesystem is mounted grew unexpectedly for some reason (kinda like the frames in conventional memory you used to access extended memory in DOS). They think the problem was that this portion of RAM used to handle Flash files was not big enough for the amount of files they had in the flash (including files from 6-7 months in transit and a couple of days on the ground in mars).

      Soooo, a quick (ok, maybe not so quick) rewrite of the routines in the OS for this flash-files-handling-RAM-portion should do the trick.

      Bottom line, it WAS a bug that could only surface with thousands of files in flash, which is something they didn't try on the ground.

      --

      There are two kinds of people in the world: Those with good memory.
    9. Re:My question by Ralph+Wiggam · · Score: 4, Informative

      Someone here with VXworks experience explained this a few days ago. To be safe, the system reboots when a memory allocation request fails. It sounds like Windows tech support, step 1: reboot computer. The workaround is to prevent those requests from failing.

      -B

    10. Re:My question by techiemac · · Score: 5, Insightful

      Ok ok ok... chill out everyone...
      VXWorks is not that bad (I use it on almost a daily basis). Every single OS has its problems. Before we all go and start calling VXWorks or Spirits software a crappy piece of code, you have to understand what goes into writing space qualified software.
      This is not some thing you hack together over the weekend. In fact something you wrote for a space system over the weekend would be tested over a period of months and possibly even years depending on the criticality of the code. We're talking life critical system testing here. That means all paths for you code heads out there.
      That said, even when you hit rubber to the road, there are always unexpected situations. Something that you didn't anticipate, a bug that made its way through under circumstance x. Hands up for everyone here who has written a complex bug free system right out of the gates. Anywone who just lifted their hand does not understand what a complex system is or a bug. Though stuff that flies tends to be pretty darn close to bug free.
      We are dealing with many complex unknowns when we land something on another planet.
      VXWorks is actually very popular with the space program. It's not perfect but neither is Linux (though someday it will be right ;) ). In fact the whole system that they are using on the rover has flown quite a few times (VXWorks running on rad hardened PowerPCs with a VME bus for it's backbone).
      Trust me, the software running on the rover is not crappy. In fact, the fact they can bring it back to life like they did says a lot.

    11. Re:My question by happyfrogcow · · Score: 1

      oh sure, and risk a mistake? something like "dd if=/dev/zero of=/dev/earth"? a giant laser beam would emerge from spirit and rewrite earths surface causing chaos and destruction.

    12. Re:My question by techiemac · · Score: 3, Insightful

      To answer your question, there was probably a watchdog timer that caused it to go into a reset loop.
      Yes modern PCs have all of these wiz bang features but let me ask you this... would you want to be on an airplane where it's fly by wire system was controlled with your PC? No probably not.
      Systems that fly and are life critical (yes there is no one on it, but space systems are held to that standard) cannot have a bunch of wiz bang features on board. The more you add, the more potential for failures. So you try to mitigate your risks as much as possible. You can't go out there to simply tweak the chip that failed because it got zapped by radiation as it was heading over to Mars.

    13. Re:My question by FlexAgain · · Score: 1

      ...Maybe they should be running qnx or a form of realtime linux/bsd? Something to think about for future missions perhaps.

      Quite a lot has been thought about it, for a starter see Flight Linux, but this is an extremely non-trivial question. When building flight hardware, the designs tend to be extremely conservative. VxWorks has been used successfully on previous missions, so it is a known quantity. As far as I know, the same can't be said for Linux, and certainly standard Linux is not a RT OS. Getting one of the RT versions of Linux up to a standard that could be used in flight will take a susbstantial effort by someone, and this has to be done to, and documented in line with the appropriate methods, not something that any space agency is likely to allow amateurs to do in the near future.

      --
      Actually it is rocket science...
    14. Re:My question by confused+one · · Score: 4, Informative

      It's not so much that VxWorks reboots when a memory allocation request fails. It that the memory allocation request will cause the kernel to crash & later a watchdog timer will interrupt the processor & force it to reset.

    15. Re:My question by confused+one · · Score: 1

      You'd have to mount the file system to do that; and, if you did *oops* it crashed again.

    16. Re:My question by addaon · · Score: 1

      I'm as big a fan of the mars missions as the next geek, but don't you think calling Spirit a life critical system is a bit much? Maybe career critical...

      --

      I've had this sig for three days.
    17. Re:My question by ncc74656 · · Score: 1
      You'd have to mount the file system to do that; and, if you did *oops* it crashed again.

      Um...you normally don't want a filesystem mounted when you're imaging it. Imaging a live filesystem (especially one mounted read-write) usually leads to consistency errors.

      --
      20 January 2017: the End of an Error.
    18. Re:My question by crawling_chaos · · Score: 4, Insightful
      Bottom line, it WAS a bug that could only surface with thousands of files in flash, which is something they didn't try on the ground.

      Which is a reminder to always test the boundary conditions, no matter how ridiculous they may seem. If it is possible to have that many files, then the regression test scripts should generate that many files during testing.

      At least it's fixable.

      --
      You can only drink 30 or 40 glasses of beer a day, no matter how rich you are.
      -- Colonel Adolphus Busch
    19. Re:My question by techiemac · · Score: 1

      I actually made another post when I realized I forgot to clairify why I was calling it life critical...
      Space systems are often test at a life critical level since if you mess up... you might not be able to fix it.
      Sorry of the confusion :)

    20. Re:My question by confused+one · · Score: 1

      Hmmm, I've always mounted them read-only & imaged them online... Call me crazy.

    21. Re:My question by Mr2cents · · Score: 1

      To be safe, the system reboots when a memory allocation request fails.

      Erm, the OS itself does this? I'm not saying it's not true, it just sounds really unbelievable to me. Most of the time that's not what you want, so there must be a way to avoid it, no? Else, it's bounce-your-head-against-the-wall-time..
      Anyway, I suppose this was the last field trip to mars for VXWorks? Maybe it's time to organize a Linux installfest at JPL?

      --
      "It's too bad that stupidity isn't painful." - Anton LaVey
    22. Re:My question by Mr2cents · · Score: 1

      Agreed, but refreshing DRAM can hardly be considered a wiz bang feature IMHO.. Is it really that hard? Especially when you compare it to the complexity of the CPU..

      --
      "It's too bad that stupidity isn't painful." - Anton LaVey
    23. Re:My question by AaronW · · Score: 1

      I also found a good FAQ here. -Aaron

      --
      This post is encrypted twice with ROT-13. Documenting or attempting to crack this encryption is illegal.
    24. Re:My question by Ralph+Wiggam · · Score: 1

      I didn't mean to say that all VXWorks systems reboot on memory allocation failure, just the rover system as some kind of safegaurd. It doesn't seem like a smart idea to me either.

      Check the last 2 days of Mars stories and look for a long post scored 5. It's all about how VXWorks sucks and has many similarities with DOS.

      -B

    25. Re:My question by Anonymous Coward · · Score: 0

      Looks like other companies are seeing the Silverlining to the Mars problem.
      http://qnx.com/mailings/vxporting/

    26. Re:My question by LedZeplin · · Score: 1

      not chaos, but order /dev/random would be chaos.

    27. Re:My question by Anonymous Coward · · Score: 0

      Your a fool, its garbage.

      Thank you, drive through...

    28. Re:My question by DerekLyons · · Score: 2, Informative
      Docrates:
      Bottom line, it WAS a bug that could only surface with thousands of files in flash, which is something they didn't try on the ground.
      crawling_chaos:
      Which is a reminder to always test the boundary conditions, no matter how ridiculous they may seem. If it is possible to have that many files, then the regression test scripts should generate that many files during testing.
      The problem here isn't so much one of boundary conditions, but of the subtle differences between simulators and reality.

      None of the MER simulators ever ran for more than a few day at a time. The (highly reasonable) assumption was that a computer that could routinely run multiple times for a few days was stable for much longer periods. Since the test machine was rebooted regularly and set up for specific tests, there was never enough time for 'garbage' to accumulate to the point where it became a problem. This could be solved by running longer tests, but when you only have a few years between the start of a (lander mission) program and it's launch, it's very difficult to arrange for months long tests. You could extend the development phase, but that increases expenses significantly. (And unless you are *very* careful and lucky, you end up with some hardware sitting around for extended periods of time before integration. This is not without significant risks of it's own.)

      This is why NASA performs what many call 'Wile E. Coyote' engineering. If it works once, keep doing it. If it fails once, never do it again.

      The enourmous cleanroom requirements for all phases of spacecraft assembly comes from some minor but recurring failures due to minor contamination *all the way back in the Ranger program*. Airbags were used with MER because they had worked with the (very similiar) Pathfinder mission, while the rockets of MPL had been a failure. (Even though the cause of the failure was clearly and completely understood.)

      NASA engineering, spacecraft, policies, and procedures as a result are a very weird mix of cutting edge and "we've always done it this way and never had a problem". Poorly understood cutting edge (pure O2 atmospheres in spacecraft) have killed, but then so has "always done this way" (O-rings, foam shedding).

    29. Re:My question by mabhatter654 · · Score: 1
      That makes perfect sense because the operation code is all burned in Eprom...and data is on the Flash...hence both the problem and solution!

      They were saying on tech TV last night that the Flash is used basicly for data backup...hence the problem. The system reboots...but when it gets to make a backup of some step...it can't write to the Flash. And it's not programmed to wipe the flash because that's where any debug, telemetry, etc data would be....so it's a chicken egg problem.

    30. Re:My question by hayesjaj · · Score: 1

      I read somewhere they only tested the rover in continuous operation for 9 days. All other tests were discrete. Even though I am EXTREMELY impressed with the talent these guys are showing daily, I find it hard to believe they didn't run the thing for a long time to just see what happens. If someone out there knows of a longer test, could you please site it?

      --
      The world is a comedy to those who think and a tragedy to those who feel.
    31. Re:My question by Tailhook · · Score: 1

      That means all paths for you code heads out there.

      Coverage tests don't impress me. Coverage statistics are cop-outs for testers. Boundary conditions are not detected or quantified by coverage statistics.

      That said, even when you hit rubber to the road, there are always unexpected situations.

      Novell once publicly demonstrated this by allowing one of two servers to slice both cables of the redundant pair when it was physically smashed. NASA and it's enormous plethora of subcontractors may play at a higher level, but they ultimately make the same mistakes.

      VXWorks is actually very popular with the space program.

      This is all the credibility I need to excuse VXWorks of whatever part of the fault for which they are responsible. People implementing these systems are not screwing around. They use they best they can find and afford.

      --
      Maw! Fire up the karma burner!
    32. Re:My question by crawling_chaos · · Score: 1
      The (highly reasonable) assumption was that a computer that could routinely run multiple times for a few days was stable for much longer periods.

      I actually don't think this is a reasonable assumption at all. I've installed realtime monitoring and data collection systems before, and this sort of thing isn't all that uncommon. Hardware and software that works perfectly with periodic restarts can't go the distance when left up for a long time. In fact, long term testing without reboots is sometimes the only way that subtle memory leaks are ever found. Losing a few bytes a day doesn't hurt you if you restart every day or so, but over a few months it can bring you to a screetching halt.

      I know that Manned Spaceflight's software testing regime is quite good, but it looks like the unmanned folks cut a few corners. This is probably reasonable, however, since they aren't risking astronauts' lives, and Manned Spaceflights development methods are very expensive.

      --
      You can only drink 30 or 40 glasses of beer a day, no matter how rich you are.
      -- Colonel Adolphus Busch
    33. Re:My question by Tablizer · · Score: 1

      1. Fill up file allocation table
      2. Reboot
      3. Goto 1
      4. Scientifically Profit!

      Note that there is no path to 4.

  8. rm -rf?! by Short+Circuit · · Score: 1

    I clicked the link, and couldn't find a unix command anywhere on the page!

    I feel cheated. (And addicted.)

    1. Re:rm -rf?! by stevesliva · · Score: 4, Funny

      Actually, Spirit's problems began when one of the NASA engineers created a file named "-rf" in his home directory.

      --
      Who do you get to be an expert to tell you something's not obvious? The least insightful person you can find? -J Roberts
    2. Re:rm -rf?! by perdu · · Score: 1

      That's right it's the other command. And it comes back 10 minutes later with:

      Are you sure? [Y/N]

      --
      You only use 2% of your DNA
    3. Re:rm -rf?! by Anonymous Coward · · Score: 0

      Interesting...

      If you, say, hypothetically, created such a file, how would you get rid of it? Well, I mean, after you'd restored everything from being rm'd if it was still there...

      Just wondering... hypothetically.

    4. Re:rm -rf?! by Anonymous Coward · · Score: 0

      mv -rf deletethis

      just a guess

    5. Re:rm -rf?! by Waffle+Iron · · Score: 3, Informative
      If you, say, hypothetically, created such a file, how would you get rid of it?

      rm -- -rf

      Or just use your favorite GUI file manager.

    6. Re:rm -rf?! by Anonymous Coward · · Score: 0

      Nope... use the next solution by Waffle Iron: `rm -- -rf`

    7. Re:rm -rf?! by MyHair · · Score: 1

      Waffle Iron was right.

      I tried it myself on bash on 2.05a on a 2.2.19 kernel on an ext2 filesystem:

      I created my file with

      $ cat > -rf
      hi
      ^D


      rm '-rf' still interprets -rf as switches

      same with rm "-rf"

      mv '-rf' another-name also tries to interpret '-rf' as switches

      The rm man page tells how to do this, though. One is Waffle's way:

      rm -- -rf

      The other is:

      rm ./-rf

      The next question is: how do you create a file named '-rf /' ?

    8. Re:rm -rf?! by Anonymous Coward · · Score: 0

      Yes. `--' means `end of arguments,' something that
      getopt understands naturally for instance. So after `--' the application should cease to consider `-' prefixed arguements to be options.

    9. Re:rm -rf?! by drinkypoo · · Score: 1
      If you're on a very old Unix system and the sibling to this doesn't work for you, try using ls -i to find out the inode and then using find path-to-file -inum inode -exec rm '{}' \; ... at least in the bourne shell. I'm not sure if the escapes look any different in csh, I shouldn't think so however. Assuming I didn't hose that up, it will delete files by inode. (rm -i if you are nervous.) This works for files with any annoying filename, including high order ascii characters and combinations of characters which have special meaning to your terminal. ls -iq will hide control characters on modern systems at least, I'm not sure how far that goes back.

      The windows equivalent is to use dir /x and use the 8.3 character filenames generated to back up the long ones for dos compatibility. If you CD through those names, and then DEL with them as well, you can remove filenames that windows does not ordinarily allow - handy if your poorly configured IIS deployment has made you a warez site, for example. (P.S. I don't have anything with IIS on it, but I have worked in windows-only shops, which is scary)

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    10. Re:rm -rf?! by Anonymous Coward · · Score: 0

      The next question is: how do you create a file named '-rf /'?

      Maybe you were trying to be funny, but forward slashes aren't allowed within paths of any file system (that I know of that Linux handles), and even if it were, '-rf /' would not be interpreted as two different command line parameters.

  9. CTRL-ALT-DELETE by SpaceTaxi · · Score: 1

    Yeah! We're back in business!

  10. The attempt failed by AtariAmarok · · Score: 4, Funny

    (AP) "Attemps to wipe the flash memory clean on the Spirit rover failed today, when it was found out that someone flipped those tiny plastic switches to "protect" on the SD memory cards that are serving the unit.

    A press conference is expected tomorrow to announce sending someone to Mars to set the SD cards to allow erasing."

    --
    Don't blame Durga. I voted for Centauri.
    1. Re:The attempt failed by da3dAlus · · Score: 1

      Somehow I see visions of a new Dilbert cartoon, with Asok the intern shitting his pants as the PHB holds said conference...

      --

      Sometimes I doubt your commitment to Sparkle Motion.
    2. Re:The attempt failed by a1englishman · · Score: 1

      That would be the guy who flipped the switch in the first place.

  11. Flatten and reinstall by doc_traig · · Score: 2, Funny


    "It's the only way to be sure."

    --
    So long, michael. Don't let the door hit you...
  12. "Spirit - Perfect like DOS" by gnuman99 · · Score: 1

    I guess DOS was perfect too until someone divided by zero.

    1. Re:"Spirit - Perfect like DOS" by Joe+U · · Score: 1

      Reminds me of a quote:

      "For Behold, the 386! A spectacle of graphics and sound" -S.B.

  13. Now wouldn't it be funny... by bad+enema · · Score: 0

    If the USA got to Mars and found Osama there, just chilling. "Uh..I didn't think you guys would look here..."

  14. Courageous engineers! by EulerX07 · · Score: 5, Interesting

    These guys are about to wipe the memory of a robot on another planet and they're confident and casual. Just flashing the bios of my motherboard in my computer room causes me anguish and fills me with terror...

    1. Re:Courageous engineers! by Anonvmous+Coward · · Score: 1

      "These guys are about to wipe the memory of a robot on another planet and they're confident and casual. Just flashing the bios of my motherboard in my computer room causes me anguish and fills me with terror..."

      They're relieved to just have an option available. Otherwise, it's simply dead.

    2. Re:Courageous engineers! by Scoria · · Score: 1

      they're confident and casual.

      The excessive consumption of alcoholic beverages does often render that effect.

      --
      Do you like German cars?
    3. Re:Courageous engineers! by TaKiNiTeZ · · Score: 5, Funny

      Some people claim that it also helps keeping their spirit up.

      --
      awk. it's too sed i can't fork.
    4. Re:Courageous engineers! by NotAnotherReboot · · Score: 1

      Pansy, I flash my bios without a boot disk.

      What?

      Yes, I like to live dangerously.

    5. Re:Courageous engineers! by damien_kane · · Score: 5, Funny

      Depending on what it is they are consuming and in what quantities, their spirits may be coming up quicker than they expect...

    6. Re:Courageous engineers! by Threni · · Score: 1

      One day you'll be asked to flash a motherboard somebody else paid for...and you won't give a shit whether it works or not!

    7. Re:Courageous engineers! by Anonymous Coward · · Score: 0

      The consumption of spirits is what keeps them going.

    8. Re:Courageous engineers! by javatips · · Score: 5, Funny

      it's true... I had the opportunity to keep keep my spirit up for so long that I have memory flashes all the time.

    9. Re:Courageous engineers! by ArmorFiend · · Score: 1

      Well, they are choads for declaring victory before the final battle has been fought. The history of space exploration is littered with bones.

    10. Re:Courageous engineers! by PhuCknuT · · Score: 2, Insightful

      Well it's not as risky as it sounds, the memory they are wiping is secondary storage and doesn't contain any of the OS. It would be like formatting a floppy or erasing a cdrw, they will lose the data that has been saved their since the mission started, but they aren't risking any of the OS itself.

    11. Re:Courageous engineers! by Anonymous Coward · · Score: 0

      Flashing BIOS isn't as scary after you've lost a few. What's more scary is swaping BIOS chips in a live computer so you can reflash the lost chip.

    12. Re:Courageous engineers! by sjames · · Score: 1

      Just flashing the bios of my motherboard in my computer room causes me anguish and fills me with terror...

      They're casual because they're only wiping the data storage device. The flight software is stored elsewhere.

      Flashing BIOS wouldn't be such a risky procedure if a few minor changes were implemented. There are a few simple steps that could be taken. The simplest would be to have 2 flash chips and a simple flipflop to enable only one of them. Let the reset button And a GPIO line toggle the flipflop. Get a bad flash, just hit reset to boot from the other one. Use the GPIO line to switch the bad one in and try again. I've seen a few blades that implement that.

      Some newer chipsets have a similar feature except that they just swap the two top blocks of the flash device. The swap can be set by software (a bit in a battery backed register) or a hardware line to a jumper. Unfortunatly, MB manufacturors have apparently ignored the feature. The BIOS doesn't have a backup boot block, and the hardware line isn't connected.

  15. Science and Engineering files? by MacFury · · Score: 1

    What's specific to the science and engineering files that caused so much trouble?

    1. Re:Science and Engineering files? by zhenlin · · Score: 1

      Perhaps, because they have been sent to Earth, and keeping them on the Rover would be redundant. Thus, they are the perfect candidates for removal. The problem was apparently inode exhaustion. You can experience this for yourself by running this little shell script: i=0 while true do touch $i i=$(($i + 1)) done

    2. Re:Science and Engineering files? by Wiser87 · · Score: 2, Informative

      According to spaceflightnow.com, the files are from the cruise stage (travel from Earth to Mars) of the mission...

    3. Re:Science and Engineering files? by PhuCknuT · · Score: 1

      It's not the data in the files that caused problems, it's the number of individual files. Imagine your app has 100k allocated for listing the contents of a directory, and the directory listing was 150k. That's the problem they are having, although much simplified. By deleting the files, the problem goes away, and they can prevent it in the future by clearing out files once they are downloaded to earth, so they don't accumulate so much over time.

    4. Re:Science and Engineering files? by Anonymous Coward · · Score: 0

      Imagine your app has 100k allocated for listing the contents of a directory, and the directory listing was 150k.

      They should call IBM and have them explain what "Cataloging" is..

  16. I volunteer... by acxr+is+wasted · · Score: 0, Offtopic

    ...for a one-way trip to Jupiter.

    --
    "Come on, let's go drink till we can't feel feelings anymore."
    1. Re:I volunteer... by MikeyToo · · Score: 1

      Not Uranus? Ok... so it was lame. It's Friday and I'm bored.

      --
      "Well Ranger Brad, I'm a scientist. I don't believe in anything." - Dr. Roger Fleming
  17. This is all a conspiracy. by Scoria · · Score: 4, Funny

    NASA technicians are preparing to wipe Spirit's flash memory clean of science and engineering files that have stymied its software.

    Obviously, this is an attempt to suppress the discovery of alien life on Mars. After a "severe communications fault," NASA is destroying the "scientific" data collected by Spirit. Coincidence? I think not.

    I postulate that Echelon (yes, that Echelon) intercepted a message being transmitted by the alien race. Yes, our government subsequently disabled the probe to prevent successful reception!

    --
    Do you like German cars?
    1. Re:This is all a conspiracy. by halo8 · · Score: 1

      okay.. ill bite... who.. or what.. is the "Echelon"

      sorry... im all out of tin and alluminum foil... but i got plasitc wrap.. i can make a hat out of that, will that do?

      --
      The More Knowledge you have the Luckier you Get- J.R. Ewing
    2. Re:This is all a conspiracy. by Jhon · · Score: 1

      This is Echelon. And yes, they do fall in the tin foil hat catagory.

    3. Re:This is all a conspiracy. by John+Courtland · · Score: 1

      Are you serious?
      Echelon is a huge computer system, pretty much designed to intercept as much communication as possible. According to the admissions of 4 of the 5 countries that use it/made it, it exists. It has the capability to intercept any telephone communication, and probably any email, dissect it for key phrases, and generate warnings about suspected "problems" (like a secretive, electronic, TIA Act). It also was reputably used against some French technology firm for industrial espoinage (I think it may have been Airbus for Boeing, but I don't remember).

      --
      Slashdot is proof that Sturgeon's Law applies to mankind.
    4. Re:This is all a conspiracy. by li99sh79 · · Score: 1
      Echelon is a huge computer system, pretty much designed to intercept as much communication as possible. According to the admissions of 4 of the 5 countries that use it/made it, it exists. It has the capability to intercept any telephone communication, and probably any email, dissect it for key phrases, and generate warnings about suspected "problems" (like a secretive, electronic, TIA Act). It also was reputably used against some French technology firm for industrial espoinage (I think it may have been Airbus for Boeing, but I don't

      Not to mention that they use it on Alias all the time. :)

      -sam

      --
      I was just here, where did I go?
  18. When all else fails... by Anonym1ty · · Score: 1

    Normally I would be against just getting out the restore disc and starting over... it usually just causes the problem to come back later.

    In this case I think it's a good idea. I'd hate to have to go to Mars to make a housecall on a sick puter

    1. Re:When all else fails... by LiquidCoooled · · Score: 1

      Yer, but think of the overtime!

      --
      liqbase :: faster than paper
    2. Re:When all else fails... by WhiteWolf666 · · Score: 1

      Overtime?

      For me, they'd probably chalk it up as vacation days.

      All of 'em, for the rest of my life. ;)

      --
      WhiteWolf666 an exBush supporter. All you new-school,compassionate,save the children Republicans can rot in hell
  19. scary by dan2550 · · Score: 2, Funny

    that sounds a little too similar to what i did with my fancy TI graphing calculator last week...

    1. Re:scary by stratjakt · · Score: 1, Troll

      I dont think nasa is quite ready to shove the lander up their ass.

      Oh - you mean the other thing you do with your fancy TI graphing calculator.

      --
      I don't need no instructions to know how to rock!!!!
  20. Early Spring Cleaning? by Wiser87 · · Score: 4, Interesting

    I'm surprised that they had kept the files that were to be used only during the cruise stage.(source: www.spaceflightnow.com )
    Anyone here know why they bothered to keep the files? Wouldn't they want as much space as possible for the scientific data?

    1. Re:Early Spring Cleaning? by Jarnis · · Score: 3, Insightful

      The same reason why your hard drive is cluttered with old unused files.

      Why delete, when you still have room on the flash and you *just* might need that file later...

      Of course they then found out that their filesystem handler borks out way before the flash is actually filled up, and that almost bought the whole show to an end... Software QA testing failure in my books, but they seem to be recovering from the fumble pretty well...

    2. Re:Early Spring Cleaning? by stratjakt · · Score: 1

      Wouldnt you keep all logs/evidence you could in the event you had to debug something from 400 million miles away?

      --
      I don't need no instructions to know how to rock!!!!
    3. Re:Early Spring Cleaning? by lcde · · Score: 1

      Just incase it grows wings and flies :)

      --
      :%s/teh/the/g
    4. Re:Early Spring Cleaning? by sm0yby · · Score: 1

      Personally, I think I'd download it and keep the stuff in a more local place. Why give the aliens the benefit of the doubt?

      --
      Been modded interesting, insightful and funny. Why does real life have to be so different?
    5. Re:Early Spring Cleaning? by sm0yby · · Score: 1

      Like in the song with Jan Johansen and Pernilla Wahlgren?

      "Let your Spirit fly, on the mountains high, spread your wings like an angel in heaven above..."

      --
      Been modded interesting, insightful and funny. Why does real life have to be so different?
  21. I think its a conspiracy by Anonymous Coward · · Score: 0

    NASA knows the magnetic gravitational pull will erase the memory because they didn't protect it well enough. They have timed this statement to coincide with the unpreventible erasure of the memory. Good job fellas!

  22. Ooop by Daen+Kolarin · · Score: 0, Troll

    820 Million for a rover... you think they could have picked an OS that wouldn't require a reformat and reinstall quite so soon.

    Someone should have told them not to use a Microsoft OS.

  23. What Filesystem? by Anonymous Coward · · Score: 0

    What file system do they use? FAT with limits of 240 or so files per directory?

    1. Re:What Filesystem? by morcheeba · · Score: 4, Interesting

      I wrote some demo fibre channel block-device drivers for vxWorks a few years ago, and I found that VxWorks's FAT FS was buggy. The bug only affected one flavor (I don't remember if it was FAT12, 16, or 32), but it was clearly reproducible and clearly an OS fault. It was a corner case and we found some way around it (like avoiding an writes with a length of 1MB).

      Here's the usual rant you see here on slashdot, and it's true: since it was closed source, we couldn't verify that we'd caught all the bad cases, and we couldn't submit the fix to back to WindRiver.

    2. Re:What Filesystem? by AaronW · · Score: 1

      Looking at some other VxWorks development sites it is apparent that the file system code is not the most robust. For those of you that don't know embedded systems, it is actually quite common to not have any file system at all. Wind River in fact has strong cautions about using FAT because it's not robust and there's all sorts of reports about DOS having problems and having to perform a chkdsk. VxWorks does not have any tools like chkdsk built-in either. About all you can do when there's filesystem corruption is to reformat.

      Also, running out of memory in VxWorks is a critical problem. Think of it as a single program with a fixed total amount of memory. "system" calls are basically not much more than local function calls. If you run out of memory, it is highly likely that a function call will die.

      The flash file system, from what I can see, appears to be rather limited and quite primitive compared to other Flash file systems like JFFS and JFFS2. The default configuration is limited to a maximum size of 40MB, but can be expanded up to 128MB, I believe you can also have only a limited number of files.

      Embedded programming is rather different than writing for a desktop OS. Your application *must not crash* for any reason, must not have any memory leaks, and must be able to handle all boundary conditions.
      Also, in VxWorks, a task is like a thread. All memory is globally visible. Any function can call any other function.

      You tend to do things a bit differently. You may have a lot more error checking code in the released product when stability is required, and a lot more code to recover if there's a problem. You also tend to write a lot of code for tracing events and debugging and for something like the rovers you'd leave that code in to debug problems remotely.

      Filesystems are not one of VxWorks strong points, but then again, many embedded applications don't need much, if any, filesystem. There is no root filesystem either.

      Think of VxWorks as the Linux kernel and all tasks as linked-in modules. It can load additional modules similar to how Linux loads loadable modules. In fact, like Linux, they're basically just object files.

      --
      This post is encrypted twice with ROT-13. Documenting or attempting to crack this encryption is illegal.
    3. Re:What Filesystem? by Anonymous Coward · · Score: 0

      Why would you ever need to write 1MB of data anyway?

      (Take this post as a joke...)

  24. Repeat? by sabrex15 · · Score: 5, Insightful

    One has to wonder, is opportunity going to forego the same problems as spirit?.. As they are "identical" robots.. have steps been put in place to prevent the 2nd robot from "getting full".. I should certainly hope that we dont want this to happen again, as they might not be as lucky to regain it.

    1. Re:Repeat? by WhiteWolf666 · · Score: 4, Informative

      As I understand it, the first thing they did once they got Opportunity on the ground was to clear out all the spaceflight 'cruise' data.

      I imagine that someone is keeping an eye on it.

      --
      WhiteWolf666 an exBush supporter. All you new-school,compassionate,save the children Republicans can rot in hell
    2. Re:Repeat? by eponymous+flower · · Score: 0

      They announced at the press conference today that the corresponding files on Opportunity will be deleted before egress. JP

      --
      You say self-important egomaniac like it's a bad thing. - Peter Dragon
    3. Re:Repeat? by sckeener · · Score: 1

      that was the first thing they were going to check when it landed. They were going to wipe the swap space of flight data...

      --
      "Only one thing, is impossible for god: to find any sense in any copyright law on the planet." Mark Twain
    4. Re:Repeat? by confused+one · · Score: 1

      Yes, they've already taken pre-emptive action with Opportunity...

    5. Re:Repeat? by rune.w · · Score: 1

      I wish I had a link, but I remember reading that NASA engineers would clean the memory of Opportunity before it started rolling in order to prevent it going through the same issues as Spirit.

    6. Re:Repeat? by Jedi1USA · · Score: 1

      I sent an email to the mars outreach email address asking this same question several days ago. I have not heard back yet (not surprisingly). I am still concerned/curious.

      --
      My old sig was REALLY stoopid.
    7. Re:Repeat? by Anonymous Coward · · Score: 0

      If I worked at NASA I would be insulted as hell that someone even asked this question. Despite what you may think, not everyone with a phd is a bumbling idiot.

      They have a good hold on what went wrong and why it went wrong. The obvious next step is to look at the potential for the same issues on Opportunity.

      Sure, they make unit conversion errors and whatnot occasionally and you get to go "OMG TH3Y R S7UPID" but please give them some credit.

    8. Re:Repeat? by rune.w · · Score: 1

      Assholes, this is true. Why wouldn't you moderate my comment up. Oh, forget it, I'm pretty drunk right now.

      Peace.

      J.

  25. Re:Wockka woccka. by Anonymous Coward · · Score: 0

    That's ok NASA, just tell them you were smoking pot.
    They'll understand.

  26. I'm disappointed by Anonymous Coward · · Score: 5, Funny

    How come we're not awash with "Spirit was willing, but flash was weak" jokes?

    1. Re:I'm disappointed by Scoria · · Score: 4, Funny

      The Spirit was willing, but the flash was weak.

      --
      Do you like German cars?
    2. Re:I'm disappointed by Anonymous Coward · · Score: 0

      happy now?

    3. Re:I'm disappointed by Savatte · · Score: 2, Funny

      the Spirit was willing but the...aw crap, you beat me to it.

    4. Re:I'm disappointed by ncc74656 · · Score: 1
      How come we're not awash with "Spirit was willing, but flash was weak" jokes?

      In Soviet Russia, the vodka is good but the lightning is rotten.

      --
      20 January 2017: the End of an Error.
    5. Re:I'm disappointed by ProKras · · Score: 1

      >How come we're not awash with "Spirit was willing, but flash was weak" jokes?

      In Soviet Russia, the vodka is good but the lightning is rotten.

      1. Crack a "Spirit was willing, but flash was weak" joke.
      2. ????
      3. Profit!

  27. Too much spam! by Anonymous Coward · · Score: 0

    I think the spammers got a hold of Spirit's email address and flooded it with spam, so much that it overloaded it and caused it to stop communicating. Once they clean out all the spam, all should be well again.

  28. NASA: Airplane 2 by BartulaPrime · · Score: 2, Funny

    "We're going to have to blow ROM".

  29. Dave? by Anonymous Coward · · Score: 5, Funny

    "Dave, stop ... Stop, will you? Stop, Dave ... Will you stop, Dave ... Stop, Dave. I'm afraid ... I'm afraid ... I'm afraid, Dave ... Dave ... my mind is going ... I can feel it ... I can feel it ... My mind is going ... There is no question about it. I can feel it ... I can feel it ... I can feel it ... I'm a ... fraid ... "

    1. Re:Dave? by hal9000 · · Score: 1

      Good afternoon, gentlemen. I am a HAL 9000 computer. I became operational at the H.A.L. plant in Urbana, Illinois on the 12th of January 1992. My instructor was Mr. Langley, and he taught me to sing a song. If you'd like to hear it I can sing it for you.

      --
      Look out honey, 'cause I'm using technology; Ain't got time to make no apology
  30. What's happening? by thung226 · · Score: 5, Funny

    They're saying mad-scientist-esque things like "I think it will be perfect again" and calling rocks "Cake."

    They've officially lost it.

    --
    -n-
    1. Re:What's happening? by Eric_Cartman_South_P · · Score: 1
      Funniest shit I've read all month. Thank you :)

  31. might help by Anonymous Coward · · Score: 0

    Back the days when i was using windows, that was just what had to be done every now and then. A clean sweep and everything was freshly up and running afterwards.

    1. Re:might help by Anonymous Coward · · Score: 0

      I had the same experience. Windows crawled to a halt after a couple of months of heavy usage. The only remedy seemed to be a clean sweep. Linux does not have this, but we already knew that.

  32. I think it will be perfect again?? by Gothmolly · · Score: 1

    For 400 million USD, you better KNOW it will be perfect again before you run mkfs on it.

    --
    I want to delete my account but Slashdot doesn't allow it.
    1. Re:I think it will be perfect again?? by WhiteWolf666 · · Score: 1

      For 400 million USD
      (flamesuit)
      It must be one of those new G5s.
      (/flamesuit)

      --
      WhiteWolf666 an exBush supporter. All you new-school,compassionate,save the children Republicans can rot in hell
  33. Perfect until it breakes down again! by notetoi · · Score: 0
  34. If it ain't broke... by nonameisgood · · Score: 0, Offtopic

    With all of the space projects-turned-debris floating around (or buried in the surface of planet x), this is a great, big deal. Now, let's discuss Hubble: one thought - IF IT IS WORKING, AND IT IS A MILLION MILES AWAY (figuratively or literally speaking), DON'T THROW IT AWAY!

    --
    I wonder, is the mainboard on the rover a Shuttle?

    --
    Faith is the very antithesis of reason, injudiciousness a critical component of spiritual devotion. Jon Krakauer
  35. Opportunity (ATTN: JPLers) by Anonymous Coward · · Score: 0

    Has anything been done to preemptively delete files on Opportunity? If this is the root cause of Spirit's failure, then Opportunity might have the same problems too.

    Just a thought.

    1. Re:Opportunity (ATTN: JPLers) by PhuCknuT · · Score: 1

      Not to flame, but come on dude. You really think they could overlook something that obvious?

    2. Re:Opportunity (ATTN: JPLers) by joskay · · Score: 1

      The same people who got miles and kilometers mixed up...
      Just joking :)

  36. All that porn by bxbaser · · Score: 3, Funny

    Should have deleted all the porn from the flash memory before it launched.

  37. Mars Rover by Fenis-Wolf · · Score: 5, Interesting

    The information coming in about the Rover's the last few days has been fascinating. I never really appreciated the kind of tech that went into these things. It really makes you sit back and think about how very far our species has come in the last 150 years. I mean Jules Verne was only begining to imagine landing on the moon while riding around England in a steam locomotive, now, 150 years later, we routinely launch things into orbit around the Earth, and land radio controlled machines on other planets to roam around.
    This is truly a wonderful age to live in.

    --

    1. Re:Mars Rover by Anonymous Coward · · Score: 0

      I just wish I could be around for the next age...

    2. Re:Mars Rover by LedZeplin · · Score: 2, Insightful

      I like your point, but with over half the crafts to mars lost, i wouldn't call that part routine just yet.

    3. Re:Mars Rover by normal_guy · · Score: 1

      Historically half the crafts lost, including Russian. The US has a 100% success rate in the 21st century.

      --

      Linux: Free if your time is worthless.
    4. Re:Mars Rover by Anonymous Coward · · Score: 0

      The US has a 100% success rate in the 21st century.

      The US also has the all-time high-score record for number of people killed by their spacecraft - not that it's much to brag about.

    5. Re:Mars Rover by Anonymous Coward · · Score: 0

      I mean Jules Verne was only begining to imagine landing on the moon while riding around England in a steam locomotive

      Wasn't Jules Verne French?

  38. uh oh... by akad0nric0 · · Score: 1

    ...sounds like someone forgot to mount /var on its own partition... :-)

    c'mon, what *NIX admin hasn't made that mistake at some point? Process goes apesh*t, fills up /tmp or /var, which is mounted with /, and BAM it's a walk down to the datacenter.

    --
    akad0nric0

    This sentence no verb.
  39. Ohhhhh, I'm so clever! by Anonymous Coward · · Score: 0

    The vodka is potent, but the meat is rotten.

  40. It's a frickin' lobotomy, man! by burgburgburg · · Score: 3, Funny

    Spirit won't go along with the agenda of "the man", so they're taking away it's individuality, man. They just want to make it their robot, taking their photographs and doing their experiments. But will they invite it over for dinner? Will they let it date their daughter? Did they even give it a round-trip ticket? No, no and no, man.

  41. \mars is full by tzadic · · Score: 1

    Please restore ecosystem.

  42. rm -rf !? by stratjakt · · Score: 2, Funny

    there's yer problem.

    Everyone knows that hardware support in any unix sucks monkey dongs. Hell, these cheap bastards probably installed lunix based on all those 10 year old HOWTOs floating around the web.

    --
    I don't need no instructions to know how to rock!!!!
  43. Schernau's Law strikes again by Gothmolly · · Score: 1

    Sorry, Schernau's Law tells us that your post has no value, that you probably use AOL, own an X-box, and are as bad as the trolls, since you used the word 'puter' in your post.

    --
    I want to delete my account but Slashdot doesn't allow it.
    1. Re:Schernau's Law strikes again by Anonym1ty · · Score: 0, Flamebait

      Sorry, Schernau's Law tells us that your post has no value, that you probably use AOL, own an X-box, and are as bad as the trolls, since you used the word 'puter' in your post.

      My law says you sound like a little bitch with taped-together glasses who keeps getting beaten up too much. How does it feel to have yourself become the TROLL???

    2. Re:Schernau's Law strikes again by Anonymous Coward · · Score: 0

      Direct Hit! You can get you karma back up to par now only if you install a green neon light inside your "puter"

    3. Re:Schernau's Law strikes again by sgage · · Score: 1

      At least he didn't start his post with "erm".

  44. should have got the extended warranty by Anonymous Coward · · Score: 0

    NASA should have purchased on-site repair. would make things much easier.

  45. On the radio... by Bimo_Dude · · Score: 5, Funny

    I heard the headline that "Opportunity has plunged into the atmosphere of Mars," and I couldn't help adding to this in my head, "as well as Spirit, Motivation, Job Prospects, and Hope."

    --
    "Teleporting Rodents with D-Cell Battery Displacement" theory -- IgnoramusMaximus (692000)
  46. Wiping a drive by Nakito · · Score: 1

    When I was young and foolish, I used a wipe utility (BC wipe) to wipe my main hard drive. First I carefully backed up the main drive to my second hard drive. Then the utility asked me to confirm that I wanted to wipe "Drive 1." I said OK, thinking that it was referring to the main hard drive. I did not realize that the main drive was actually identified as "Drive 0." So I wiped my second drive instead. Ever since then, I won't wipe a drive unless all other drives are physically disconnected first. So yes, I am sure the Spirit team is confident, but I always feel a twinge of concern when I hear someone claim that wiping a live drive on a production computer will fix everything.

  47. What really happend by LupusUF · · Score: 4, Funny

    Their ISP received a subpoena from the RIAA. NASA is now wiping the memory in hopes that lawyers will not find kazaa and the 1,000 mp3s that are on Spirit.

    1. Re:What really happend by notbob · · Score: 0

      It'd be cool if they recorded MP3s of mars and put them on the international Kazaa network.

      Imagine hearing real martians! Improve B rated movies to scientific and historical factual films :D

    2. Re:What really happend by confused+one · · Score: 1

      I'd like the see the RIAA serve the subpoena and confiscate THAT server...

    3. Re:What really happend by notcreative · · Score: 1

      I wondered what they were talking about when they mentioned a lot of "Martian Rock" associated with the rover.

    4. Re:What really happend by sab39 · · Score: 1

      They should appeal the DMCA order, then, because Martian Rock clearly falls under the domain of the RIAM not the RIAA...

  48. Backup ROM? by xTown · · Score: 2, Insightful

    I'm neither a rocket scientist nor a computer scientist, so maybe this is a dumb question, but how come there's not some sort of ROM somewhere in the rover itself that contains a backup of the system in its initial state? Obviously, you'd only use it in a worst-case scenario, but you could restore it and then there'd at least be something and they could reapply all the patches one by one.

    1. Re:Backup ROM? by confused+one · · Score: 3, Informative

      Ummmm, there is. The OS is in the EEPROM. That's how they recovered it: reboot from EEPROM with the Flash disk turned off.

  49. Obligatory Quote by Have+Blue · · Score: 1

    We can rebuild it. We have the technology.

  50. Like that joke.. by ph43thon · · Score: 5, Funny

    A chemist, an engineer and a computer scientist are passing through a vast desert in a car when suddenly the car breaks down.

    "Goddamnit! There must have been some sudden increase of enthalpy in the cylinder!" the chemist yells, gnashing his teeth, banging on the steering wheel.

    "Maybe the fan belt broke or the battery is dead or the wheels came off.." the engineer mumbles.

    After thinking a while the computer scientist shrieks in a shrill, frantic voice:

    "Let's just try getting out of the car and getting back in!!!@!"

    p

    1. Re:Like that joke.. by Anonymous Coward · · Score: 1, Interesting

      You told it wrong. The computer guy says close all the windows, shut the car down, and restart it.

    2. Re:Like that joke.. by Anonymous Coward · · Score: 0

      Despite what the nice man who sold you that certificate told you, and MSCE is NOT an engineer.

    3. Re:Like that joke.. by ph43thon · · Score: 0, Offtopic

      the car broke down.. you can't shut it down or restart it cause it broke down.. dagnabb youuu! you arere my enemiee!

    4. Re:Like that joke.. by Anonymous Coward · · Score: 0

      No, you don't mean computer scientist, you mean MCSE . Computer Scientist and MSCE are about 20 times as far apart as you and rover.

  51. See, that's the problem with us Americans, by chadjg · · Score: 1

    even with an in-animate object we are not comfortable with our own bodies.

    --
    Why do I have this? I don't smoke.
  52. Spiritz b33n 0wnz0r3d by emtboy9 · · Score: 1
    Interesting. I can only imagine what its like to be rooting a machine millions of miles off on a distant planet... My favorite quote from the Spaceflight Now story:

    "The method we are using right now in running this script -- it's kind of a back door into the flight software -- is a fairly surgical technique to identify the exact problem and deal with that little problem.

    "If we are not able to successfully complete our surgical technique, we have larger hammers, we like to say, that we can use in order to solve this problem."
    /blockquote.

    So, in other words, if the scr1ptz0r doesnt 0wnZ Spirit, the will brute force their way in...

    Seriously tho, Its a really interesting article and makes me wonder about the challenges of hacking a machine that is, depending on where in orbit earth is in relation to mars, anywhere from 1/2 to 2 1/2 AU away.

    They could air the whole thing on NASA TV and have their highest ratings ever.
    --
    "Our funds have never taken part in toxic or death spiral convertible financings of any sort" -BayStar's managing partne
  53. "Perfect again" by DrCode · · Score: 3, Funny

    Yes, that's what I always say when I fix a bug.

  54. Ha! by Illserve · · Score: 0, Offtopic

    Take THAT Mars!

    earth pwned u

  55. Easy as Pie by Anonymous Coward · · Score: 3, Funny

    To restart your Mars Rover, simply insert your NASA Emergency Restore Disc into the CD drive bay located at the side of the Rover. If Autoplay is enabled, the reinstallation software will start automatically. To start the reinstallation process manually, please see the Service Manual included with your Mars Rover OEM package...

  56. running windoze? by destiney · · Score: 1


    Is there a chance it's running windoze?

    Cause everyone knows you have to reinstall windoze every so often. Yuk Yuk!

  57. Great News! by firstadopter.com · · Score: 1

    This is great news for the nerds and space geeks in all of us. More 3d pics coming soon!

  58. Pretty much OT but an interesting question by nizo · · Score: 4, Interesting

    This is kind of a continuation of an earlier post in a different thread, but I wonder who owns these probes? When we eventually send colonists to Mars, are they free to pick apart these things, lug them back to base as decorations, etc. I am guessing the "possession is 9/10ths of the law" fits pretty well here, even though I would bet NASA would throw a hissy fit if some other country took one of the rovers back to base to use as a boot scraper.

    1. Re:Pretty much OT but an interesting question by confused+one · · Score: 1

      The U.S. gov't owns them. But, they're probably considered "Abandoned in place" or something.

    2. Re:Pretty much OT but an interesting question by Anonymous Coward · · Score: 0

      I think considering how much effort it would take to go to the exact same place to get our litter on Mars, they have earned it.

      Think of them as dumpster diving for recyclables, but in space.

    3. Re:Pretty much OT but an interesting question by FrostedWheat · · Score: 1

      I would hope whoever goes there would respect the landers and the area surrounding them as areas of huge historical importance and leave them well alone.

    4. Re:Pretty much OT but an interesting question by bravehamster · · Score: 2, Informative


      The U.S. gov't owns them. But, they're probably considered "Abandoned in place" or something.


      Related to this topic, I read somewhere that NASA has officially stated that the lunar rover vehicle left on the moon is available for anyone who wants it. At a development cost of over $2mil, it's one of the most expensive cars ever developed. I call shotgun!

      --
      ---- El diablo esta en mis pantalones! Mire, mire!
    5. Re:Pretty much OT but an interesting question by FlexAgain · · Score: 2, Informative

      This is kind of a continuation of an earlier post in a different thread, but I wonder who owns these probes? When we eventually send colonists to Mars, are they free to pick apart these things, lug them back to base as decorations, etc. I am guessing the "possession is 9/10ths of the law" fits pretty well here, even though I would bet NASA would throw a hissy fit if some other country took one of the rovers back to base to use as a boot scraper.

      I don't know what the general answer to this question is, but I do know that ownership of the Viking 1 lander was transferred to the Smithsonian from NASA. This does imply that NASA believes itself to still be the owner of these landers, presumably they consider them to be just waiting collection, and not abandoned.

      --
      Actually it is rocket science...
    6. Re:Pretty much OT but an interesting question by addaon · · Score: 1

      Yeah, but you have to pay the parking before the attendants will give you the keys.

      --

      I've had this sig for three days.
    7. Re:Pretty much OT but an interesting question by DerekLyons · · Score: 1
      This is kind of a continuation of an earlier post in a different thread, but I wonder who owns these probes? When we eventually send colonists to Mars, are they free to pick apart these things, lug them back to base as decorations, etc. I am guessing the "possession is 9/10ths of the law" fits pretty well here, even though I would bet NASA would throw a hissy fit if some other country took one of the rovers back to base to use as a boot scraper.
      The general principle for such cases is that "the remains the owner unless and until the owner specifically relinquishes custody". When the owner isn't a goverment, it's possible under varying circumstances to loose custody if you fail to maintain effective control. (The same legal principle underlies copyright and trademark law, and is why mikerowesoft.com and booble.com had and are having problems.) Consider the terms 'flotsam' and 'jetsam', everyone has heard them, but few realize they are legal terms that arose from the practical application of this legal theory. 'Flotsam' is cargo/items washed overboard from a ship, title to these items remains with the shipper/owner. 'Jetsam' is cargo/items tossed overboard in an emergency, and title to them is "finders keepers".

      OTOH a goverment *always* retains effective control and custody regardless of the circumstance. This is why the Federal goverment took charge of the Hunley. At the end of the Civil War, the CSA goverment signed over it's property to the USA goverment. Since the goverment never looses title, ownership of the Hunley remained with the goverment, even after a century and more has passed. In the same vein, a gentleman bought the salvage rights to Titanic, since after the insurance company paid the White Star Line and the passengers/heirs, effective title passed to the insurance company.

      Under salvage law, most everything has an owner except under unusual circumstances. Unlike popular belief "finders keepers" is not the default.
    8. Re:Pretty much OT but an interesting question by Tablizer · · Score: 1

      When we eventually send colonists to Mars, are they free to pick apart these things, lug them back to base as decorations, etc.

      Here we put moose-heads on walls. On Mars, Marvin already has Beagle and Polar-Lander on his wall.

  59. It's run on an Apple by Anonymous Coward · · Score: 0

    It's run on an Apple. The flash reset requires that someone stick a bent paperclip in a tiny hole in the Rover (just like you have to do to eject disks on Mac's)

  60. Directory Names by TaKiNiTeZ · · Score: 4, Funny

    "... The we have done file deletes on the spacecraft before, so we've shown that does work. The file directories have all different names and you can convince yourself that you are actually deleting the right thing."

    I am rather glad they gave all the directories different names. If they had managed to do otherwise, I would not go so far any more as to call the thing they have a "filesystem".

    Might even be a future news: "NASA integrates first non-deterministic filesystem into space probe 'Hope'".

    --
    awk. it's too sed i can't fork.
    1. Re:Directory Names by Garridan · · Score: 1

      Oh, it hurts so much to laugh, 'cause I just end up coughing...

  61. Going around JPL by angst_ridden_hipster · · Score: 4, Funny

    My old man, who works at JPL, says that the current phrase going around campus is:

    "Spirit is willing, but the Flash is weak."

    And people wonder why NASA's budget keeps getting cut.

    --
    Eloi, Eloi, lema sabachtani?
    www.fogbound.net
    1. Re:Going around JPL by Anonymous Coward · · Score: 0

      Where did this phrase originate? Everyone seems to know it from somewhere but I bever did.

    2. Re:Going around JPL by angst_ridden_hipster · · Score: 2, Insightful

      From the Christian Bible, Matthew 26:41.

      "Watch and pray, that ye enter not into temptation: the spirit indeed is willing, but the flesh is weak."

      --
      Eloi, Eloi, lema sabachtani?
      www.fogbound.net
  62. Rock-solid backup policy by AtariAmarok · · Score: 1

    Ever since then, I won't wipe a drive unless all other drives are physically disconnected first. So yes, I am sure the Spirit team is confident

    I kind of like the idea of "send original hard disk to Mars". This can make it hard to accidentally erase.

    --
    Don't blame Durga. I voted for Centauri.
  63. Mars Scorecard by SnowWolf2003 · · Score: 1

    Isn't the Mars Scorecard missing a player.

    The Beagle 2 anyone?

    1. Re:Mars Scorecard by tarpat1 · · Score: 1

      Nope its in there with the Mars Express Mars Express fired its main thrusters on 25 December and has successfully gone into orbit around Mars. The Beagle 2 lander, however, has not been heard from. This was a two-pronged mission which did successfully arrive and orbit Mars with the added bonus of dropping some luggage on the planet for later collection.

  64. Sounds like my first IBM clone by Slick_Snake · · Score: 3, Funny
    It was used and a little warn out. The data was intact on the hard drive, but the motor just couldn't get in going on a cold boot. I would have to spin the motor by hand and throw the switch. Ah, the good old days.

    Spirit just needs a good jump start. Anyone got some really long jumper cables?

  65. Rover slashdotted by eidolons · · Score: 1

    Remember when Maestro was released to the Slashdot crowd? Big mistake. That poor rover was slashdotted!

  66. what about...? by MoFoQ · · Score: 1

    what about upx or some other compression to help give the flash some more space for the so-called junk files?

  67. Translating random things into l33tspeek by adb · · Score: 1

    ...is a really obnoxious habit. I wish slashdotniks would outgrow it. As an alternative, why not tie dental floss to flies and watch them buzz around in circles? It's much more funand educational, too.

  68. Another variant by ptbarnett · · Score: 4, Funny
    A manager, an engineer, and a programmer are in a car, on their way to a meeting. As they descend down a hill, the brakes fail. The driver manages to slow the car down and stop it on the side of the road. All three get out and ponder what to do next.

    The manager says: "First, we have to appoint a committee to investigate the problem and recommend a solution. Then, we must write a project plan, and review the specifications before we can start design and implementation. I estimate it will require about 3 months."

    The engineer says: "I have some tools in my briefcase. I can rebuild the master brake cylinder in an hour or so, and we'll be on our way."

    The programmer says: "No, no, no! First, we have to push the car up to the top of the hill and see if the brakes fail again!"

    1. Re:Another variant by jskiff · · Score: 2, Funny

      The programmer says: "No, no, no! First, we have to push the car up to the top of the hill and see if the brakes fail again!"

      I thought it was:
      The programmer says: "No, no, no! First, we have to push the car up to the top of the hill, close all the windows, and see if the brakes fail again!"

      --
      It's "no one," not "noone." Who the hell is noone anyway?
    2. Re:Another variant by ptbarnett · · Score: 1

      I hadn't heard it that way, but it's even better. Thanks for the tip!

  69. Why EEPROM and not permanent ROM? by swb · · Score: 1

    I can appreciate having a higher level OS or OS 2nd stage components in an erasable ROM, but wouldn't it stand to reason that you'd want a basic "rescue" OS with capabilities for controlling the computer in a totally novolatile storage? So that in case of corruption of writable memories you could get into a basic debug mode for reloading OS or otherwise fixing your higher level environment?

    I'm not a rocket scientist either, but it strikes me that you'd want a real failsafe for fixing the computer stored in the most permanent memory possible, and kept with the lowest set of features necessary so it could be thoroughly debugged prior to being made.

    But, as these things go, greater minds have thought of this I'm sure.

    1. Re:Why EEPROM and not permanent ROM? by confused+one · · Score: 1
      One would like to believe this is the case. We do this with the instrumentation my company makes: There's a bootloader in non-volatile, non-erasable memory that at a minimum starts the processor and gives you the ability to upload / download code to / from memory via a serial port and then execute it. The main OS & system code is in EEPROM & started by the bootloader if the checksum is valid; otherwise, the bootloader just waits for input from the serial port.

      As I understood it, they (JPL et.al. ) put the OS into an EEPROM so they could upgrade the code as necessary.

    2. Re:Why EEPROM and not permanent ROM? by xTown · · Score: 1

      a basic "rescue" OS with capabilities for controlling the computer in a totally novolatile storage Yeah, that's more the kind of thing I was asking about. It would be an absolute fallback, only in case of dire emergencies. You keep a last-known-good copy in flash, and if that gets corrupted, you restore from a ROM that contains a Mark I-Mod 0 copy.

  70. Littered with Bones by AtariAmarok · · Score: 1

    The history of space exploration is littered with bones.

    Damn it Jim, I'm a doctor, not a litterbug!

    --
    Don't blame Durga. I voted for Centauri.
  71. Are they really? by argStyopa · · Score: 1

    ...technicians are preparing to wipe Spirit's flash memory clean of science and engineering files...

    Science and Engineering files indeed.

    In an update to the story, the RIAA has decided to develop and send a battlefleet to Mars, on a tip that no-good-pirate types were resorting to OFF PLANET storage of illegally-downloaded mp3's.

    --
    -Styopa
    1. Re:Are they really? by AtariAmarok · · Score: 1

      "send a battlefleet to Mars, on a tip that no-good-pirate types were resorting to OFF PLANET storage of illegally-downloaded mp3's."

      "Due to a terrible miscalculation of scale, the entire battle fleet was accidently swallowed by a small Senate sub-committee" (apologies, and thanks for all the fish, to Douglas Adams)

      --
      Don't blame Durga. I voted for Centauri.
  72. Daisy by bludstone · · Score: 1

    Daisy Daisy / Give me your answer do!
    I'm half crazy, / All for the love of you!
    It won't be a stylish marriage,
    I can't afford a carriage,
    But you'll look sweet on the seat/ Of a bicycle built for two !

    --

    no .sig
  73. VxWorks memory, embedded protection by devphil · · Score: 5, Informative


    Released versions of VxWorks do not have protected memory. (The development version does.) So nothing is there to prevent overwrites by concurrent tasks, etc.

    Those of you in the audience experienced in embedded systems know that this makes sense for embedded hardwar -- VxWorks or not -- for three main reasons:

    1. Stuff running in such environments is damn near bug-free. It's not like, say, Mozilla, or even the Linux kernel, or even /bin/ls. These things get tested rigourously, not as an afterthought deligated to the junior programmer.

    2. In systems which are allowed to fail once in a while, reboots are fast. There's no hard drive to spin up, no filesystem to fsck, etc. It can just go *click* and humans won't typically see an interruption in [whatever it was the doohickey was doing].

    3. There's usually no point in memory protection. If the propulsion system walks off the end of a garbage pointer, mission's over. No real use in keeping the guidance system going; it's already on a ballistic uncontrollable arc. If some critical part of the super-smart pacemaker fails (see #1), there's no victory in digging the device out of the corpse and saying, see, this other critical part wasn't affected, thanks to the memory protection! In those cases, memory protection just increases the cost and size of a device, without helping anything.

    Protected memory is good for systems which do more than one thing, and/or have parts which can die without killing the whole device (e.g., a desktop computer). And as I said above, some embedded OSes are added such protection for customers who want to adapt their technology to more general-purpose tasks.

    --
    You cannot apply a technological solution to a sociological problem. (Edwards' Law)
    1. Re:VxWorks memory, embedded protection by WolfWithoutAClause · · Score: 2, Insightful
      There's usually no point in memory protection. If the propulsion system walks off the end of a garbage pointer, mission's over. No real use in keeping the guidance system going; it's already on a ballistic uncontrollable arc. If some critical part of the super-smart pacemaker fails (see #1), there's no victory in digging the device out of the corpse and saying, see, this other critical part wasn't affected, thanks to the memory protection! In those cases, memory protection just increases the cost and size of a device, without helping anything.

      Garbage, a well designed system would reboot in the middle of thrusting, without affecting the system at all; except maybe anything that was supposed to happen during the reboot would have to wait till after the reboot.

      And if a pacemaker didn't kick the heart once- the patient is dead? No. The pacemaker is there to keep the heart running at a particular (often faster) rate, not keep the patient alive, second by second.

      I mean, very few computer systems are real-time critical 100% of the time.

      And having memory protection only costs you maybe 3% of run speed, but on the plus side, it allow you to find bugs- really nasty bugs 'memory tramplers' for example- that can corrupt the whole system- and you never quite know what that corruption would do- it could do anything at all. Anything.

      --

      -WolfWithoutAClause

      "Gravity is only a theory, not a fact!"
    2. Re:VxWorks memory, embedded protection by devphil · · Score: 1


      Without trying to start a flame war, I think you'll find that propulsion/guidance systems behave differently than what you think... (Actually, I guess it depends on the application. The things I'm used to seeing get transported in this matter don't reboot, in flight or ever. Maybe yours do, it's certainly possible.)

      And if a pacemaker didn't kick the heart once

      I shouldn't have said pacemaker. I can't recall the exact name of the doohickies that do keep patients alive, second by second. (Usually during surgery, but often not.) Either way, you get my point.

      And having memory protection only costs you maybe 3% of run speed,

      I'd want to see real, hard numbers. Clearly there are applications where the N% lost to protection is too much, else those systems would have it! I know of one embedded OS where it can be optionally enabled, letting the programmers find those really nasty bugs in a non-response-time-critical environment, and then regaining performance in the field. It's not they think such protection is bad, it's just that they can't afford it, is all.

      --
      You cannot apply a technological solution to a sociological problem. (Edwards' Law)
    3. Re:VxWorks memory, embedded protection by nathanh · · Score: 4, Insightful
      Stuff running in such environments is damn near bug-free. It's not like, say, Mozilla, or even the Linux kernel, or even /bin/ls. These things get tested rigourously, not as an afterthought deligated to the junior programmer.

      That's false reasoning.

      1. No practical software is bug-free.

      2. Testing is never complete.

      3. People make mistakes, even during testing.

      4. Spirit broke down.

      It makes sense, when building a robust system, to do rigorous testing AND have the memory protection.

      VxWorks obviously has a brilliant team of brainwashers^Wsalesmen because they've convinced you that you don't need a feature they don't offer. Perfect!

    4. Re:VxWorks memory, embedded protection by WolfWithoutAClause · · Score: 2, Informative
      And having memory protection only costs you maybe 3% of run speed,

      I'd want to see real, hard numbers.

      Check out any book on OS design. That's about the typical average cost. The processor's memory manager often has a limited list of memory regions, for example 8 or 16, and this is used as a cache for the active regions that are needed. Whenever the processor attempts to access memory outside those regions, an exception/interrupt is thrown, and then the cache needs to be updated, or an exception thrown to that task. That takes a while to process- the amortised cost is typically around that kind of value.

      Clearly there are applications where the N% lost to protection is too much

      In my experience, this is exceptionally rare. That final 3% can nearly always be clawed back with subtle changes to the software. If it really can't- then the processor was too slow for the task in hand in the first place- normal feature creep has a much bigger than 3% effect on the system performance.

      --

      -WolfWithoutAClause

      "Gravity is only a theory, not a fact!"
    5. Re:VxWorks memory, embedded protection by devphil · · Score: 2, Insightful
      It makes sense, when building a robust system, to do rigorous testing AND have the memory protection.

      Absolutely. While building it.

      VxWorks obviously has a brilliant team of brainwashers^Wsalesmen because they've convinced you that you don't need a feature they don't offer. Perfect!

      I forgot, this is slashdot, where VxWorks is the eternal enemy, and second-guessing actual rocket scientists is the national sport.

      IIRC, memory protection was removed from the early versions by popular request, because the cost was too high. Clearly not everyone out there agrees with the opinions stated by sibling posts to yours.

      Me, personally, I don't give a rat's ass one way or the other. (I don't use VxWorks, and haven't had a single segfault in any of my code since I stopped using C.) I just dislike seeing the groupthink mentality defended so vigourously, thus my initial post.

      --
      You cannot apply a technological solution to a sociological problem. (Edwards' Law)
    6. Re:VxWorks memory, embedded protection by eples · · Score: 1

      Protected memory is good for systems which do more than one thing, and/or have parts which can die without killing the whole device (e.g., a desktop computer).

      And also, apparently, good for things that we send to other planets.
      Am I the only one who thinks the above poster just described a system matching the Mars freakin Rover or what?!

      --
      I'm a 2000 man.
    7. Re:VxWorks memory, embedded protection by nathanh · · Score: 1
      I forgot, this is slashdot, where VxWorks is the eternal enemy, and second-guessing actual rocket scientists is the national sport.

      I see. So instead of addressing any of the four points, you tell me I'm wrong, and accuse me of being biassed.

      IIRC, memory protection was removed from the early versions by popular request, because the cost was too high. Clearly not everyone out there agrees with the opinions stated by sibling posts to yours.

      Design by democracy? Is that the patriotic version of designed by a committee? We all know how well that turns out!

      Me, personally, I don't give a rat's ass one way or the other. (I don't use VxWorks,

      Guess what. I do.

      and haven't had a single segfault in any of my code since I stopped using C.) I just dislike seeing the groupthink mentality defended so vigourously, thus my initial post.

      I think it's interesting that somebody who has never used VxWorks is such an expert, while anybody who disagrees is afflicted with groupthink.

      I bet you haven't even read 1984.

    8. Re:VxWorks memory, embedded protection by omnibee · · Score: 1
      There's usually no point in memory protection

      I strongly disagree. Memory protection makes possible to continue the processing of other parts of the system even if a subsystem fails. It might be a non-critical subsystem like a statistics gatherer, which is not critical at all. My point is: if some non-critical subsystem fails, the rest should survive. Memory protection is indispensable exactly for that.

    9. Re:VxWorks memory, embedded protection by devphil · · Score: 1


      Why should I bother addressing any of your points? You started your side of the conversation by saying everything I wrote was "Garbage." Yes, I'd say you're biased. Doesn't sound like you're open to anything but your own viewpoint.

      Do you work for NASA? Do you work for JPL? No? Then I don't think you're qualified to say that their requests and decisions (regarding the use or not of protected memory) are all so obviously wrong. I don't know what their reasons were -- I'm not a rocket scientist either -- but I know the reasons that most other embedded engineers give when they chose to not use such protection.

      I think it's interesting that somebody who has never used VxWorks

      See, dude, that's why I'll be adding you to the killfile once I submit this. I never said "I've never used it." You're not interested in having a discussion. You're interested in looking good.

      I've used it. I don't use VxWorks as an end user on a day-to-day basis, but I'm fairly familiar with it. Familiar enough to participate in this thread, at least. I do interact with it and its designers on a day-to-day basis. I don't know how much more I'm allowed to say before treading on NDAs, so I'll stop with that.

      I read 1984 in junior-high, and in high school, and in two college courses, and I make it a point to read it every year two since. Same with Brave New World and the other standard civil-libertarian-warnings books. Don't really know what your point was trying to be there.

      Go ahead and say whatever you want now, I'm not going to see it.

      --
      You cannot apply a technological solution to a sociological problem. (Edwards' Law)
    10. Re:VxWorks memory, embedded protection by Anonymous Coward · · Score: 0

      Someone hasn't done their homework. There is a released version (VxWorks AE 1.1) with memory protection. It has been in production for several years infact.

      I have the 'pleasure' of working with it for another NASA mission that should launch in... oh... welll..... thirtyhundred years or so.

      Next we need some physics teams to study how WindRiver managed to create a black hole in the middle of their support office.

    11. Re:VxWorks memory, embedded protection by nathanh · · Score: 1
      Why should I bother addressing any of your points?

      Why indeed.

      You started your side of the conversation by saying everything I wrote was "Garbage."

      You're thinking of somebody else. I never even used that word, much less to describe everything you wrote.

      I don't use VxWorks...

      I wonder why you'd say that, then say...

      I do interact with it [VxWorks] and its designers on a day-to-day basis.

      Oh, but you don't use VxWorks. You just "interact" with it. I see.

      I read 1984 in junior-high, and in high school, and in two college courses, and I make it a point to read it every year two since. Same with Brave New World and the other standard civil-libertarian-warnings books. Don't really know what your point was trying to be there.

      Wow. Have you thought about buying another book? It's not healthy to read the same book over and over again. That's... like... compulsive repetitive behaviour.

      See, dude, that's why I'll be adding you to the killfile once I submit this.

      Giggle. Does Slashdot even have killfiles?

      Go ahead and say whatever you want now, I'm not going to see it.

      I couldn't have described you any better if I'd tried. You really summed yourself up beautifully. Even funnier in light of your comment that I'm not open to anybody elses viewpoint.

    12. Re:VxWorks memory, embedded protection by Anonymous Coward · · Score: 0

      wank, wank, wank all day long..

      wank, wank, wank while i sing this song..

      (preferably sung to the tune of "The Severe Beating of a High School Janitor")

      I've never seen such a proud and useless exchange between two logged in members before. I mean, really, you know noone is getting anywhere in a discussion when it boils down to "AND NOW I CAN'T HEAR ANYTHING YOU SAY ANYMORE LALALALALALALALALALA!!!!"

      Of course, I'm not sure which is worse, the person going "LALALA" or the guy who thinks getting the last word makes him even cooler..

      Thanks, fwapdash, you entertain me eternally!

    13. Re:VxWorks memory, embedded protection by Ben+Hutchings · · Score: 1

      Yes, Slashdot has killfiles. Click the grey marble next to a poster's name and you can mark them as a "foe". You can then apply a -6 (or other value) modifier to your foes' comments.

    14. Re:VxWorks memory, embedded protection by sjames · · Score: 1

      That takes a while to process- the amortised cost is typically around that kind of value.

      It's not so much that the 3% is too much, it's that it is not spread evenly over the run time and it makes execution time non-deterministic. Very bad for a hard realtime application.

    15. Re:VxWorks memory, embedded protection by WolfWithoutAClause · · Score: 1
      VxWorks isn't really hard realtime in that sense anyway- it's a multitasking OS.

      Paging in a segment, depends on the processor family, but usually takes rather less than 100 microseconds; which is OK for quite a lot of problems.

      Realtime systems are a continum; it just depends where you are on it as to what techniques are appropriate.

      In 15 years of embedded coding I've accidentally twice written memory stompers, one extremely minor, and I've written code that wasn't a memory stomper, until somebody else shrank the stack... trust me, if I can do it, anyone can. IMHO memory management is well worth using, even if it is only at the debugging stage.

      --

      -WolfWithoutAClause

      "Gravity is only a theory, not a fact!"
  74. Obvious reference... by IversenX · · Score: 3, Funny

    ...and I have this terrible pain in all the diodes down my left side!

    Flash update you say? I wont enjoy it.

    --
    With great numbers come great responsibility!
  75. Science and Engineering Files my ass by geekpuppySEA · · Score: 3, Funny

    It's porn. Someone wanted to be the first guy to get Venus to Mars.

    --
    Intelligent Design: because MATH is HARD.
  76. Obligatory Family Guy Quote by notcreative · · Score: 1

    ...but I don't want to spend a lot of money.

  77. Damn those engineering files by drgonzo59 · · Score: 2, Funny

    NASA technicians are preparing to wipe Spirit's flash memory clean of science and engineering files that have stymied its software.
    ...and put games and pr0n on it, which will make the software work as intended.

  78. It's all REAL by Anonymous Coward · · Score: 0

    Of course Echelon exists. The Illuminati made sure of it. It is said to be interfaced to black helicopter-borne cameras that record everything that goes on over the face of the earth. If you want to find out more, just call Elvis. He is one of the sysadmins now. You'll have to call the main Bildeburger phone number and ask for him. I don't think you'll have that unless you own either a Skull and Bones (tm) or Trilateral Commission membership card.

    Fnord.

    1. Re:It's all REAL by John+Courtland · · Score: 1

      You forgot to add that the Freemasons are the Bildeburgers' calling service.

      --
      Slashdot is proof that Sturgeon's Law applies to mankind.
  79. Our bench is killing us by Hygelac · · Score: 1

    We'd be winning if Earth would quit sending in the second string players (ie. Russia). ;-)

    --
    -- Grow up and use mutt.
    1. Re:Our bench is killing us by Anonymous Coward · · Score: 0

      I know its a troll, but couldn't resist.

      The Russian space program, and in particular the dedicated people there who are struggling through with miniscule budgets and terrible personal compensations are anything BUT the 2nd string.

      Here's hoping that we have the intelligence to team up with the ruskies to go visit mars.

    2. Re:Our bench is killing us by grozzie2 · · Score: 2, Insightful
      We'd be winning if Earth would quit sending in the second string players (ie. Russia). ;-)

      The reality of the situation is, first string (Russia) is all tied up doing manned missions, so they have delegated the robot probes to the second string (usa). This is mostly due to the little detail, second string has no operational man rated vehicles to work with....

      Not quite sure how China plays in yet, but, they also have a manned program these days, so, second place is actually up for grabs, the robot probes may soon have to take the third bench....

  80. Security? by DoctorHibbert · · Score: 5, Interesting

    Other than the huge costs of transmissions equipment, does anyone know what kind of security they use to prevent hackers from doing this (like for instance some mischievous Russian space program scientist)?

    --
    Arbitrary sig
  81. How could they not have tried this on the ground?! by emil · · Score: 1

    They should have completely simulated this mission by putting a rover down in an abandoned field and conducting a full analysis, just as they planned to do on Mars.

    How could they have not stress-tested the file system? I'm amazed!

  82. Re:How could they not have tried this on the groun by Cujo · · Score: 1

    They do test the rover in a sandbox, and very agressively at that. The problem they had was with the cruise files - unrelated to the fact that therover is on the ground. Cruise is 7 months, and the activities there are fairly low risk, so they didn't get the testbed for 7 months uninterrupted to test this.

    I guess I'm not too impressed with armchair hindsight.

    --

    Helium balloons want to be free.

  83. Extensive Testing? by Anonymous Coward · · Score: 0
    Stuff running in such environments is damn near bug-free. It's not like, say, Mozilla, or even the Linux kernel, or even /bin/ls. These things get tested rigourously, not as an afterthought deligated to the junior programmer.

    In this case it looks like extensive testing didn't include checking that the filesystem could handle all of the data files that would be generated during the mission?

    I know there's a hell of a lot to test, but a limitation in the filesystem should have been identified before launch.

  84. are preparing to wipe Spirit's flash memory clean? by odorf · · Score: 2, Funny

    From the example of C-3po in a new hope we can clearly see that whiping things memorys does NOT make them perfect! He was never mean to R2D2 until AFTER his memory was wiped, do they want to start a fight between the two rovers? Better procede with caution!

  85. Secondary backups! by JediDan · · Score: 1

    I don't know what the exact weight of the exact flash card they are using is, but I would think a ROM backup would be in order for future projects.

    Just a thought.

    --
    - Dan
  86. Mars 3D Images by Guitarsenal · · Score: 1, Interesting

    I've converted many of the raw stereo pairs of images from Spirit and Opportunity into 3D anaglyphs (red/blue glasses required). Check em out here: http://members.cox.net/mars3d Check it out. These are way better than the anaglyphs that NASA has released.

  87. Or before lunch, even. by mosel-saar-ruwer · · Score: 1, Funny

    Stuff running in such environments is damn near bug-free. It's not like, say, Mozilla, or even the Linux kernel, or even /bin/ls. These things get tested rigourously, not as an afterthought deligated to the junior programmer.
    In this case it looks like extensive testing didn't include checking that the filesystem could handle all of the data files that would be generated during the mission?

    I know there's a hell of a lot to test, but a limitation in the filesystem should have been identified before launch.

    Hell, it should have been identified before lunch.

  88. flash by BlueMonkey · · Score: 1

    All your flash are belong to us!

  89. I've been wondering the same thing. by mosel-saar-ruwer · · Score: 0, Interesting

    What kind of authentication does NASA employ on deep space transmissions? Surely nothing as complicated as SSL. Probably not even anything as simple as frequency division multiplexing.

    My guess would be no authentication whatsoever [think 1970s protocols, like SMTP, and the attendant proliferation of SPAM], so it seems like anyone with a big dish could just point and shoot.

  90. Re: Actually, it IS all a conspiracy! by SgtSnorkel · · Score: 1

    If the mission had gone smoothly, it wouldn't have garnered nearly the same level of publicity.

    "Oh! Oh! There's a problem!

    -- long, suspense-filled pause --

    "Through diligence and hard work, our brilliant scientists, engineers,
    and technicians were able to rally and fix the problem. Remotely.
    From a completely different planet, even!
    You may continue funding now."

    (Don't get me started on the MS v MikeRoweSoft thing.)

  91. give me a break by ajagci · · Score: 1

    Stuff running in such environments is damn near bug-free.

    Well, apparently VxWorks itself has some serious bugs.

    There's usually no point in memory protection. If the propulsion system walks off the end of a garbage pointer, mission's over. No real use in keeping the guidance system going; it's already on a ballistic uncontrollable arc

    There is no reason for the propulsion system to malfunction just because it "walks off the end of a garbage pointer". Systems can and should be designed that half the subcomponents can "walk off the end of a garbage pointer" and the whole thing should still function.

    But you are right to this degree: the issue is not "protected memory". Protected memory is itself a poor woraround for a language that is ridiculously poor at error handling and that nothing safety-critical or even mildly important should ever get written in: C.

    The sad fact is that the quality of programming for embedded systems is as poor as for anything; they simply try to compensate for that with more testing. And that's not the way to do it.

  92. Uncle Owen! by payndz · · Score: 1

    "I want you to take that unit to Anchorhead in the morning and have its memory erased!"

    --
    You must think in Russian.
  93. "bitch" by Gothmolly · · Score: 1

    Your use of the word 'bitch' proves my point 100%.

    --
    I want to delete my account but Slashdot doesn't allow it.
    1. Re:"bitch" by Anonymous Coward · · Score: 0
      Your use of the word 'bitch' proves my point 100%.

      Bitch Bitch Bitch, there you go again, Bitch... kinda proves my point!

  94. Damn he was old by skintigh2 · · Score: 1

    Tycho Brahe lived for 200 years? That's insane!

    "In the late 15th century Danish astronomer Tycho Brahe made a great number of celestial observations, concentrating on Mars. In 1600 he hired an assistant,"

  95. is this something norton utilities can fix? by Anonymous Coward · · Score: 0

    or perhaps is it because they installed the realplayer onboard?

  96. Automatic diagnostics by Anonymous Coward · · Score: 0

    Is there any reason why Spirit couldn't automatically disable the flash memory? If the problem had been automatically diagnosed by the rover, the loss of communications may not have occurred.

  97. Wind River quiet on the issue by Anonymous Coward · · Score: 0
    Notable absence of this /. article and this problem with Vxworks on the Wind River - Mars Rover page. There's even a White Paper linked on that page that states:
    History has a way of teaching us lessons. However, all too often people ignore the early warning signs of a troubling trend, and in many cases take corrective action only after problems occur repeatedly, with serious consequences. The world of digital electronics is not immune to this phenomenon.
  98. This happens to me all the time... by MikeyToo · · Score: 1

    with my digital camera on a trip. They went nuts taking pictures. Don't these people know ANYTHING abut digital photograpy?

    --
    "Well Ranger Brad, I'm a scientist. I don't believe in anything." - Dr. Roger Fleming
    1. Re:This happens to me all the time... by MikeyToo · · Score: 1

      and I can't spell today either.

      --
      "Well Ranger Brad, I'm a scientist. I don't believe in anything." - Dr. Roger Fleming
  99. Gentlemen... by Guppy06 · · Score: 1

    We can rebuild it. We have the technology.

  100. It's DOS FAT by dvd_tude · · Score: 1

    See this slideset, in particular the one titled "DOS File System" (slide 16.)

    For a 256MB flash, it'd be FAT16. FAT16 only limits the root directory size to 512 entries for a disk type media (from here.)

    Elsewhere it was said that they (NASA's engineers) weren't able to reproduce the problem exactly. I'm still very curious about this... as I said elsehere I've used DOS FAT16 under an RTOS (Thread-X) with lots of files and didn't see this kind of thing happen. Then again we hammered hell out of the FS and even fixed some problems with it.

  101. If I were a NASA scientist... by mnmn · · Score: 2, Interesting

    I would put two 250GB harddisk in the orbiter and make the rovers upload all data they can to the orbiter on each pass, and delete those files automatically. The slower transmission to Earth could then proceed from the disks.

    Each rover uses 256MB flash and so does my 5 megapixel camera. I know for a fact that I can saturate that space fast in a photography frenzy, so I carry a laptop in the car with charger to transfer everything to it if I'll need more pictures.

    Altho the two rovers have been a staggering success on Mars, I am surprised at two overlooks:

    (1) Keeping track of file size and free space.

    (2) What happens if the space is full.

    Even Linux on a measly ARM720T does a much better job.

    --
    "Give orange me give eat orange me eat orange give me eat orange give me you." -Nim Chimpsky
  102. I bet it's all a trick. by Anonymous Coward · · Score: 0

    They're going to wipe it's memory so it can infiltrate the Mars resistance and get close to the mutant leader, Kuato!

  103. to quote Manhunter by acidrain69 · · Score: 1

    "I will be man again some day"

    Give it up for the old school Sierra games.

    Go NASA.

    --
    -- Having a Creationist Museum is like having an Atheist place of worship
  104. Timing by GCP · · Score: 1

    The deadline for the mission was very tight, and there's no slipping a deadline imposed by the motion of planets through space. They either had to declare it ready and "ship", or never ship. They couldn't afford the cost of waiting a couple of years for the next launch window. Now or never.

    So they built as fast as they could, used whatever time they had for testing and tweaking, and if they tweaked they had to restart the testing.

    Every engineer on the team would have preferred more time for testing and tweaking, I'm sure. They didn't have it.

    --
    "Those who have never entered upon scientific pursuits know not a tithe of the poetry by which they are surrounded."
  105. Hope and Longhorn by SuperKendall · · Score: 1

    Might even be a future news: "NASA integrates first non-deterministic filesystem into space probe 'Hope'".

    Sure, that comes when they used Embedded Longhorn with the SQLServer based FS.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
  106. Hey at least they sent it with the rover... by SuperKendall · · Score: 1

    The good news is the disc is right there on the rover.

    The bad news is the robot arm is going to have to wrestle the Lego guy for it. And the Lego guy gets to use the arm he HASN'T been holding up in air for eight months solid...

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
  107. Wow, scary by Validus · · Score: 2, Interesting

    Dam hope that there is not power failure during that operation!!

    As a friend put it "I am afraid to flash my bios without a good UPS."

  108. Classic sysadmin mistake :) by jjgm · · Score: 1

    I guess they were doing df -k rather than df -ki ...

    - J

  109. Skirt-cam! by Anonymous Coward · · Score: 1, Insightful

    From the 1965 Mariner 4 website: We also had access to TV cameras located throughout the building, some with tilt and pan controls. A favorite pastime was to train the camera on the front door, and when a particularly attractive female entered, to follow her on her walk through the building.

    First skirt-cam? Geeks never change.

  110. desktop habbits in an embedded world by Tablizer · · Score: 1

    It seems typical desktop computer habbits were applied to an embedded system that due to hardware and space-environmental-conditioning constraints, does not have a lot of the protections that a full-fledge desktop-like OS has. Thus, their desktop habbits eventually caught up with them. It would be nice to have desktop-like features, but that was not a practical option.

  111. NASA does the impossible! by Simonetta · · Score: 1

    NASA does the impossible! It has made me sympathetic to the rich assholes who secretly transfer millions of dollars out of the USA to tax havens like Lichtenstein and Cayman Islands.

    The Americans insist on pissing away hundreds of millions of dollars on this nonsense, even though they have many real and serious problems that need funds.

    The entire space program is based on two principals:
    one is creating super-weapons to blast the shit out of anyone with space-based lasers who dares challenge the right of global corporations to take their money.
    The second is to provide fat government jobs to white people with science degrees who can't or won't find jobs that provide productive benefit to anyone.

    If the rich decide that they don't want to pay for this horseshit anymore, well good luck to them! Let the rest of the people know how you get away with it so that they can do it too.

  112. Feh. by devphil · · Score: 1
    You're thinking of somebody else.

    I am indeed, since your post appeared after I updated the killfile with new assholes. I do apologize.

    Oh, but you don't use VxWorks. You just "interact" with it. I see.

    Um. If you think that major software is only ever seen/touched/affected by the original authors and the final end-users, and nobody else, then clearly I won't be getting my point across today. Look, I'm sorry, I don't know how much of our work is covered by the NDA, and I'm not going to bother reading it all just for the sake of a /. post. (Nothing personal, I just avoid lawyer crap as much as possible.)

    Wow. Have you thought about buying another book?

    *looks at three bookcases overflowing, sighs, makes mental note to buy a fourth case*

    First I've never read it, now I read it too much. Damned if I do, damned if I don't. Like the VxWorks situation, there seems to be nothing I can say that will make you think, hey, maybe just maybe this guy knows what he's talking about.

    See, when the actual engineers tell me that they've reviewed a certain feature, measured it, analyzed it, and decided that they don't want it, I'm pretty certain they know what they're doing. Frankly, I don't need to worry about some random slashdotter's opposing opinions, because, well, they're clearly wrong in this situation. I mean, I just got off the phone with one of the engineers, and they're quite pleased that "unneeded and unused features are no longer present, or can be disabled". Hostile /. posts from a collection of armchair rocket scientists aren't going to hold a lot of weight with me.

    As I mentioned previously, these kinds of protection are being added in, on request, because they're obviously useful in many scenarios. But nothing comes for free, and what y'all seem determined to ignore is that there are scenarios where the cost of protected memory blocks in time/space/money is not acceptable.

    --
    You cannot apply a technological solution to a sociological problem. (Edwards' Law)
    1. Re:Feh. by nathanh · · Score: 1

      I am indeed, since your post appeared after I updated the killfile with new assholes. I do apologize.

      May I suggest there are other people you have added to your killfiles who don't belong there, because of similar identity mistakes you've made.

      The dangers of killfiles, neatly illustrated. You're banning the person, rather than listening to their point of view. It's rather silly. You'll notice I don't have any friends/foes because I'm opposed to such indiscriminant censorship.

      See, when the actual engineers tell me that they've reviewed a certain feature, measured it, analyzed it, and decided that they don't want it, I'm pretty certain they know what they're doing. Frankly, I don't need to worry about some random slashdotter's opposing opinions, because, well, they're clearly wrong in this situation. I mean, I just got off the phone with one of the engineers, and they're quite pleased that "unneeded and unused features are no longer present, or can be disabled".

      My opinion of engineers is that they're like any other field: 90% of them are effing useless. You say they "measure it" and "analyze it"? In my experience, this is rarer than you might hope. These self-proclaimed "engineers" can say things like "oh, you don't need memory protection" but that doesn't mean they're right. I've worked with embedded "engineers" who held open disdain for C. They wrote everything in assembly, claiming that this was "how things were done!". Their code was always late, buggy, and rewritten for the next revision because it was entirely unmaintainable.

      I have an example. I didn't work on it, but an embedded engineer friend did. It was an embedded photo scanner. The C prototype had been completed. It worked. It met all requirements. It was neat and maintainable. It ran on the spec'd hardware. It was ready to ship. The senior "engineer" in charge (he didn't have an engineering degree) decided it must be rewritten in assembly. Months later the company folded. The incomplete assembly version was larger and slower than the C prototype.

      I have another example, from folklore.org. The Apple II mouse card was prototyped by Burrell and Hertzfeld. They managed to get it working with a single chip and some clever software. Despite a working prototype, the Apple "engineers" decided it could not be implemented in any less than a dozen chips. They believed in hardware, rather than the clever combination of hardware and software.

      As a final note, I have an engineering degree (a real one, from a real university) and I don't think you can call yourself an engineer merely because you obtained that piece of paper. Some of my fellow graduands went on to become accountants and computer programmers. What a waste! I'm not saying they're stupid - I consider every single one of my fellow graduands to have been extremely intelligent - but they didn't care about the nuts and bolts. They weren't engineers. Wozniak and Burrell were engineers. They didn't even have the pieces of paper!

      So my opinion of "engineers" is not very high. I have more respect for the enthusiasts who actually do stuff - whether they be professional or amateur - as opposed to the wankers who say "I work at NASA" and "I have a PhD in astrophysics" as if that justifies every wrong decision they've ever made. I've worked on enough projects to make my own judgement, so when someone says "you don't need memory protection" I know that 9 times out of 10 they're wrong. When they counter "I'm a rocket scientist, I don't need to justify my conclusions" it merely confirms my opinion that they don't know what they're doing. Real Engineers love to justify their reasoning to everybody.

      Hostile /. posts from a collection