Exercise 1: Two Linux Files Collapse Into One on NTFS — Possible Solution ==================================================================== WHAT HAPPENED, IN ONE SENTENCE ------------------------------ "notes.txt" and "Notes.txt" collapsed into a single file because NTFS is case-insensitive by default, while the Linux file system they originated from was case-sensitive. WHY THIS HAPPENED, USING THE CHAPTER'S OWN TABLE ------------------------------ Per this chapter's own compare-table, NTFS is "case-insensitive by default (case-preserving, but 'File.txt' and 'file.txt' collide)" while ext4 is "case-sensitive - 'File.txt' and 'file.txt' are two different files." On the original Linux/ext4 system, "notes.txt" and "Notes.txt" were two genuinely distinct files that could coexist without conflict. The moment they were copied onto an NTFS volume, NTFS treated the two names as referring to the same file, since it only distinguishes files by name while ignoring letter case - so the second file copied overwrote the first (or the copy operation itself would have prompted a "file already exists" conflict, depending on the copy tool used). WHY "CASE-PRESERVING" DOESN'T PREVENT THIS ------------------------------ The chapter's own table specifically notes NTFS is "case-preserving" - meaning it will display whichever exact capitalization was used to create or last rename the file - but that's a display detail only. It does not make case a distinguishing factor when checking whether a name is already in use, which is exactly the check that caused the collision here. WHY THIS IS A PRACTICAL, NOT JUST THEORETICAL, ISSUE ------------------------------ Anyone regularly moving files or project folders between a Linux environment and Windows should treat this as a genuine data-loss risk worth checking for in advance, not a rare edge case - any Linux folder that happens to contain two files differing only by case will silently lose one of them the moment it's copied onto a default NTFS volume. WHY THIS WORKS AS AN ANSWER ------------------------------ It identifies the root cause using this chapter's own explicit compare-table entries for both file systems, distinguishes case-preserving display behavior from case-sensitive uniqueness checking (avoiding a common point of confusion), and frames the practical stakes of the collision rather than treating it as merely a technical curiosity.