Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.sys.mac.system > #101287
| From | Snit <usenet@gallopinginsanity.com> |
|---|---|
| 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 | 2017-02-26 13:29 -0700 |
| Message-ID | <D4D888D6.94192%usenet@gallopinginsanity.com> (permalink) |
| References | (4 earlier) <o8src7$tfl$1@dont-email.me> <o8tp2q$vg5$2@news.datemas.de> <o8ut69$ev9$1@dont-email.me> <o8v553$cr4$1@news.datemas.de> <o8vbem$58q$1@dont-email.me> |
On 2/26/17, 12:50 PM, in article o8vbem$58q$1@dont-email.me, "Alrescha"
<alrescha@gmail.com> wrote:
> On 2017-02-26 18:01:06 +0000, Alan Baker <alangbaker@telus.net> said:
>
>> So for the rest of time, you have to remember which is the original
>> version and which the newer...
>> ...by minor variations in capitalization...
>> ...and you think that is LESS complicated?
>
> It is not complicated, it is immediately apparent. Obvious. Moreover,
> it matches the real world. These objects are *distinguished* by case.
> Case is important - It is "macOS", not "MacOS" or "MACOS". These
> things are not the same (see also: e e cummings).
>
> You asked for a real world example and I provided one. Discount it as
> you may, those in opposition have only suggested imaginary users who
> are unable to find their files using their equally mythical search
> tools which somehow fail when they encounter the case-sensitive
> filesystem tyranically forced upon them by some unnamed oppressor.
> Ridiculous. There has been no rational justification for the torches
> and pitchforks.
>
> A.
>
There are edge cases where you might want "macOS" and "MacOS" in the same
folder, but those are rare and FAR more often, and even in those cases, it
is more likely to lead to confusion than benefit. Heck, if someone tells
you, vocally, to open the "Mac OS" folder which would you open? Who knows...
you would need more context or more explanation.
You can get this with other names, too, of course, such as with "Mac-OS" but
that is easily said as "Mac dash OS".
Really comes down to the developers of macOS and Windows went out of their
way to add this benefit for a reason. Cannot find it off hand, but there is
a quote from Dennis Ritchie where he speaks about how when he was developing
C he just took it as a given and gave it no real thought. He also spoke
about how his development favored "simplicity over perfection" and it is
more simple to NOT add extra code to have case insensitivity.
I was not done because he or anyone else was saying it was better. It was
based on the technology of the time.
In looking for that quote I did find a couple of related posts of mine where
I talked about related issues:
* Case sensitivity in Linux leading to a risk of lost data on drives that
are shared with more common environments:
<http://tmp.gallopinginsanity.com/NTFS_WIN_LINUX.mov>.
* Case sensitivity with variable names (not the same as file names, but
related). What I found at the time was this:
Clark Atlanta University
Dublin City University
Eastern Michigan University
GeorgeTown University
Ithaca College
Michigan State University
Purdue University
Southeastern Louisiana University
Southern Illinois University
University of Hawaii
University of Maine
University of Maryland, Baltimore County
Virginia Tech
Western Michigan University
14 colleges and universities... and they all side with the idea that case
sensitivity leads to the problems I talk about. Here is what they say:
Disadvantages:
* Readability: names that look alike are different
- Worse in C++, Java, and C# because predefined names are mixed
case (e.g. IndexOutOfBoundsException)
* Writability:
- Must remember exact spelling
- Case sensitive languages that do not require variable declarations
also have a writability issue: it's too easy to accidentally
create a new variable
* Millions of programmer and user hours lost on case not right.
--
Personal attacks from those who troll show their own insecurity. They cannot
use reason to show the message to be wrong so they try to feel somehow
superior by attacking the messenger.
They cling to their attacks and ignore the message time and time again.
Back to comp.sys.mac.system | Previous | Next — Previous in thread | Next in thread | Find similar
Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Ant <ant@zimage.comANT> - 2017-02-25 01:07 -0800
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. nospam <nospam@nospam.invalid> - 2017-02-25 09:52 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Ant <ant@zimage.comANT> - 2017-02-25 09:58 -0800
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Jolly Roger <jollyroger@pobox.com> - 2017-02-25 18:15 +0000
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Ant <ant@zimage.comANT> - 2017-02-25 10:35 -0800
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Alrescha <alrescha@gmail.com> - 2017-02-25 15:41 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. nospam <nospam@nospam.invalid> - 2017-02-25 15:46 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Alrescha <alrescha@gmail.com> - 2017-02-25 16:03 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. nospam <nospam@nospam.invalid> - 2017-02-25 16:25 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Jolly Roger <jollyroger@pobox.com> - 2017-02-25 21:29 +0000
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Barry Margolin <barmar@alum.mit.edu> - 2017-02-25 19:31 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Alrescha <alrescha@gmail.com> - 2017-02-25 16:47 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. nospam <nospam@nospam.invalid> - 2017-02-25 16:55 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Barry Margolin <barmar@alum.mit.edu> - 2017-02-25 19:35 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. nospam <nospam@nospam.invalid> - 2017-02-26 02:53 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. android <here@there.was> - 2017-02-26 09:29 +0100
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Alan Baker <alangbaker@telus.net> - 2017-02-25 21:28 -0800
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Jolly Roger <jollyroger@pobox.com> - 2017-02-26 05:58 +0000
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Alrescha <alrescha@gmail.com> - 2017-02-26 10:47 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. nospam <nospam@nospam.invalid> - 2017-02-26 12:12 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Alrescha <alrescha@gmail.com> - 2017-02-26 12:22 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. nospam <nospam@nospam.invalid> - 2017-02-26 12:25 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Jolly Roger <jollyroger@pobox.com> - 2017-02-26 17:25 +0000
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Alan Baker <alangbaker@telus.net> - 2017-02-26 10:01 -0800
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Alrescha <alrescha@gmail.com> - 2017-02-26 14:50 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Alan Baker <alangbaker@telus.net> - 2017-02-26 12:12 -0800
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Alrescha <alrescha@gmail.com> - 2017-02-26 15:33 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Alan Baker <alangbaker@telus.net> - 2017-02-26 12:40 -0800
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Alrescha <alrescha@gmail.com> - 2017-02-26 15:50 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Alan Baker <alangbaker@telus.net> - 2017-02-26 15:14 -0800
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Alrescha <alrescha@gmail.com> - 2017-02-26 18:42 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Alan Baker <alangbaker@telus.net> - 2017-02-26 16:29 -0800
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Alrescha <alrescha@gmail.com> - 2017-02-26 19:47 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Lewis <g.kreme@gmail.com.dontsendmecopies> - 2017-02-27 05:53 +0000
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Barry Margolin <barmar@alum.mit.edu> - 2017-02-27 01:31 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Alrescha <alrescha@gmail.com> - 2017-02-27 11:11 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Snit <usenet@gallopinginsanity.com> - 2017-02-26 13:29 -0700
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Barry Margolin <barmar@alum.mit.edu> - 2017-02-27 01:30 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. nospam <nospam@nospam.invalid> - 2017-02-27 07:02 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Lewis <g.kreme@gmail.com.dontsendmecopies> - 2017-02-26 09:46 +0000
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Jolly Roger <jollyroger@pobox.com> - 2017-02-25 21:15 +0000
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. nospam <nospam@nospam.invalid> - 2017-02-25 16:25 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Barry Margolin <barmar@alum.mit.edu> - 2017-02-25 19:35 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Jolly Roger <jollyroger@pobox.com> - 2017-02-26 02:34 +0000
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Alrescha <alrescha@gmail.com> - 2017-02-25 23:39 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Alan Baker <alangbaker@telus.net> - 2017-02-25 21:30 -0800
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. nospam <nospam@nospam.invalid> - 2017-02-26 02:53 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Jolly Roger <jollyroger@pobox.com> - 2017-02-26 15:28 +0000
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. android <here@there.was> - 2017-02-26 16:44 +0100
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Jolly Roger <jollyroger@pobox.com> - 2017-02-26 16:01 +0000
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. android <here@there.was> - 2017-02-26 17:53 +0100
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Jolly Roger <jollyroger@pobox.com> - 2017-02-26 17:02 +0000
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. nospam <nospam@nospam.invalid> - 2017-02-26 12:12 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Jolly Roger <jollyroger@pobox.com> - 2017-02-26 17:16 +0000
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. android <here@there.was> - 2017-02-26 18:18 +0100
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Jolly Roger <jollyroger@pobox.com> - 2017-02-26 17:23 +0000
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. android <here@there.was> - 2017-02-26 18:30 +0100
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Jolly Roger <jollyroger@pobox.com> - 2017-02-26 18:44 +0000
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. android <here@there.was> - 2017-02-27 06:50 +0100
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Lewis <g.kreme@gmail.com.dontsendmecopies> - 2017-02-26 21:47 +0000
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Peter Köhlmann <peter-koehlmann@t-online.de> - 2017-02-26 23:20 +0100
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Lewis <g.kreme@gmail.com.dontsendmecopies> - 2017-02-27 05:41 +0000
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. android <here@there.was> - 2017-02-27 06:53 +0100
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Peter Köhlmann <peter-koehlmann@t-online.de> - 2017-02-27 10:31 +0100
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. android <here@there.was> - 2017-02-27 10:48 +0100
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Peter Köhlmann <peter-koehlmann@t-online.de> - 2017-02-27 11:04 +0100
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. android <here@there.was> - 2017-02-27 12:33 +0100
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Snit <usenet@gallopinginsanity.com> - 2017-02-27 09:38 -0700
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Snit <usenet@gallopinginsanity.com> - 2017-02-27 09:36 -0700
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Peter Köhlmann <peter-koehlmann@t-online.de> - 2017-02-27 18:19 +0100
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Snit <usenet@gallopinginsanity.com> - 2017-02-27 10:34 -0700
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Lewis <g.kreme@gmail.com.dontsendmecopies> - 2017-02-28 09:42 +0000
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Peter Köhlmann <peter-koehlmann@t-online.de> - 2017-02-28 11:07 +0100
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Snit <usenet@gallopinginsanity.com> - 2017-02-26 22:58 -0700
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Peter Köhlmann <peter-koehlmann@t-online.de> - 2017-02-27 10:32 +0100
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. android <here@there.was> - 2017-02-27 06:50 +0100
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. nospam <nospam@nospam.invalid> - 2017-02-26 12:12 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. android <here@there.was> - 2017-02-26 18:14 +0100
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Alrescha <alrescha@gmail.com> - 2017-02-26 10:55 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Jolly Roger <jollyroger@pobox.com> - 2017-02-26 16:42 +0000
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Barry Margolin <barmar@alum.mit.edu> - 2017-02-27 01:28 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Jolly Roger <jollyroger@pobox.com> - 2017-02-27 16:23 +0000
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. android <here@there.was> - 2017-02-27 17:34 +0100
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Snit <usenet@gallopinginsanity.com> - 2017-02-27 09:34 -0700
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Alrescha <alrescha@gmail.com> - 2017-02-27 11:40 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Snit <usenet@gallopinginsanity.com> - 2017-02-27 09:53 -0700
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Alrescha <alrescha@gmail.com> - 2017-02-27 12:12 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Jolly Roger <jollyroger@pobox.com> - 2017-02-27 17:19 +0000
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Snit <usenet@gallopinginsanity.com> - 2017-02-27 10:27 -0700
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Lewis <g.kreme@gmail.com.dontsendmecopies> - 2017-02-28 10:31 +0000
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Alrescha <alrescha@gmail.com> - 2017-02-28 09:17 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Jolly Roger <jollyroger@pobox.com> - 2017-02-27 17:17 +0000
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. nospam <nospam@nospam.invalid> - 2017-02-27 12:25 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Jolly Roger <jollyroger@pobox.com> - 2017-02-27 18:29 +0000
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Snit <usenet@gallopinginsanity.com> - 2017-02-27 12:58 -0700
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Alrescha <alrescha@gmail.com> - 2017-02-27 14:10 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. nospam <nospam@nospam.invalid> - 2017-02-27 18:23 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Snit <usenet@gallopinginsanity.com> - 2017-02-27 10:27 -0700
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Alrescha <alrescha@gmail.com> - 2017-02-27 12:47 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Jolly Roger <jollyroger@pobox.com> - 2017-02-27 18:24 +0000
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Alrescha <alrescha@gmail.com> - 2017-02-27 14:03 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Jolly Roger <jollyroger@pobox.com> - 2017-02-27 20:48 +0000
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Alrescha <alrescha@gmail.com> - 2017-02-27 16:12 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Jolly Roger <jollyroger@pobox.com> - 2017-02-27 21:23 +0000
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. "David B." <DavidB@nomail.afraid.invalid> - 2017-02-27 20:33 +0000
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Jolly Roger <jollyroger@pobox.com> - 2017-02-27 20:51 +0000
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Barry Margolin <barmar@alum.mit.edu> - 2017-02-27 01:26 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Barry Margolin <barmar@alum.mit.edu> - 2017-02-27 01:24 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. nospam <nospam@nospam.invalid> - 2017-02-26 02:53 -0500
Re: Unable to migrate TM's encrypted case sensitive datas to a new drive with non-case sensitive encrypted HFS. Jolly Roger <jollyroger@pobox.com> - 2017-02-25 15:41 +0000
csiph-web