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: 27 Feb 2017 16:23:35 GMT Organization: People for the Ethical Treatment of Pirates Lines: 35 Message-ID: References: <250220170952524118%nospam@nospam.invalid> <250220171625299628%nospam@nospam.invalid> X-Trace: individual.net gYbJ2zCVqhS84nILT55e3AkrOf0ol3m18a3pL97nZaM5cGCWAr Cancel-Lock: sha1:3Ud0QMWjOR0A3o2gjw7QaseHUKo= Mail-Copies-To: nobody User-Agent: slrn/1.0.1 (Darwin) Xref: csiph.com comp.sys.mac.system:101359 On 2017-02-27, Barry Margolin wrote: > In article , 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 am confident >> you will find some way to discount that. > > You showed an example of how it COULD happen, not how it DOES happen. Bingo. From all appearances the vast majority of Mac users have no problems what-so-ever with case insensitivity in their file systems. -- 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