Apparently that is a myth: http://nsla.nevadaculture.org/...

Thanks, my kernel also says that ;)

The relevant "or later" clause from GPLv2 is Section 9, for those who are curious.

The point being, Linus could have allowed later versions of GPL. He explicitly decided to disallow them from the start, and has defended that position repeatedly.

Actually no, the Linux kernel is stuck on the GNU GPL v2 because Linus made that decision on purpose. The default GNU license allows for relicencing under any later version, but Linux removed that clause on purpose.

Here's his rant against GPLv3: https://lkml.org/lkml/2006/9/2...

Pro tip: When someone does something retarded on the internet, don't point and claim responsibility.

That dependency graph is beautiful.

I wish gcc had a --fno-circular-dependencies flag to force that on a codebase (much like go does in the language spec).

That is not even a little bit true.
Only 61% of the Canadian voting-eligible public voted at all in the last federal election.
Of those that did vote, 60% voted for a different party, not explicitly against the Tories. Our electoral process is not configured to allow one to vote against a party.

I'm not sure how you got "a pcie bridge over wires rather than on board connectors" from "Expose devices as hotplug PCI-E". Presenting devices to the operating system as PCI-E hotplug in no way implies they actually are PCI-E devices or are in any way electrically similar (much like how "file descriptor" hardly means "file").

In short, I agree with everything you said in the second paragraph, and I think it supports my point. The OS (local CPU) only gets involved with the Thunderbolt controller for communication relevant to it. The controller chip hides all the complexity of packet switching and routing etc. Unless you're on a Mac, which takes all that brilliant design and says "We're going to require the kernel to manage everything the controller chip should be doing for us".

Source: same as before, from someone who has read the relevant spec and implemented a driver - http://www.kroah.com/log/linux/hardware.html

Actually, Thunderbolt on Macs deviate from the specification a fair bit. The Thunderbolt spec is simple: Expose devices as hotplug PCI-E, let the BIOS do everything.

Thunderbolt Macs go out of their way to... not that. Read more at http://www.kroah.com/log/linux/hardware.html.

Nevermind, I found what you meant - link 60 was dead, I checked out 59 (related, not as detailed as 60 promised to be).

I wonder if you could set up a plugin to connect the wayback machine to dead wikipedia references.

Don't know what you mean by stating "Too bad the link is dead." It works for me.

Here's the link from Wikipedia's source:
http://www.bizjournals.com/pittsburgh/news/2012/05/29/spacex-success-brings-pittsburgh-space.html

According to http://en.wikipedia.org/wiki/List_of_Falcon_9_launches, someone has already contracted with them to deliver a payload to the moon (fifth from the bottom of the list).

Disagree. Tumbleweed moves, and anyone who gives it any notice while driving is putting others at risk. Any sane system ought to be able to recognize tumbleweed and give it the appropriate lack of attention.

I think massive improvements are made to safety when object collision is context aware. Heck, in my driving instruction manual they had an ordering of, "What to hit in an emergency situation," went something like "Animals, ditch, traffic on same flow pattern, structures (buildings, poles), pedestrians, oncoming traffic."

An even more obvious use of contexts: There are two objects, a bag and a baby. You have to hit one, which one do you run over? I think it is possible to build systems that make better decisions than chance in this kind of circumstance.

To alert other drivers that:
1. They should pay attention
2. I'm about to get all kinds of crazy

Ah, thanks. I didn't know why it worked, just found it incredibly convenient. And I think in my case it is set somewhere in /etc/profiles.d/.

Note to self: read through bash configuration documentation.

Such as 10km/h?

I would put it to you that situations where one would have to make a bag/baby decision one should not be travelling at highway speeds.

Even though a perfect decision can't be made in every situation, I contend one can do better than, "Fuck it, I'll probably hit it regardless," when operating a motor vehicle.

As someone who has successfully prevented collisions with cats, deer, and moose under differing circumstances (a moose in fog at night is about the most frightening thing I've ever come across), I think the ability to inform ones driving based upon the nature of a sudden unexpected obstacle is a critical part of driving well.