Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS.

Path	csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From	Jolly Roger <jollyroger@pobox.com>
Newsgroups	comp.sys.mac.system, comp.sys.mac.apps
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:01:00 GMT
Organization	People for the Ethical Treatment of Pirates
Lines	50
Message-ID	<ehgcdsF212rU1@mid.individual.net> (permalink)
References	<jZmdnTg7M8j_1CzFnZ2dnUU7-TWdnZ2d@earthlink.com> <250220170952524118%nospam@nospam.invalid> <o8sq2l$ol0$1@dont-email.me> <eheag6FkbriU3@mid.individual.net> <250220171625299628%nospam@nospam.invalid> <barmar-38263C.19354325022017@88-209-239-213.giganet.hu> <ehet4qFnl7bU1@mid.individual.net> <o8tm1h$2ai$1@dont-email.me> <ehgahqF1p91U1@mid.individual.net> <here-7DBC87.16441126022017@news.individual.net>
X-Trace	individual.net pcP+9Im+reYPO7MNCgZ/bwe0EE7JRqzUvzsUkApquo871ghIum
Cancel-Lock	sha1:GMd9T2fQCWFvb1wq29PrMyYKqbE=
Mail-Copies-To	nobody
User-Agent	slrn/1.0.1 (Darwin)
Xref	csiph.com comp.sys.mac.system:101260 comp.sys.mac.apps:37644

Cross-posted to 2 groups.

Show key headers only | View raw

On 2017-02-26, android <here@there.was> wrote:
> In article <ehgahqF1p91U1@mid.individual.net>,
>  Jolly Roger <jollyroger@pobox.com> wrote:
>
>> Alrescha <alrescha@gmail.com> wrote:
>> > On 2017-02-26 02:34:02 +0000, Jolly Roger <jollyroger@pobox.com> 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. 
>> 
>> Forcing users to worry about capitalization only complicates matters
>> for the user. Reducing complication (and, yes, the name space)
>> *improves* usability.
>
> There's no reason to remove the case sensitivity of the filesystem.

Reducing complication and improving usability as explained above are
both good enough reasons for me. It's telling that the Mac news groups
and web forums aren't filled with complaints about lack of cases
sensitivity. Most Mac users seem to be perfectly happy to reap the
benefits without complaint.

> My guess is that this is the consequence of Adobes refusal to let apps
> work from case sensitive filesystems

No. Apple's HFS file system have always been case preserving / case
insensitive. And macOS predates Adobe applications; in fact the very
first Adobe application, Adobe Illustrator, was first released in 1987
(three years after the first Mac was introduced) as a Mac-only product.
Apple's decision to go with a case insensitive file system had
absolutely nothing to do with Adobe.

> and IIRC on systems with case sensitive root directories.

Not sure what you are talking about. Can you remember any more?

-- 
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

Thread

csiph-web