snicklepuff

> C presents a simple "big array of bytes" memory model that totally abstracts all that complexity.

I don't understand what you mean by this. Machine code itself abstracts away the underlying hierarchical memory structure. Sure, some machine language might have instructions to manipulate the cache, but those are easily invoked from C, using either inline assembly or __builtin functions.

Jesus, $150!? For a smoke detector!? How hard is it to hit the little "mute" button on the cheap one you already have?

This is why they use git - subversively inserting code into git is not possible like it is with CVS

I was jumping around chronologically, the video was shown by a teacher I had in high school. That wasn't clear, sorry.

I've seen and read the entire speech dozens of times: In school, I distinctly remember being given the entire speech transcription and talking about it as a class on more than one occasion. In elementary school, we would have an actor come on our "morning announcements" and re-enact the speech each year. One teacher showed it to us on YouTube in it's entirety.

Is my experience really that unusual?

To imply that the US is somehow out of order to pursue his extradition makes no sense. What does he expect them to do?

IMHO, he should not have run. I don't think he would have any trouble convincing 12 people that what he did was the right thing. Running was bad form.

I don't like this guy, and I don't trust him.

> they couldn't release it under an updated license (like the > ASL2 or GPL3) or dual-license it for compatibility with > other projects without getting clearance from each and > every contributor.

IMHO, this is a huge advantage: it guarantees that the maintainer of the project can't run off and so something crazy. The linux kernel allows every author to retain copyright, and there's some security in that: since it is basically impossible to get clearance from even the most significant subset of copyright holders in the kernel, it will forever be GPLv2.

Look at it this way: if Torvalds were evil, he could require everybody to assign him copyright, and then take everybody's work and let corporations pay him to allow them to use it closed-source enviorments. Or even un-GPL the whole thing and sell it to somebody. (IANAL, obviously - not sure about that last one)

Point is, there is security in nobody having controlling ownership of a project,

Why the hell is CONFIG_PERF enabled in distribution kernels?? A normal server/desktop user would NEVER USE THAT. If you're smart enough to use Perf, you ought to be smart enough to compile your own kernel.

This is a brilliant example of how stupid many distros are with their kernel configurations. They need to start understanding that enabling features that nobody uses only increases the probability of problematic bugs.

Also, they need to stop enabling CONFIG_CC_STACKPROTECTOR. It slows stuff down, and as can be seen here, often doesn't do any good.

Wrong -- works on x86_64 Debian.