https://whereismydata.wordpres... "There is one $BitMap per NTFS volume (not per disk). The $BitMap is the 7th entry (MFT record number 6) in the MFT."
True to NT's was rooted in VAX/VMS. The VAX/VMS FILES-11 disk structure contains the same type of file, named BITMAP.SYS, for each volume. https://www.itec.suny.edu/scsy...

Apparently the NT designers felt putting a $ in names was a reasonable way to hide file names and network shares from ordinary list requests. So this latest bug follows an old IIS exploit using $ in a Alternate Data Stream suffix on a URL to the webserver. https://owasp.org/www-communit...
The $ will keep the users away from these important, hidden things! Hail the mighty dollar sign! :)

AbramPlace744 http://slashdot.org/~AbramPlac... mentions http://laserjammer.org/ as a source, but the source seems to be confused about how radar gun technology works.

We discovered a wonderful use for the warm-hearted student who was never going to get an A.

When someone was too embarrassed to ask a "stupid" question, we would have the "Designated Idiot" ask it. The professor might sigh a bit, but would always give a more complete answer, so the rest of us understood the material more completely.

And there were benefits all around. In a series of classes, we had a professor known to subjectively ding student's grades for "dumb" questions. Our "Designated Idiot" kept the class grades a bit higher as a result. In this class and others, we noticed that our "Designated Idiot" tended to get a higher letter grade than the test scores might have suggested.

In many cases, while it interrupted the flow of the the class, the professors saw the benefit in quizzes and tests on the topics. When the "dumb question" had been asked, the material covered was retained far better by the class.

So don't shoot the idiot. Find them a role that helps everyone!

We had a better system. Launched all its satellite payloads pretty well. Only one Tracking and Data Relay Satellite was lost. Human cost was 14 of our best and brightest people over the launch system's lifetime. See: http://en.wikipedia.org/wiki/STS-51-L and http://en.wikipedia.org/wiki/STS-107 .

NASA, and now picking up the ball DOD, decided to try and eliminate the human cost. The result, http://en.wikipedia.org/wiki/Boeing_X-37, just had a successful launch. Originally, it was to be launched from the shuttle (a shuttle within a shuttle), but the Columbia disaster changed that.

Other ideas still proceed, but slowly...

By banning wikileaks access, any subsequent access is therefore suspect. Also by banning access, any DNS lookup of www.wikileaks.org can set off the bells and whistles, even if the follow up is years later. Banning access reduces the number of leads to track down.

One of the keys to Cassini's success has been flexibility. Using fancy flying, NASA/ESA were able to save the payload Huygens probe mission, which had an almost fatal communications flaw.
The story has a hero, Boris Smeds, a Swedish radio engineer for the ESA, who pushed and pushed because he found out something was very wrong with the Huygens payload to be launched from Cassini probe.


Slashdot covered this well and humorously. See substitute links provided for 6 years of bit rot on URL's :-)
Saving Huygens

"Titan Calling: How a Swedish engineer saved a once-in-a-lifetime mission to Saturn's mysterious moon"

and The story behind "Titan Calling"

For completeness sake, here is a NASA/JPL paper on "What we can do to fix the problem"
Resolving the Cassini/Huygens Relay Radio Anomaly

The paper's "lessons learned" are particularly important:

• Spacecraft subsystems must be tested to all of their requirements before launch (this would have helped Hubble Space Telescope, too).
• Keep engineering model and flight spares operational throughout the mission.
• Documentation of Spacecraft Hardware and testing.
  "It is important to keep proper documentation of all tests so this information is available when something goes wrong."
• Never intentionally throw away data in a deep space mission.
  Spacecraft systems need to have an appropriate level of reconfigurability in flight. "This anomaly would have been easy to solve if there has been even a modest amount of reconfigurability in the PSA."

Doppler Shift? What is this Doppler Shift thing you speak of? :-)

Permanent: means it lasts until ISS de-orbit in 2016. Yup, idiocy still planned. See: (In glorious PowerPoint)

http://www.nasa.gov/pdf/386764main_09-15-09_Human_Spaceflight_Testimony.pdf

http://titan04.ksc.nasa.gov/shuttle/nexgen/Nexgen_Downloads/378555main_02-Sally_Charts_v11.ppt

Or just search via Google: for iss +"de-orbit" site:nasa.gov

http://www.google.com/search?hl=en&q=iss+%22de-orbit%22+site%3Anasa.gov

In another instance,

wrote a loving modified dd that writes to multiple files and streams to multiple programs at the same time. The program, dcfldd, also introduces the sorely missed VERIFY operation, and even block-by-block hashes, ( dcfldd Man page)

Maybe someone will combine this with dd_rescue, ddrescue and dd_rhelp to make the ultimate "Convert and Copy" utility :-)

Ah and I can dream of SCTP support too :-)

True,

witness this

From: Safe and Scalable Multicore Computing
Request for Proposals 2008
http://research.microsoft.com/ur/us/fundingopps/RFPs/SafeScalableMulticore_RFP.aspx