The movie is terrible. There, I just saved you 69 minutes and 55 seconds.

--riney

One of the early releases I downloaded had the amusing "feature" of downloading every message in the background - not just headers, full messages, with attachments. According to the bug report, this was intentional, so that your folders would be accessible without being connected to the network, but it never seemed to know where to stop. It was *constantly* and repeatedly downloading messages, and ate 40 some-odd gigs before I noticed it and went back to 2.

--riney

Until they stop relying on toxic, storable propellants for their manned launchers, and get a better handle on range safety (referring to the first LM-3B launch which took out a village - http://www.youtube.com/watch?v=2qVaXFhu7NE)... how about *no*.

The propellant issue alone ought to be a show-stopper. We knew storable propellants were a horrible idea during Gemini, but did it anyway for expediency. There was legitimate question whether, during an abort, the astronauts would manage to escape what was termed the BFRC - Big F-ing Red Cloud - created when the booster's tanks ruptured and burned.

--riney

Congratulations. It's now your job to check every *single* *freaking* *package* where the DISA specs proscribe a particular version, and see whether or not your vendor backported the security fix. Usually the DISA specs will contain a vulnerability id (CVE-ID or similar) that you can reference against. Google is your friend. The overall process is murder. It's a big reason why I got out of government IT. On a related note, I find the Linux vendor practice of keeping old version numbers, but backporting new fixes into their own trees (Red Hat's "version x.y.z-ELsomeothernumber" system for example) to be categorically infuriating, but that's a different rant. --jwriney

That's cool and all that, but who (or what) flips the pages?

--riney

Sorry, you only get that achievement if you quit browsing Slashdot...

--riney