The 120GB size is definitely something that exists, and it's probably the result of tallying up the winsxs folder. On most Windows machines this folder can be friggin' huge, largely because it stores multiple versions of various system resources. Given that it's also a "special" folder, it's difficult to accurately tell how large it is.
Almost all files under C:\Windows\System32 are hardlinks to corresponding files under C:\Windows\WinSxS. So if you are calculating Windows footprint by counting both of these directories, you are overcounting by a huge margin.
America is not missing out on the next industrial revolution, exactly. They are deliberately skipping over the robots that make the robots, focusing instead on the robots that make the robots that make the robots. They are manually building prototypes now.
The final dollar value of the fine is actually $4,294,967,295 to be exact. This happens to be the highest amount the US DOJ computer system supports currently. VW should consider themselves lucky this time.
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.
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.
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?
Hard to say about case sensitivity. NTFS itself is case-sensitive, actually, but the Win32 layer that normal Windows apps use to access it enforces case-insensitivity (but preserves case otherwise). If the implementation here is a proper NT subsystem, then it should be able to skip that Win32 translation, and use case-sensitive operations directly. But whether it actually does so or not is an interesting question, because if you were to use that approach to actually create files that only differ by case, accessing them from Win32 world will be problematic (but possible; Cygwin knows how to do that, for example), so it may be deliberately disabled. Hopefully, it is a configurable option.
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.
Why not extend NTFS to a 64-bit file system that is backward compatible w/ Microsoft's NTFS
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?
Slashdot Mirror
The 120GB size is definitely something that exists, and it's probably the result of tallying up the winsxs folder. On most Windows machines this folder can be friggin' huge, largely because it stores multiple versions of various system resources. Given that it's also a "special" folder, it's difficult to accurately tell how large it is.
Almost all files under C:\Windows\System32 are hardlinks to corresponding files under C:\Windows\WinSxS. So if you are calculating Windows footprint by counting both of these directories, you are overcounting by a huge margin.
All modern cellphones have GPS in them. What they *NEED* are apps that emulate a sextant.
That's fine, as long as there are parental controls in place.
America is not missing out on the next industrial revolution, exactly. They are deliberately skipping over the robots that make the robots, focusing instead on the robots that make the robots that make the robots. They are manually building prototypes now.
Woe to those who have taken a vow of silence.
Imagine if those who have taken a vow of celibacy had to fornicate just one little time to assert their right to remain celibate.
Did they look on the floor nearby? Did they look in the couch? How about near where they put their keys?
You ever get one stuck in your exhaust pipe? It ain'tÂpretty.
Pretty sure it means autobiographical pilot.
The final dollar value of the fine is actually $4,294,967,295 to be exact. This happens to be the highest amount the US DOJ computer system supports currently. VW should consider themselves lucky this time.
Wish I hadn't already replied to this thread so I could mod you up!
If Apple makes $2bn and all their competitors collectively lose $2bn, then what % of the industry's profits does Apple take?
If Hillary becomes president, then it's pointless.
Exactly. Hillary plans to run the Internet from personal DNS servers in her basement.
Argh!! I just installed it. Why will it be less useful soon?
I clap my hands. That assumes, of course, that I know I'm happy.
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?
Hard to say about case sensitivity. NTFS itself is case-sensitive, actually, but the Win32 layer that normal Windows apps use to access it enforces case-insensitivity (but preserves case otherwise). If the implementation here is a proper NT subsystem, then it should be able to skip that Win32 translation, and use case-sensitive operations directly. But whether it actually does so or not is an interesting question, because if you were to use that approach to actually create files that only differ by case, accessing them from Win32 world will be problematic (but possible; Cygwin knows how to do that, for example), so it may be deliberately disabled. Hopefully, it is a configurable option.
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.
Why not extend NTFS to a 64-bit file system that is backward compatible w/ Microsoft's NTFS
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.