Microsoft makes the Windows kernel source available to a number of entities [0], but this source is not to be distributed freely. Open Source is usually construed to mean that the source, if you have it, can be distributed to freely.
As an anecdote, I noticed in my tests of Prey that I just don't notice the light in that instant it's turned on. If someone wants to jut get quick pictures of who's using your computer, momentary blinks are probably going to be unnoticed while longer periods of activity are more likely to be noticed.
My experience with DoD networks is that they just tell you it's blocked, not why, and invite you to petition if you do need access to the site in question.
I'm pretty sure this is the case by playing with the OpenCL side of CUDA. If the '--version' flag is passed to the OpenCL compiler (at least the one with CUDA 3.0), info from an LLVM build from a year ago is dumped. The '-cl-nv-verbose' flag is also documented to pass '--verbose' to the ptxas assembler.
In the US it depends, but I'd venture a guess and say most public university libraries are open at least regularly to the general public. Most of the schools in my state are on this [1] list, and most law libraries I've encountered are also open to the public as well. After hours access is usually restricted to those with a library card though.
This isn't just a Mac/iOS community problem, as evidenced by a post like this popping up every week or two. It's a programming/hacker community problem.
Virtualized OS X is allowed within limitations. 10.6 required the Server version to be (legally) virtualized, while 10.7 allows 2 extra copies to be virtualized. In both cases, the host needs to be OS X, on Apple hardware.
Not entirely relevant, but Lion's Kerberos is pretty funky as well. Apple switched to Heimdal from MIT, supposedly marked the Heimdal API 'private' and provided a worse than broken shim between the MIT API and Heimdal.
It turns GSSAPI [1] off, which is typically used with Kerberos. Unless you know you're using it (and in most cases you will know if you are), it's safe to turn it off.
In my experience, Markdown is easier for just words and for things eventually going online. But as soon as I need tables, references, non-trivial layout and especially equations, I pull out LaTeX.
I don't have much more info than this, but it looks like they're both generated with Sphinx (http://sphinx.pocoo.org/), going by the footer from flask, and the common source (both have `<div class="sphinxsidebar">`).
The attribution has a link to here[1] which can get you a days worth of images. --I'm not sure which telescope the article images came from-- The telescope name (or names in the case of the top image) are in the bottom left of the image, and they are from August 9th.
The HTTP request itself is encrypted, but the IP packet (including the source and destination IP addresses) is not. SSL/TLS is application level encryption, and if you wanted to encrypt the actual packet, you need to switch to something like IPsec, but even then you need some sort of routing method (which I can't remember).
Only with Xcode 3. As I mentioned below, Xcode 4 does not include support for PPC. Also, there are really four architectures (i386, x86_64, ppc, ppc64), but Xcode 3.2.6 does not like compiling for ppc64.
Others have answered most of this question, but I'll add a slight addition to supporting 10.5. Since PPC is an unsupported platform, Xcode 4 does not include support for it. I end up using Xcode 3 just for PPC support for one of my projects.
Something I ran into recently was the removal of remote debugging in Xcode 4. The facilities to do it are there, as that is how debugging iOS devices is run, but the ability to debug remote OS X clients is gone.
They're not too bad, the iTunes and iOS images took no more than two minutes, and the Xcode image is about 10 minutes for me. Not saturating my connection, but not terrible.