Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.sys.mac.system > #101374
| 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-27 10:27 -0700 |
| Message-ID | <D4D9AF7C.942C0%usenet@gallopinginsanity.com> (permalink) |
| References | (10 earlier) <barmar-68284F.01281927022017@88-209-239-213.giganet.hu> <ehj247Filj7U1@mid.individual.net> <o91kn5$2eo$1@dont-email.me> <D4D9A7A0.942AC%usenet@gallopinginsanity.com> <o91mia$9q2$1@dont-email.me> |
On 2/27/17, 10:12 AM, in article o91mia$9q2$1@dont-email.me, "Alrescha" <alrescha@gmail.com> wrote: > On 2017-02-27 16:53:36 +0000, Snit <usenet@gallopinginsanity.com> said: > >> Can you understand why most people in most case would NOT want to have >> the risk of having different files with the exact same names in the >> same folder (other than case)? > > Oh of course. I imagine that I could come up with several > well-reasoned arguments as to why one might prefer a case-insensitive > filesystem. I would be curious to hear these from you. > Unfortunately, what has been presented here is > echo-chamber dogma, straw-men, and red-herrings. I think part of the challenge is that this is largely intuitive... for both sides. I know in the past I have done research into what studies and experts think and not found much. I will say in three decades of working with users of all levels (from engineers to lawyers to K-12 to college to corporate to octogenarian newbies and more) I have never run into an occasion where someone has stated or demonstrated a need to have "myfile" and "MyFile" or "MYFILE" in the same folder. In my research I did find a fair amount on the similar question of case sensitivity in variable names. I am NOT a programmer and have little direct experience in this, but I do know a number of programmers and have discussed it with them. They and the research back the idea that having two variables with the same name (other than case) is generally a bad idea... and leads to lots of problems. Even having two variables with names that, when spoken, sound alike leads to issues (even when not being read out loud... when we read things to ourselves we "hear" it in our heads). I posted a quick summary of that research recently and, if you like, could likely dig up the old links and the like (though some may very well be dead by now). -- 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