Bonus points for using a car analogy.

I think they're talking about in-game interaction with NPCs, not cut-scenes. In Modern Warfare for instance, you *need* to listen to your friendlies or you won't get anywhere.

Contributing to open source software is in itself a form of charity work. I chose "Zilch." as the next best option.

Ever tried writing to them? Before you start hurling abuses, did you try verifying your facts?

Last week I tried writing to an HFS+ Journaled FS on Linux, and it managed to corrupt the FS. I had to use an OSX install to run an fsck and fix the partition (and lost 100GB of data out of a total of 250G in the process).

Not if you have a journaled HFS+ filesystem. Also, hpfsck is just simply a joke.

If you think udev and devtmpfs conflict, you don't know what each of them are supposed to do.

If you read about them, you'd know that devtmpfs just populates /dev as devices are discovered by the kernel during boot. Which means udev doesn't have to spend several seconds parsing /sys to populate /dev with information the kernel already had.

Now during init, udev's job is to parse udev rules and add user configuration plus fix the permissions of nodes in /dev. Afterwards it also monitors device addition and generates events which apps can monitor (recent versions added a gobject interface too), and adds device nodes according to rules, if any.

In essence, devtmpfs's job is to allow a bootable system without the need to maintain a static /dev or depend on udev for a recovery shell.

devfs was bad, really bad because there was no naming system back then, and every driver did something different causing utter chaos (which led to different distros patching the kernel in different ways to change the node names). Now there's uniformity, and the kernel knows what to call the basic device nodes created by the drivers.

What does HAL's deprecation have to do with the Linux Kernel's development model?

Replying to negate bad modding.

You got modded troll. Still think so?

The English "or" maps to the operator "OR", but the English "either ... or" maps to the operator "XOR". In other words,

scary or wonderful => scary OR wonderful

either scary or wonderful => scary XOR wonderful

The Doppler Effect should take care of that for you. No matter what kind of sound is made, it's affected by the Doppler Effect.

Or you can use "rm -rf --no-preserve-root /" if you *really* want to stab yourself in the foot.

Does this mean we'll never have sharks with frickin' lasers?

Ah, right, sorry about that. They changed from KDE-by-default to "Choose what you want" in 2005, and now back to KDE.