Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.sys.mac.system > #101286
| From | Alan Baker <alangbaker@telus.net> |
|---|---|
| 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 12:12 -0800 |
| Organization | Datemas.de http://www.news.datemas.de |
| Message-ID | <o8vcsb$q0s$1@news.datemas.de> (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 2017-02-26 11:50 AM, Alrescha 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). No, no. You miss the point. You suggested it was a good and useful thing to distinguish between two object which differ from each other in VERSION, but the fact that you can use different CAPITALIZATION for their respective names. That puts the onus on YOU to remember which capitalization represents which version; something which is not innately represented by your scheme. > > 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. I've heard no one make the suggestions you just outlined, sorry.
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