Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Jolly Roger Newsgroups: comp.sys.mac.system Subject: Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Date: 26 Feb 2017 16:42:47 GMT Organization: People for the Ethical Treatment of Pirates Lines: 29 Message-ID: References: <250220170952524118%nospam@nospam.invalid> <250220171625299628%nospam@nospam.invalid> X-Trace: individual.net 1daKDVGvGIddqmxkp0bPcw1X1l5JaBpek5QuEYmC2wUbkXzY9P Cancel-Lock: sha1:Vwb4sCZCT0ApI29es5ynvpwdA9A= Mail-Copies-To: nobody User-Agent: slrn/1.0.1 (Darwin) Xref: csiph.com comp.sys.mac.system:101264 On 2017-02-26, Alrescha wrote: > On 2017-02-26 15:28:58 +0000, Jolly Roger said: > >> Alrescha wrote: >>> On 2017-02-26 02:34:02 +0000, Jolly Roger said: >>> >>>> Nobody can argue with the fact that file system name space conflicts are >>>> drastically reduced with case insensitivity >>> >>> I hesitate to point out that by removing case sensitivity, you have >>> reduced the available namespace by half and thus can only have >>> increased the potential for conflicts - Foo, FoO, and FOO now conflict, >>> where before they did not. >> >> And how often does that *actually* happen in real-world usage? As a user of >> case-preserving file systems daily for many years, I can tell you the >> honest answer: roughly never. > > I was pointing out that your statement about conflicts was incorrect. > As for actually happening, I have provided an example. I must have missed your real-world example of how case insensitivity causes a problem. What was it? -- E-mail sent to this address may be devoured by my ravenous SPAM filter. I often ignore posts from Google. Use a real news client instead. JR