Path: csiph.com!2.us.feeder.erje.net!feeder.erje.net!1.eu.feeder.erje.net!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 02:34:02 GMT Organization: People for the Ethical Treatment of Pirates Lines: 34 Message-ID: References: <250220170952524118%nospam@nospam.invalid> <250220171625299628%nospam@nospam.invalid> X-Trace: individual.net 6MQeaUnQWGfudblKM/KKawjOlBQ1EAZEJy1qYCqzuYAPlUGkSA Cancel-Lock: sha1:xCbkCq7HimE+OLR8GIZwWBvKZko= Mail-Copies-To: nobody User-Agent: slrn/1.0.1 (Darwin) Xref: csiph.com comp.sys.mac.system:101214 On 2017-02-26, Barry Margolin wrote: > In article <250220171625299628%nospam@nospam.invalid>, > nospam wrote: > >> In article , Jolly Roger >> wrote: >> >> > >> don't use a case sensitive file system. why would anyone want to do >> > >> that anyway? >> > > >> > > For what it's worth, all of my non-OS filesystems are case-sensitive >> > > (with no issues). Why whould anyone want to do anything else? >> > >> > It's completely unnecessary. >> >> and makes the simplest things harder. > > Such as? Nobody can argue with the fact that file system name space conflicts are drastically reduced with case insensitivity, since one no longer has to be concerned with any potential difference between different capitalizations of the same string. It's only natural that such simplicity increases productivity. Simplification of the interface is a basic human interface design concept. Also as has been mentioned, some unfortunately popular software is written in such a way that it malfunctions on case sensitive files systems. There's really no need for any Mac user to format a native Mac volume with case sensitivity. -- 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