Firstly, you can't safely cast pointers to unsigned long. Unsigned long isn't guaranteed to be big enough to hold a pointer value. Secondly, (dst - src >= len) is not even close to the correct condition for testing that the buffers overlap. Thirdly, the reason for not using a backward copy in all cases is that it corrupts the output buffer in 1 of the 2 overlapping cases. Those three huge errors aside, you make some good points.

Not sure why that sentence needed any translation, or why your "translation" was modded insightful. The sentence was quite clear the way it was written.

No, a proof is a proof. What kind of a proof? It's a proof. A proof is a proof, and when you have a good proof, it's because it's proven.

Did you mean the abolition of slavery? We've advanced farther and been more productive since abolition than before abolition. Keep in mind, I'm not necessarily implying causation.

Ramanujan must have gotten on very well with the ladies.

Then there is 'secure boot' which requires UEFI - in the end is less secure than an old BIOS.

Are you saying Secure Boot (using UEFI) is less secure than traditional BIOS, or that UEFI by itself is less secure than traditional BIOS? And either way, I'm curious why you think that?

Your description is close but not quite accurate. NTFS is case-preserving: file names are stored in an exact case on disk. Case-sensitivity actually has nothing to do with what's on disk, it's a property of a given operation. And NTFS has the ability to support either case-sensitive or case-insensitive operations, as needed, on a per-operation basis. What determines whether a given operation is case-sensitive or not is a combination of 3 factors: a global system setting, the subsystem (e.g. Win32 vs Linux), and the app requesting the operation. Incidentally even if you are a "Win32 app", you can still call NT APIs directly, which negates the subsystem from the list of factors.

This is what happens when somebody tries to use applied math to a pure math problem. Who cares what string patterns you see when you express a prime in a certain base. Primeness has no relationship whatsoever to base.

The next logical step after atomic clocks seems to be hydrogen clocks, or "H-clocks" as they are known.

Burning down the building would be another acceptable solution.

Could you explain what you mean by 64-bit file system, specifically? Because what you said doesn't really mean anything without more context. And are you implying that NTFS-3g is not 64-bit (whatever that means) while Microsoft's NTFS is?

The only thing that is fundamentally unknown is the question of fundamental unknowability itself.

Bravo to The Netherlands for taking this stand. I mean that sincerely. They will face an uphill battle however.

The little bastard was probably wearing a Casio watch too.

He took yer job!!!