Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.advocacy > #286473
| From | owl <owl@rooftop.invalid> |
|---|---|
| Newsgroups | comp.os.linux.advocacy |
| Subject | Re: NTFS is case-sensitive |
| Date | 2015-03-28 17:28 +0000 |
| Organization | ok by me, so long as it doesn't get out of hand |
| Message-ID | <bhf93.hjrow@rooftop.invalid> (permalink) |
| References | <bvh893r.a30rp@rooftop.invalid> <mf6n1h$i4p$3@dont-email.me> <hgheu0.paf3@rooftop.invalid> |
owl <owl@rooftop.invalid> wrote: > DFS <nospam@dfs.com> wrote: >> On 3/27/2015 6:46 PM, owl wrote: >>> NTFS is not "case-insensitive, case-preserving" as has been crowed about >>> here forever.I recently was fooling around and found that I could >>> mount NTFS under linux and create files with names that differed >>> only in case. Even windows explorer would still show those files >>> in a listing. >>> So I decided to do a little digging, and this pops up: >>> >>> http://support.microsoft.com/en-us/kb/100625 >>> <quote> >>> Filenames are Case Sensitive on NTFS Volumes >>> >>> Collapse imageSUMMARY >>> As part of the requirements for POSIX compliance, the Windows NT File >>> System (NTFS) provides a case-sensitive file and directory naming >>> convention. Even though NTFS and the POSIX subsystem each handle >>> case-sensitivity well, 16-bit Windows-based, MS-DOS-based, OS/2-based, >>> and Win32-based applications do not. >>> Collapse imageMORE INFORMATION >>> In NTFS, you can create unique file names, stored in the same directory, >>> that differ only in case. For example, the following filenames can >>> coexist in one directory on an NTFS volume: >>> CASE.TXT >>> case.txt >>> case.TXT >>> ... >>> </quote> >>> >>> Did not know that. :) >> Neither does my NTFS volume on Win7-64bit. >> Try to copy tree.txt to Tree.txt, and >> Windows Explorer: "There is already a file with the same name in this >> location." >> Does that mean Windows Explorer (explorer.exe) is 32-bit? The file is >> found in C:\Windows. >> Also fails in cmd windows: "The file cannot be copied onto itself." >> cmd.exe is found in C:\Windows\System32, which holds 64-bit files on >> Win7-64 (cmd.exe is also found in C:\Windows\SysWOW64, which holds >> 32-bit files on Win7-64). >> When you run cmd in the Start box, it runs the [supposed] 64-bit version >> of cmd.exe (the one found in System32). > I didn't quote the whole page. Here's the rest: > <quote> > ... > Other inconsistencies also exist. The Windows NT Command Prompt and > File Manager correctly display the names of the files. However, normal > commands, such as COPY, fail when you attempt to access one or more > filenames that differ only in case. > NTFS supports two slightly different modes of operation that can be > selected by the subsystem of the application interacting with NTFS. The > first is fully case sensitive and demands that file names supplied > by the application match the names stored on disk including case if > the file on disk is to be selected. The second mode of operation is > case preserving but not case sensitive. This means that applications > can select files on the disk even if the supplied name differs in case > from the name stored on the disk. Note that both modes preserve the case > used to create the files. The difference in behavior noted here applies > only when an application needs to locate an existing file. POSIX takes > advantage of the full case sensitive mode, while MS-DOS, WOW, and Win32 > subsystems use the case insensitive mode. > </quote> Oh, and this KB article was written for NT 3.1. So it's not a 32-bit vs 64-bit thing. NTFS has apparently been fully case-sensitive from the get-go.
Back to comp.os.linux.advocacy | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
NTFS is case-sensitive owl <owl@rooftop.invalid> - 2015-03-27 22:46 +0000
Re: NTFS is case-sensitive Slimer <slvrslmr@lv.c> - 2015-03-27 19:29 -0400
Re: NTFS is case-sensitive John Gohde <john.h.gohde@gmail.com> - 2015-03-28 08:45 -0700
Re: NTFS is case-sensitive DFS <nospam@dfs.com> - 2015-03-28 16:00 +0000
Re: NTFS is case-sensitive owl <owl@rooftop.invalid> - 2015-03-28 16:26 +0000
Re: NTFS is case-sensitive DFS <nospam@dfs.com> - 2015-03-28 12:56 -0400
Re: NTFS is case-sensitive owl <owl@rooftop.invalid> - 2015-03-28 17:06 +0000
Re: NTFS is case-sensitive John Gohde <john.h.gohde@gmail.com> - 2015-03-28 10:32 -0700
Re: NTFS is case-sensitive Snit <usenet@gallopinginsanity.com> - 2015-03-28 13:08 -0700
Re: NTFS is case-sensitive DFS <nospam@dfs.com> - 2015-03-28 22:22 -0400
Re: NTFS is case-sensitive Snit <usenet@gallopinginsanity.com> - 2015-03-28 21:40 -0700
Re: NTFS is case-sensitive Steve Carroll <fretwizzer@gmail.com> - 2015-03-28 22:23 -0700
Re: NTFS is case-sensitive DFS <nospam@dfs.com> - 2015-03-29 11:06 -0400
Re: NTFS is case-sensitive owl <owl@rooftop.invalid> - 2015-03-29 15:12 +0000
Re: NTFS is case-sensitive DFS <nospam@dfs.com> - 2015-03-29 21:22 -0400
Re: NTFS is case-sensitive Snit <usenet@gallopinginsanity.com> - 2015-03-29 23:08 -0700
Re: NTFS is case-sensitive Snit <usenet@gallopinginsanity.com> - 2015-03-29 09:18 -0700
Re: NTFS is case-sensitive DFS <nospam@dfs.com> - 2015-03-29 21:22 -0400
Re: NTFS is case-sensitive Snit <usenet@gallopinginsanity.com> - 2015-03-29 18:27 -0700
Re: NTFS is case-sensitive owl <owl@rooftop.invalid> - 2015-03-30 02:16 +0000
Re: NTFS is case-sensitive DFS <nospam@dfs.com> - 2015-03-30 09:49 -0400
Re: NTFS is case-sensitive Snit <usenet@gallopinginsanity.com> - 2015-03-30 08:24 -0700
Re: NTFS is case-sensitive owl <owl@rooftop.invalid> - 2015-03-30 17:06 +0000
Re: NTFS is case-sensitive Snit <usenet@gallopinginsanity.com> - 2015-03-30 12:19 -0700
Re: NTFS is case-sensitive owl <owl@rooftop.invalid> - 2015-03-30 23:54 +0000
Re: NTFS is case-sensitive owl <owl@rooftop.invalid> - 2015-03-31 00:06 +0000
Re: NTFS is case-sensitive Steve Carroll <fretwizzer@gmail.com> - 2015-03-30 17:12 -0700
Re: NTFS is case-sensitive Snit <usenet@gallopinginsanity.com> - 2015-03-30 17:41 -0700
Re: NTFS is case-sensitive Snit <usenet@gallopinginsanity.com> - 2015-03-30 17:15 -0700
Re: NTFS is case-sensitive owl <owl@rooftop.invalid> - 2015-03-31 01:07 +0000
Re: NTFS is case-sensitive Snit <usenet@gallopinginsanity.com> - 2015-03-30 18:21 -0700
Re: NTFS is case-sensitive Snit <usenet@gallopinginsanity.com> - 2015-03-30 12:24 -0700
Re: NTFS is case-sensitive DFS <nospam@dfs.com> - 2015-03-30 20:46 -0400
Re: NTFS is case-sensitive owl <owl@rooftop.invalid> - 2015-03-31 01:52 +0000
Re: NTFS is case-sensitive Snit <usenet@gallopinginsanity.com> - 2015-03-30 19:10 -0700
Re: NTFS is case-sensitive Steve Carroll <fretwizzer@gmail.com> - 2015-03-30 11:35 -0700
Re: NTFS is case-sensitive DFS <nospam@dfs.com> - 2015-03-30 23:09 -0400
Re: NTFS is case-sensitive Steve Carroll <fretwizzer@gmail.com> - 2015-03-30 22:01 -0700
NTFS is not the best filesystem taka0038@gmail.com - 2015-03-31 18:52 -0700
Re: NTFS is not the best filesystem Slimer <slvrslmr@lv.c> - 2015-03-31 22:51 -0400
Re: NTFS is case-sensitive DFS <nospam@dfs.com> - 2015-03-30 09:48 -0400
Re: NTFS is case-sensitive Snit <usenet@gallopinginsanity.com> - 2015-03-30 08:44 -0700
Re: NTFS is case-sensitive Steve Carroll <fretwizzer@gmail.com> - 2015-03-30 09:37 -0700
Re: NTFS is case-sensitive DFS <nospam@dfs.com> - 2015-03-30 20:50 -0400
Re: NTFS is case-sensitive Snit <usenet@gallopinginsanity.com> - 2015-03-30 19:14 -0700
Re: NTFS is case-sensitive Steve Carroll <fretwizzer@gmail.com> - 2015-03-28 17:09 -0700
Re: NTFS is case-sensitive owl <owl@rooftop.invalid> - 2015-03-29 00:24 +0000
Re: NTFS is case-sensitive DFS <nospam@dfs.com> - 2015-03-28 22:26 -0400
Re: NTFS is case-sensitive owl <owl@rooftop.invalid> - 2015-03-28 16:09 +0000
Re: NTFS is case-sensitive DFS <nospam@dfs.com> - 2015-03-28 13:06 -0400
Re: NTFS is case-sensitive owl <owl@rooftop.invalid> - 2015-03-28 17:15 +0000
Re: NTFS is case-sensitive owl <owl@rooftop.invalid> - 2015-03-28 17:28 +0000
Re: NTFS is case-sensitive owl <owl@rooftop.invalid> - 2015-03-28 18:35 +0000
Re: NTFS is case-sensitive owl <owl@rooftop.invalid> - 2015-03-29 12:57 +0000
csiph-web