XPost: comp.sys.mac.systems

"The selected source cannot be used for migration. This source is not
using a Case Sensitive filesystem, while your Mac system is."

Both Time Machines were encrypted and backed up recently with Mac OS X v10.8.5/Mountain Lion.

15" early-2008 MBP was just formatted and installed with a brand new El
Capitan v10.11.(5&6).

From what I read this is normal, but a pain to fix (e.g., reformat the
drive into the correct file system). Am I correct? :(

Thank you in advance. :)
--
"When I was five years old, I saw an insect that had been eaten by ants
and of which nothing remained except the shell. Through the holes in its anatomy one could see the sky. Every time I wish to attain purity I look
at the sky through flesh." --Salvadore Dali
Note: A fixed width font (Courier, Monospace, etc.) is required to see
this signature correctly.
/\___/\ Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / If crediting, then use Ant nickname and AQFL URL/link.
( ) Axe ANT from its address if e-mailing privately.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: comp.sys.mac.systems

Ant <ant@zimage.comANT> wrote:

"The selected source cannot be used for migration. This source is not
using a Case Sensitive filesystem, while your Mac system is."

Both Time Machines were encrypted and backed up recently with Mac OS X v10.8.5/Mountain Lion.

15" early-2008 MBP was just formatted and installed with a brand new El Capitan v10.11.(5&6).

From what I read this is normal

The problem is mostly explained by the error message, but the situation
which led to it is not "normal".

For some reason, you chose to format your drive as "Mac OS Extended
(Case Sensitive, Journaled)", then installed OS X El Capitan on it.

The Case Sensitive variant is NOT the normal choice. The vast majority
of Macs are using "Mac OS Extended (Journaled)", i.e. HFS+ with
journaling enabled, but not case sensitve (it does preserve case, like
Windows file systems).

The only reason to choose the Case Sensitive option is if you have some
obscure software (probably originating on other Unix or Linux systems)
which does not work properly unless the file system is case sensitive.

There are some Mac applications which don't work properly on case
sensitive file systems, e.g. some versions of Adobe Creative Suite (if I remember right, this is due to inconsistent case in filenames which are supposed to refer to the same file installed as part of the suite).

It appears that migration is one situation where you can't mix
case-sensitive and case-insensitive file systems. The problem is obvious
if the source was case sensitive and the destination not, because there
might be files on the source which map to the same name on the
destination; the other way around is less obviously a problem but Apple probably had a good reason to disallow it.

, but a pain to fix (e.g., reformat the
drive into the correct file system). Am I correct? :(

Yes. You can't do an on-the-fly conversion between case-sentive and non-case-senstive variants of HFS+.

Thank you in advance. :)

--
David Empson
dempson@actrix.gen.nz

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: comp.sys.mac.systems

In message <jZmdnTk7M8hA1SzFnZ2dnUU7-TXNnZ2d@earthlink.com> Ant <ant@zimage.comANT> wrote:

"The selected source cannot be used for migration. This source is not
using a Case Sensitive filesystem, while your Mac system is."

Of course not. You must match the drive's case sensitivity.

Both Time Machines were encrypted and backed up recently with Mac OS X v10.8.5/Mountain Lion.

15" early-2008 MBP was just formatted and installed with a brand new El Capitan v10.11.(5&6).

From what I read this is normal, but a pain to fix (e.g., reformat the
drive into the correct file system). Am I correct? :(

Using a case-sensitive file system on a Mac is foolish.

--
NON-FLAMMABLE IS NOT A CHALLENGE Bart chalkboard Ep. BABF13

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: comp.sys.mac.systems

In message <1n20y9f.dbw0cx1p98fevN%dempson@actrix.gen.nz> David Empson <dempson@actrix.gen.nz> wrote:

Ant <ant@zimage.comANT> wrote:

"The selected source cannot be used for migration. This source is not
using a Case Sensitive filesystem, while your Mac system is."

Both Time Machines were encrypted and backed up recently with Mac OS X
v10.8.5/Mountain Lion.

15" early-2008 MBP was just formatted and installed with a brand new El
Capitan v10.11.(5&6).

From what I read this is normal

The problem is mostly explained by the error message, but the situation
which led to it is not "normal".

For some reason, you chose to format your drive as "Mac OS Extended
(Case Sensitive, Journaled)", then installed OS X El Capitan on it.

The Case Sensitive variant is NOT the normal choice. The vast majority
of Macs are using "Mac OS Extended (Journaled)", i.e. HFS+ with
journaling enabled, but not case sensitve (it does preserve case, like Windows file systems).

The only reason to choose the Case Sensitive option is if you have some obscure software (probably originating on other Unix or Linux systems)
which does not work properly unless the file system is case sensitive.

AND you are never planning on using any of the numerous software
packages for the Mac that have never worked properly on a case-sensitive
file system.

There are some Mac applications which don't work properly on case
sensitive file systems, e.g. some versions of Adobe Creative Suite (if I remember right, this is due to inconsistent case in filenames which are supposed to refer to the same file installed as part of the suite).

There are many, and I think no version of Adobe CS works on a
case-sensitive file system as I just heard someone talking about this
within the last month.

As I recall, Steam also does not work and neither does World of
Warcraft, though that information might be old.

Ah, at least for Blizzard that is correct. The requirements for the
latest expansion list for Mac OS X

"Note: FileVault options and case-sensitive formatted volumes are not
supported for installation of Blizzard games."

Not sure what "FileVault options" means.

In other news, someone has managed to boot 10.12 on a APFS volume.

--
The hippo of recollection stirred in the muddy waters of the mind.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: comp.sys.mac.systems

On 2/25/2017 6:00 AM, Lewis wrote:

In message <jZmdnTk7M8hA1SzFnZ2dnUU7-TXNnZ2d@earthlink.com> Ant <ant@zimage.comANT> wrote:

"The selected source cannot be used for migration. This source is not
using a Case Sensitive filesystem, while your Mac system is."

Of course not. You must match the drive's case sensitivity.

Both Time Machines were encrypted and backed up recently with Mac OS X
v10.8.5/Mountain Lion.

15" early-2008 MBP was just formatted and installed with a brand new El
Capitan v10.11.(5&6).

From what I read this is normal, but a pain to fix (e.g., reformat the
drive into the correct file system). Am I correct? :(

Using a case-sensitive file system on a Mac is foolish.

Even with UNIX and Linux engine? I always used case sensitive filenames
in them. Oh well, time to redo this old 2008 MBP. At least I am
practicing and learning at the same time. :/
--
"For every 1 person on earth there are 1 million ants." --Factoid for
the video of Adam Ant's "Goody Two Shoes" Pop Up Video
Note: A fixed width font (Courier, Monospace, etc.) is required to see
this signature correctly.
/\___/\ Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / If crediting, then use Ant nickname and AQFL URL/link.
( ) Axe ANT from its address if e-mailing privately.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: comp.sys.mac.systems

On 2/25/2017 6:13 AM, Lewis wrote:

There are some Mac applications which don't work properly on case
sensitive file systems, e.g. some versions of Adobe Creative Suite (if I
remember right, this is due to inconsistent case in filenames which are
supposed to refer to the same file installed as part of the suite).

There are many, and I think no version of Adobe CS works on a
case-sensitive file system as I just heard someone talking about this
within the last month.

As I recall, Steam also does not work and neither does World of
Warcraft, though that information might be old.

Ah, at least for Blizzard that is correct. The requirements for the
latest expansion list for Mac OS X

"Note: FileVault options and case-sensitive formatted volumes are not supported for installation of Blizzard games."

Not sure what "FileVault options" means.

In other news, someone has managed to boot 10.12 on a APFS volume.

Wow, that is crazy. I wonder if that is why I couldn't install 2008 Mac
Office into it. Yeah, that is weird for FileVault not to be supported. I
wonder what other limitations there are with Macs.
--
"In a battle between elephants, the ants get squashed." --Thailand
Note: A fixed width font (Courier, Monospace, etc.) is required to see
this signature correctly.
/\___/\ Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / If crediting, then use Ant nickname and AQFL URL/link.
( ) Axe ANT from its address if e-mailing privately.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: comp.sys.mac.systems

On 2017-02-25, Ant <ant@zimage.comANT> wrote:

On 2/25/2017 6:00 AM, Lewis wrote:

In message <jZmdnTk7M8hA1SzFnZ2dnUU7-TXNnZ2d@earthlink.com> Ant <ant@zimage.comANT> wrote:

"The selected source cannot be used for migration. This source is not
using a Case Sensitive filesystem, while your Mac system is."

Of course not. You must match the drive's case sensitivity.

Both Time Machines were encrypted and backed up recently with Mac OS X
v10.8.5/Mountain Lion.

15" early-2008 MBP was just formatted and installed with a brand new El
Capitan v10.11.(5&6).

From what I read this is normal, but a pain to fix (e.g., reformat the
drive into the correct file system). Am I correct? :(

Using a case-sensitive file system on a Mac is foolish.

Even with UNIX and Linux engine?

What exactly do you think macOS is, if not a UNIX operating system? : D

I always used case sensitive filenames in them.

Not on Macs you didn't. Don't do that.

Oh well, time to redo this old 2008 MBP. At least I am
practicing and learning at the same time. :/

That you actually charge people for Mac support is rather scary. : /

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: comp.sys.mac.systems

On 2017-02-25, Ant <ant@zimage.comANT> wrote:

On 2/25/2017 6:13 AM, Lewis wrote:

There are some Mac applications which don't work properly on case
sensitive file systems, e.g. some versions of Adobe Creative Suite (if I >>> remember right, this is due to inconsistent case in filenames which are
supposed to refer to the same file installed as part of the suite).

There are many, and I think no version of Adobe CS works on a
case-sensitive file system as I just heard someone talking about this
within the last month.

As I recall, Steam also does not work and neither does World of
Warcraft, though that information might be old.

Ah, at least for Blizzard that is correct. The requirements for the
latest expansion list for Mac OS X

"Note: FileVault options and case-sensitive formatted volumes are not
supported for installation of Blizzard games."

Not sure what "FileVault options" means.

In other news, someone has managed to boot 10.12 on a APFS volume.

Wow, that is crazy. I wonder if that is why I couldn't install 2008 Mac Office into it. Yeah, that is weird for FileVault not to be supported. I wonder what other limitations there are with Macs.

The default file system on Macs has *always* been case insensitive.
While there is an *option* to format a Mac volume with case sensitivity,
it's *not* recommended, because poorly-written software often has
problems operating correctly on case sensitive files systems. That's not
the fault of macOS - it's squarely the fault of the software developers
who wrote the malfunctioning applications.

Bottom line: Unless you have a *very* *specific* *reason* to format a
Mac volume as case sensitive, you should *not* do it.

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: comp.sys.mac.systems

On 2/25/2017 10:16 AM, Jolly Roger wrote:
...

Oh well, time to redo this old 2008 MBP. At least I am
practicing and learning at the same time. :/

That you actually charge people for Mac support is rather scary. : /

I am doing it for free.
--
"It's kind of an insane case ... 6,000 ants dressed up as rice and
robbed a Chinese restaurant." --Steven Wright
Note: A fixed width font (Courier, Monospace, etc.) is required to see
this signature correctly.
/\___/\ Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / If crediting, then use Ant nickname and AQFL URL/link.
( ) Axe ANT from its address if e-mailing privately.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: comp.sys.mac.systems

In article <SuidncYhSMsQcizFnZ2dnUU7-cmdnZ2d@earthlink.com>, Ant <ant@zimage.comANT> wrote:

This very old MBP is just for testing and practice too for the future.
I'm repeating what I did yesterday, but with the correct El Capitan installer's version and encrypted journal HFS+ (no case sensitive).

you do *not* want an encrypted format on a 2008 mac because there is no hardware support for encryption, which means there will be a rather
significant speed hit for all disk i/o.

looks like you get to reformat it one more time.

For some reason, my install is stuck with a second left. Hmm.

the time estimates are never correct.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: comp.sys.mac.systems

Ant <ant@zimage.comANT> wrote:

On 2/25/2017 10:16 AM, Jolly Roger wrote:
...

Oh well, time to redo this old 2008 MBP. At least I am
practicing and learning at the same time. :/

That you actually charge people for Mac support is rather scary. : /

I am doing it for free.

Good, but still scary! : /

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

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: comp.sys.mac.systems

On 2/25/2017 12:43 PM, Jolly Roger wrote:

Ant <ant@zimage.comANT> wrote:

On 2/25/2017 10:16 AM, Jolly Roger wrote:
...

Oh well, time to redo this old 2008 MBP. At least I am
practicing and learning at the same time. :/

That you actually charge people for Mac support is rather scary. : /

I am doing it for free.

Good, but still scary! : /

This very old MBP is just for testing and practice too for the future.
I'm repeating what I did yesterday, but with the correct El Capitan
installer's version and encrypted journal HFS+ (no case sensitive).

For some reason, my install is stuck with a second left. Hmm.
--
"Look at them, fighting like ants. The fate's waiting them." --Kane in
Command & Conquer 3: Tiberium Wars
Note: A fixed width font (Courier, Monospace, etc.) is required to see
this signature correctly.
/\___/\ Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / If crediting, then use Ant nickname and AQFL URL/link.
( ) Axe ANT from its address if e-mailing privately.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: comp.sys.mac.systems

Lewis <g.kreme@gmail.com.dontsendmecopies> wrote:

In message <1n20y9f.dbw0cx1p98fevN%dempson@actrix.gen.nz> David Empson <dempson@actrix.gen.nz> wrote:

There are some Mac applications which don't work properly on case
sensitive file systems, e.g. some versions of Adobe Creative Suite (if I remember right, this is due to inconsistent case in filenames which are supposed to refer to the same file installed as part of the suite).

There are many, and I think no version of Adobe CS works on a
case-sensitive file system as I just heard someone talking about this
within the last month.

Ah, so it wasn't something they bothered fixing then. Just goes to show
the lack of demand for compatibility testing with case sensitive file
systems.

As I recall, Steam also does not work and neither does World of
Warcraft, though that information might be old.

Ah, at least for Blizzard that is correct. The requirements for the
latest expansion list for Mac OS X

"Note: FileVault options and case-sensitive formatted volumes are not supported for installation of Blizzard games."

Not sure what "FileVault options" means.

I've had FileVault 2 (full disk encryption) enabled for a while, and
StarCraft 2 continued to work fine afer I enabled FileVault.

I have no experience with original FileVault (home folder in an
encrypted disk image) and Blizzard games, and my other Blizzard games
are old enough to not work after Snow Leopard.

In other news, someone has managed to boot 10.12 on a APFS volume.

Sweet. Despite iOS 10.3 switching to APFS, I'm inclined to think Apple
is holding back mainstream use of APFS on macOS until the next major
version in September. There will be more complex bits to test, e.g. Time Machine support. It would be nice to see feature improvements in the pre-release APFS before then.

--
David Empson
dempson@actrix.gen.nz

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: comp.sys.mac.systems

On 2/25/2017 1:00 PM, nospam wrote:

In article <SuidncYhSMsQcizFnZ2dnUU7-cmdnZ2d@earthlink.com>, Ant <ant@zimage.comANT> wrote:

This very old MBP is just for testing and practice too for the future.
I'm repeating what I did yesterday, but with the correct El Capitan
installer's version and encrypted journal HFS+ (no case sensitive).

you do *not* want an encrypted format on a 2008 mac because there is no hardware support for encryption, which means there will be a rather significant speed hit for all disk i/o.

looks like you get to reformat it one more time.

Really? Dang it.

For some reason, my install is stuck with a second left. Hmm.

the time estimates are never correct.

This one was WAY off. Haha.
--
"It is not enough to be industrious; so are the ants. What are you
industrious about?" --Henry David Thoreau
Note: A fixed width font (Courier, Monospace, etc.) is required to see
this signature correctly.
/\___/\ Ant(Dude) @ http://antfarm.ma.cx (Personal Web Site)
/ /\ /\ \ Ant's Quality Foraged Links: http://aqfl.net
| |o o| |
\ _ / If crediting, then use Ant nickname and AQFL URL/link.
( ) Axe ANT from its address if e-mailing privately.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: comp.sys.mac.systems

Ant <ant@zimage.comANT> wrote:

On 2/25/2017 1:00 PM, nospam wrote:

In article <SuidncYhSMsQcizFnZ2dnUU7-cmdnZ2d@earthlink.com>, Ant <ant@zimage.comANT> wrote:

This very old MBP is just for testing and practice too for the future.
I'm repeating what I did yesterday, but with the correct El Capitan
installer's version and encrypted journal HFS+ (no case sensitive).

you do *not* want an encrypted format on a 2008 mac because there is no hardware support for encryption, which means there will be a rather significant speed hit for all disk i/o.

looks like you get to reformat it one more time.

Really? Dang it.

Not really. First, test the performance yourself and decide whether it
is a problem.

Second, you can turn off encryption without having to wipe and reinstall everything.

For a manually encrypted drive (as in this case): in Finder, Ctrl-click
on the drive icon and choose the Decrypt command.

For a FileVault-encrypted drive: System Prefrences > Security & Privacy

FileVault > Turn Off FileVault (after authenticating with your admin

account).

In either case, you can only decrypt the drive once encryption has
finished. Both encryption and decryption take place in the background,
working their way through the entire volume while allowing normal
operation of the computer. (There is a moving mark on the disk, with
encrypted data on one side and unencrypted data on the other; the OS automatically takes care of using the appropriate method as data is read
or written on either side of the progress mark.)

--
David Empson
dempson@actrix.gen.nz

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: comp.sys.mac.systems

In message <wsSdnSCkGbmuVSzFnZ2dnUU7-fPNnZ2d@earthlink.com> Ant <ant@zimage.comANT> wrote:

On 2/25/2017 6:00 AM, Lewis wrote:

In message <jZmdnTk7M8hA1SzFnZ2dnUU7-TXNnZ2d@earthlink.com> Ant <ant@zimage.comANT> wrote:

"The selected source cannot be used for migration. This source is not
using a Case Sensitive filesystem, while your Mac system is."

Of course not. You must match the drive's case sensitivity.

Both Time Machines were encrypted and backed up recently with Mac OS X
v10.8.5/Mountain Lion.

15" early-2008 MBP was just formatted and installed with a brand new El
Capitan v10.11.(5&6).

From what I read this is normal, but a pain to fix (e.g., reformat the
drive into the correct file system). Am I correct? :(

Using a case-sensitive file system on a Mac is foolish.

Even with UNIX and Linux engine?

With Unix? macOS (neé OS X) is Unix. Using a case-sensitive file system
on a Mac is foolish.


--

<http://xkcd.com/241/>
<http://xkcd.com/304/>
<http://xkcd.com/635/>
<=-

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: comp.sys.mac.systems

In message <1n229fg.1uznobo1h0rjljN%dempson@actrix.gen.nz> David Empson <dempson@actrix.gen.nz> wrote:

Ant <ant@zimage.comANT> wrote:

On 2/25/2017 1:00 PM, nospam wrote:

In article <SuidncYhSMsQcizFnZ2dnUU7-cmdnZ2d@earthlink.com>, Ant
<ant@zimage.comANT> wrote:

This very old MBP is just for testing and practice too for the future.
I'm repeating what I did yesterday, but with the correct El Capitan
installer's version and encrypted journal HFS+ (no case sensitive).

you do *not* want an encrypted format on a 2008 mac because there is no
hardware support for encryption, which means there will be a rather
significant speed hit for all disk i/o.

looks like you get to reformat it one more time.

Really? Dang it.

Not really. First, test the performance yourself and decide whether it
is a problem.

I have to agree with nospam on this one, having run an encrypted
filesystem on a 2008 MacBook. It is not fun. At all.

It's not really that the machine is dog slow, it's just that it's slow
and it bogs down a lot. and it just feels lethargic.

My 2012 MBP is encrypted. Not detectable, at all.

Second, you can turn off encryption without having to wipe and reinstall everything.

True, but that will take days and reformatting it and reinstalling will
take an hour or two.


--
Beautiful dawn / Lights up the shore for me / There is nothing else in the world I'd rather see with you.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: comp.sys.mac.systems

In message <1n21ve2.h3tnna12sxiw3N%dempson@actrix.gen.nz> David Empson <dempson@actrix.gen.nz> wrote:

Lewis <g.kreme@gmail.com.dontsendmecopies> wrote:

"Note: FileVault options and case-sensitive formatted volumes are not
supported for installation of Blizzard games."

Not sure what "FileVault options" means.

I've had FileVault 2 (full disk encryption) enabled for a while, and StarCraft 2 continued to work fine afer I enabled FileVault.

Yes, same with me with all the other Blizzard games. Also, there is no
way that I know of for an application to know the disk is encrypted
without actually checking diskutil for the disk type.

And the phrasing is odd. So no idea what they mean.

I have no experience with original FileVault (home folder in an
encrypted disk image) and Blizzard games, and my other Blizzard games
are old enough to not work after Snow Leopard.

I tried the original FileVault once just to try it. It was pretty
terrible.

In other news, someone has managed to boot 10.12 on a APFS volume.

Sweet. Despite iOS 10.3 switching to APFS, I'm inclined to think Apple
is holding back mainstream use of APFS on macOS until the next major
version in September. There will be more complex bits to test, e.g. Time Machine support. It would be nice to see feature improvements in the pre-release APFS before then.

APFS seems to be coming along quite well (from what I hear from others,
I've not played with it at all so far). I will not be surprised to see
it as a bootable option in 10.13 and as the default format in 10.14.

--
'I believe you find life such a problem because you think there are the
good people and the bad people,' said the man [Vetinari]. 'You are
wrong, of course. There are, always and only, the bad people, but some
of them are on opposite sides.'

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)