The usual dumbass Migration Assistant Question

[Alan Browne]

New iMac should be here tomorrow. Probably won't have time to do much
with it until next week.

My plan is to migrate-assist only apps and transfer user data in the BG
when up and running. That's the huge bulk of the machine in any case
and there is cruft I'd probably leave behind. That would get me my apps
quickly while leaving user data for a more leisurely transfer via the
ethernet network (and available if needed via same) while I fool around,
er, carefully explore the new machine. Comments?

- What happens to licensed s/w such as Photoshop? Do I have to
de-authorize on the source and authorize on target?


--
"Political correctness is a doctrine, fostered by a delusional,
illogical minority, and rapidly promoted by mainstream media,
which holds forth the proposition that it is entirely possible
to pick up a piece of shit by the clean end."
-Unknown

[Király]

Alan Browne <alan....@freelunchvideotron.ca> wrote:
> My plan is to migrate-assist only apps and transfer user data in the BG
> when up and running. That's the huge bulk of the machine in any case
> and there is cruft I'd probably leave behind. That would get me my apps
> quickly while leaving user data for a more leisurely transfer via the
> ethernet network (and available if needed via same) while I fool around,
> er, carefully explore the new machine. Comments?

I wouldn't do that. You'll be going about it the hard way. Setting up a
fresh user account on the new system and then trying to migrate all your
data over to it from an old system can be a real PITA. Don't use
Migration Assistant at all. Use Setup Assistant, which will grab
everything from your old system right from the beginning. If you then
have stuff on the new machine you don't want, delete it.

--
K.

Lang may your lum reek.

[nospam]

In article <PdCdnf7sI9icsdnP...@giganews.com>, Alan Browne

<alan....@FreelunchVideotron.ca> wrote:

> New iMac should be here tomorrow. Probably won't have time to do much
> with it until next week.
>
> My plan is to migrate-assist only apps and transfer user data in the BG
> when up and running. That's the huge bulk of the machine in any case
> and there is cruft I'd probably leave behind. That would get me my apps
> quickly while leaving user data for a more leisurely transfer via the
> ethernet network (and available if needed via same) while I fool around,
> er, carefully explore the new machine. Comments?

migrate during initial setup. otherwise you're asking for problems.
delete whatever you don't want afterwards.

> - What happens to licensed s/w such as Photoshop? Do I have to
> de-authorize on the source and authorize on target?

deauthorize on the old mac, migrate, reauthorize on the new mac.

[Savageduck]

On 2013-09-26 06:53:09 -0700, Lewis <g.k...@gmail.com.dontsendmecopies> said:

> In message <PdCdnf7sI9icsdnP...@giganews.com>

> Alan Browne <alan....@FreelunchVideotron.ca> wrote:
>
>> New iMac should be here tomorrow. Probably won't have time to do much
>> with it until next week.
>
>> My plan is to migrate-assist only apps and transfer user data in the BG
>> when up and running.
>

> That is not a good idea. If you don't want to copy all the user
> settings, then I would setup the new machine without any migration
> assistant use, copy the apps from the old machine, and start over.

>
>> - What happens to licensed s/w such as Photoshop? Do I have to
>> de-authorize on the source and authorize on target?
>

> Knowing Adobe, this will be 1) a huge pain in the ass 2) will fuck up no
> matter what you do 3) will involve hours on the phone with Adobe.
>
> You're ONLY hope for it working is to do a full migration assistant
> install, but I have no confidence Adobe will have gone to great lengths
> to ensure that doesn't work.

Adobe Photoshop migration is simple. First, their license permits
installation on two machines, even with the new CC, usually a desktop &
a laptop, but there is nothing stopping installation on two desktops or
two laptops.

If I remember correctly Alan already has CS5 or CS6 installed on an
iMac and a MBA. So, the procedure on the iMac being upgraded is to open
Photoshop and go to "Help"-> "Deactivate" and follow the dialog.
Only then install CS(x) on the new iMac.

If, as in my case, you have a Photoshop upgrade trail, and have more
than one version of Photoshop installed on the old machine, there is
nothing stopping you from deactivating the latest version on the old
machine and continuing to use the earlier PS version on an older
machine. On this iMac I have both PS CS5 (an upgrade from CS3) & PS
CS6. When the time comes to get a new iMac, and if I keep this one, and
I haven't moved to the CC program, PS CS5 will remain.

With my various iMacs, a "white" iBook, a G4 PowerBookPro, and an MBP.
I have some level of Photoshop, from CS2 to CS6 running on 5 Apple
computers of various vintage.

--
Regards,

Savageduck

[JF Mezei]

On 13-09-26 08:43, Alan Browne wrote:

> My plan is to migrate-assist only apps and transfer user data in the BG
> when up and running.

If that is the case, make sure yoiur new user account on the new machine
has the same GUID UUID as on the old machine. In unix security, username
doesn't count, its the numbers behind it.

What you did not mention is whether the new machine will have same OS
version or not.

Also, will the two machines be hardwired together for the initial
transfer and then ethernet for rest, or will it be ethernet for both ?

With regards to Photoshop:

There is stuff spread around the system that may not be caught by
migration assistant. For instance in /Library/Preferences, there is a
"Flexnet" directiory which contains the authorisations for your various
adobe packages.

So after migration assistant has done its job, you can go through the
new /Library to make sure it caught everything adobe related.

If you re-install from scratch, you lose your preferences and default to
the garish look by default.

> - What happens to licensed s/w such as Photoshop? Do I have to
> de-authorize on the source and authorize on target?

Since Adobe no longer sells licensed software, there is not much point
in going out of your way to manage your licenses. Just copy the software.

[nospam]

In article <5244905a$0$9753$c3e8da3$aae7...@news.astraweb.com>, JF

Mezei <jfmezei...@vaxination.ca> wrote:

> > My plan is to migrate-assist only apps and transfer user data in the BG
> > when up and running.
>
> If that is the case, make sure yoiur new user account on the new machine
> has the same GUID UUID as on the old machine. In unix security, username
> doesn't count, its the numbers behind it.

that's why it's best to migrate at initial setup, not later.

> What you did not mention is whether the new machine will have same OS
> version or not.

it will probably be a version of 10.8.5 for that hardware.

> Also, will the two machines be hardwired together for the initial
> transfer and then ethernet for rest, or will it be ethernet for both ?

firewire target mode or fw800/usb3 to a time machine or clone is the
best.

> With regards to Photoshop:
>
> There is stuff spread around the system that may not be caught by
> migration assistant. For instance in /Library/Preferences, there is a
> "Flexnet" directiory which contains the authorisations for your various
> adobe packages.

it works just fine with photoshop.

> > - What happens to licensed s/w such as Photoshop? Do I have to
> > de-authorize on the source and authorize on target?
>
> Since Adobe no longer sells licensed software, there is not much point
> in going out of your way to manage your licenses. Just copy the software.

adobe absolutely does still sell licensed software.

[JF Mezei]

On 13-09-26 15:59, nospam wrote:

> adobe absolutely does still sell licensed software.

Did it change its mind to go to a subscription-only sales model ?

[nospam]

In article <52449454$0$16995$c3e8da3$40d4...@news.astraweb.com>, JF

Mezei <jfmezei...@vaxination.ca> wrote:

> > adobe absolutely does still sell licensed software.
>
> Did it change its mind to go to a subscription-only sales model ?

creative cloud is subscription based.

creative suite 6 is still available as a full purchase, no subscription.

there are also other apps, such as photoshop elements, which are only
full purchase.

[Savageduck]

Of the software currently available Adobe's "Creative Cloud", you can
still buy Photoshop CS6 and updates to PS CS6 from CS5, Lightroom 5 and
updates to Lightroom 5.

I bought my CS5 to CS6 update after the implementation of the CC.

--
Regards,

Savageduck

[Alan Browne]

I don't agree that migrating data is a real PITA - it's just moving
files that would get moved one way or the other.

You do point out the detail I forgot about: Setup Assistant v. Migration
assistant.

But, per this page: http://pondini.org/OSX/SetupLion.html
the default folders (Documents, Pictures, etc.) will be transferred
whether I want them to or not using "Setup Asst.". That is not
preferable to me as I'll lose the machines during transfer (Pictures
alone has close to half a TB in it as I save all my raw photo files).

--
"Political correctness is a doctrine, fostered by a delusional,
illogical minority, and rapidly promoted by mainstream media,
which holds forth the proposition that it is entirely possible

to pick up a piece of shit by the clean end."
-Unknown

[Alan Browne]

On 2013.09.26 09:53 , Lewis wrote:
> In message <PdCdnf7sI9icsdnP...@giganews.com>
> Alan Browne <alan....@FreelunchVideotron.ca> wrote:
>

>> New iMac should be here tomorrow. Probably won't have time to do much
>> with it until next week.
>
>> My plan is to migrate-assist only apps and transfer user data in the BG
>> when up and running.
>

> That is not a good idea. If you don't want to copy all the user
> settings, then I would setup the new machine without any migration
> assistant use, copy the apps from the old machine, and start over.

It's not the user settings I worry about - it's not having a computer to
use while the greater part of the data transfer (over 0.5 TB) is taking
place. A rough estimate of that is 1.6 - 2.0 hours based on ethernet
speed of 800 Mb/s and disk write speeds for the 2012 iMac reported as
107 MB/s (pretty well matched). Even if I get higher ethernet speeds
the disk won't be able to swallow much more.

I'll be reviewing all the user settings, and using Onyx and/or terminal
to set those that don't have a GUI setting. (Such as being able to see
~/Library, turning off some OS X options that are irritating and so on).

>> - What happens to licensed s/w such as Photoshop? Do I have to
>> de-authorize on the source and authorize on target?
>

> Knowing Adobe, this will be 1) a huge pain in the ass 2) will fuck up no
> matter what you do 3) will involve hours on the phone with Adobe.

At worst I'd reinstall PS from the DMG and do the one update that is
needed for Bridge/DNG converter to load photos from media without hanging.

> You're ONLY hope for it working is to do a full migration assistant
> install, but I have no confidence Adobe will have gone to great lengths
> to ensure that doesn't work.

I'm not quite as pessimistic where Adobe is concerned but I do get where
you're coming from.

[Alan Browne]

On 2013.09.26 10:28 , nospam wrote:
> In article <PdCdnf7sI9icsdnP...@giganews.com>, Alan Browne
> <alan....@FreelunchVideotron.ca> wrote:
>
>> New iMac should be here tomorrow. Probably won't have time to do much
>> with it until next week.
>>
>> My plan is to migrate-assist only apps and transfer user data in the BG
>> when up and running. That's the huge bulk of the machine in any case
>> and there is cruft I'd probably leave behind. That would get me my apps
>> quickly while leaving user data for a more leisurely transfer via the
>> ethernet network (and available if needed via same) while I fool around,
>> er, carefully explore the new machine. Comments?
>
> migrate during initial setup. otherwise you're asking for problems.
> delete whatever you don't want afterwards.

Stinks as a strategy. "What" problems specifically?

>
>> - What happens to licensed s/w such as Photoshop? Do I have to
>> de-authorize on the source and authorize on target?
>
> deauthorize on the old mac, migrate, reauthorize on the new mac.

OK - as I thought.

[Alan Browne]

On 2013.09.26 11:23 , Savageduck wrote:

> Adobe Photoshop migration is simple. First, their license permits
> installation on two machines, even with the new CC, usually a desktop &
> a laptop, but there is nothing stopping installation on two desktops or
> two laptops.
>
> If I remember correctly Alan already has CS5 or CS6 installed on an iMac
> and a MBA.

That's creepy you know. Maybe you shoulda been a cop or sumpin'. |-/

(CS5. For your file).

> Photoshop and go to "Help"-> "Deactivate" and follow the dialog.
> Only then install CS(x) on the new iMac.

My question was not clear enough. I meant more along the lines of "does
Migration (or Setup) assistant transfer the license?" In the end
probably best to follow the Adobe way...

>
> If, as in my case, you have a Photoshop upgrade trail, and have more
> than one version of Photoshop installed on the old machine, there is

I used to keep an old PS 5 available on the old PC (motherboard died)
and under virtual Win on the Mac, but never used it so dumped it a
couple years ago. (Gave the disk to someone long before that).

[nospam]

In article <tYednbrHjNDxA9nP...@giganews.com>, Alan Browne

<alan....@FreelunchVideotron.ca> wrote:

> It's not the user settings I worry about - it's not having a computer to
> use while the greater part of the data transfer (over 0.5 TB) is taking
> place. A rough estimate of that is 1.6 - 2.0 hours based on ethernet
> speed of 800 Mb/s and disk write speeds for the 2012 iMac reported as
> 107 MB/s (pretty well matched). Even if I get higher ethernet speeds
> the disk won't be able to swallow much more.

let it run overnight.

when you wake up it will be ready to go.

[nospam]

In article <tYednbXHjNAbA9nP...@giganews.com>, Alan Browne

<alan....@FreelunchVideotron.ca> wrote:

> > migrate during initial setup. otherwise you're asking for problems.
> > delete whatever you don't want afterwards.
>
> Stinks as a strategy. "What" problems specifically?

migrating afterwards will create a new account with a new uid.

that means you are likely to have permissions issues because of the
mismatch. you can chown it, but that's a pain.

migrating at setup will create your initial account and copy everything
to it, so there won't be a second account at all.

[nospam]

In article <rZednasT59bKAtnP...@giganews.com>, Alan Browne

<alan....@FreelunchVideotron.ca> wrote:

> My question was not clear enough. I meant more along the lines of "does
> Migration (or Setup) assistant transfer the license?" In the end
> probably best to follow the Adobe way...

no, because there's nothing to transfer. it uses a hash of your
hardware to determine what machine it's licensed to.

you should also deauthorize/reauthorize itunes too.

[Alan Browne]

On 2013.09.26 15:51 , JF Mezei wrote:
> On 13-09-26 08:43, Alan Browne wrote:
>
>> My plan is to migrate-assist only apps and transfer user data in the BG
>> when up and running.
>
> If that is the case, make sure yoiur new user account on the new machine
> has the same GUID UUID as on the old machine. In unix security, username
> doesn't count, its the numbers behind it.

This is the sort of thing I was really looking for. Please clarify:

- Setup assistant does this Y / N

- Migration assistant does this Y / N.

- Are my user files (docs, pictures, etc.) on this machine the
"property" of the UUID?

- How would copied files (docs, pictures, music, etc.) be affected if I
simply copied them from the old machine to the new? (Can't see why/how
this could even be an issue).

- does it affect file permissions after the transfer?

>
> What you did not mention is whether the new machine will have same OS
> version or not.

My current iMac is 10.8.5 and I assume the new one will be 10.8.x.

>
> Also, will the two machines be hardwired together for the initial
> transfer and then ethernet for rest, or will it be ethernet for both ?

Ethernet and Ethernet.

>
> With regards to Photoshop:
>
> There is stuff spread around the system that may not be caught by
> migration assistant. For instance in /Library/Preferences, there is a
> "Flexnet" directiory which contains the authorisations for your various
> adobe packages.

There is only one I need to worry about and at worst I can re-authorize
it with the license.

>
> So after migration assistant has done its job, you can go through the
> new /Library to make sure it caught everything adobe related.
>
> If you re-install from scratch, you lose your preferences and default to
> the garish look by default.

Probably my default anyway.

>
>
>> - What happens to licensed s/w such as Photoshop? Do I have to
>> de-authorize on the source and authorize on target?
>
> Since Adobe no longer sells licensed software, there is not much point
> in going out of your way to manage your licenses. Just copy the software.

Without entering the license CS5 will not work 30 days after install.
Having it on more that 2 machines violates the license.

[Your Name]

In article <PYGdnbyk1IMeAdnP...@giganews.com>, Alan Browne
<alan....@FreelunchVideotron.ca> wrote:

> On 2013.09.26 09:14 , Kir�ly wrote:
> > Alan Browne <alan....@freelunchvideotron.ca> wrote:
> >> My plan is to migrate-assist only apps and transfer user data in the BG
> >> when up and running. That's the huge bulk of the machine in any case
> >> and there is cruft I'd probably leave behind. That would get me my apps
> >> quickly while leaving user data for a more leisurely transfer via the
> >> ethernet network (and available if needed via same) while I fool around,
> >> er, carefully explore the new machine. Comments?
> >
> > I wouldn't do that. You'll be going about it the hard way. Setting up a
> > fresh user account on the new system and then trying to migrate all your
> > data over to it from an old system can be a real PITA. Don't use
> > Migration Assistant at all. Use Setup Assistant, which will grab
> > everything from your old system right from the beginning. If you then
> > have stuff on the new machine you don't want, delete it.
>
> I don't agree that migrating data is a real PITA - it's just moving
> files that would get moved one way or the other.
>
> You do point out the detail I forgot about: Setup Assistant v. Migration
> assistant.
>
> But, per this page: http://pondini.org/OSX/SetupLion.html
> the default folders (Documents, Pictures, etc.) will be transferred
> whether I want them to or not using "Setup Asst.". That is not
> preferable to me as I'll lose the machines during transfer (Pictures
> alone has close to half a TB in it as I save all my raw photo files).

Set-up Assisteant transfers the account fully intact with the same
internal Mac OS X user ID.

Migration Assistant requires you to cerate a new account, then transfer
over the old material, at which stage it creates a new account with a
new internal Mac OS X user ID ... which can cause all sorts of annoying
issues.

[Alan Browne]

That's no fun.

[Alan Browne]

On 2013.09.26 17:08 , nospam wrote:

I was afraid of that.

[Alan Browne]

On 2013.09.26 17:08 , nospam wrote:

Yep. On the checklist.

[Your Name]

In article <52449454$0$16995$c3e8da3$40d4...@news.astraweb.com>, JF

Yes and no. Adobe no longer sells software boxes in stores (although no
doubt some stores still have the old boxed versions), but you do still
download a licensed copy of the software to install and pay the monthly
/ annual subscription fee to be able to use it.

[Your Name]

In article <2013092608232677923-savageduck1@REMOVESPAMmecom>,

Savageduck <savageduck1@{REMOVESPAM}me.com> wrote:

> On 2013-09-26 06:53:09 -0700, Lewis <g.k...@gmail.com.dontsendmecopies> said:
>
> > In message <PdCdnf7sI9icsdnP...@giganews.com>
> > Alan Browne <alan....@FreelunchVideotron.ca> wrote:
> >
> >> New iMac should be here tomorrow. Probably won't have time to do much
> >> with it until next week.
> >
> >> My plan is to migrate-assist only apps and transfer user data in the BG
> >> when up and running.
> >
> > That is not a good idea. If you don't want to copy all the user
> > settings, then I would setup the new machine without any migration
> > assistant use, copy the apps from the old machine, and start over.
> >
> >> - What happens to licensed s/w such as Photoshop? Do I have to
> >> de-authorize on the source and authorize on target?
> >
> > Knowing Adobe, this will be 1) a huge pain in the ass 2) will fuck up no
> > matter what you do 3) will involve hours on the phone with Adobe.
> >
> > You're ONLY hope for it working is to do a full migration assistant
> > install, but I have no confidence Adobe will have gone to great lengths
> > to ensure that doesn't work.
>
> Adobe Photoshop migration is simple. First, their license permits
> installation on two machines, even with the new CC, usually a desktop &
> a laptop, but there is nothing stopping installation on two desktops or
> two laptops.

Tehcnically true, but if you not going to still be using the old
computer, then it's best to deactivate it (especially if you're not
going to keep it of course). If the new computer breaks down, then you
may get given a different machine and then you're stuck with no more
activations. If the old computer breaks, then you won't be able to
deactivate it later. Then you've got to try and convince the Adobe Help
Desk that you're not simply trying to pirate it.

[David Empson]

Alan Browne <alan....@FreelunchVideotron.ca> wrote:

> On 2013.09.26 09:14 , Kir�ly wrote:
> > Alan Browne <alan....@freelunchvideotron.ca> wrote:
> >> My plan is to migrate-assist only apps and transfer user data in the BG
> >> when up and running. That's the huge bulk of the machine in any case
> >> and there is cruft I'd probably leave behind. That would get me my apps
> >> quickly while leaving user data for a more leisurely transfer via the
> >> ethernet network (and available if needed via same) while I fool around,
> >> er, carefully explore the new machine. Comments?
> >
> > I wouldn't do that. You'll be going about it the hard way. Setting up a
> > fresh user account on the new system and then trying to migrate all your
> > data over to it from an old system can be a real PITA. Don't use
> > Migration Assistant at all. Use Setup Assistant, which will grab
> > everything from your old system right from the beginning. If you then
> > have stuff on the new machine you don't want, delete it.
>
> I don't agree that migrating data is a real PITA - it's just moving
> files that would get moved one way or the other.
>
> You do point out the detail I forgot about: Setup Assistant v. Migration
> assistant.
>
> But, per this page: http://pondini.org/OSX/SetupLion.html
> the default folders (Documents, Pictures, etc.) will be transferred
> whether I want them to or not using "Setup Asst.". That is not
> preferable to me as I'll lose the machines during transfer (Pictures
> alone has close to half a TB in it as I save all my raw photo files).

Move the folders you don't want to migrate out of your user account home
folder beforehand, and then don't select the "other files and folders"
option.

--
David Empson
dem...@actrix.gen.nz

[Alan Browne]

On 2013.09.26 17:32 , Your Name wrote:

> Tehcnically true, but if you not going to still be using the old
> computer, then it's best to deactivate it (especially if you're not
> going to keep it of course). If the new computer breaks down, then you
> may get given a different machine and then you're stuck with no more
> activations. If the old computer breaks, then you won't be able to
> deactivate it later. Then you've got to try and convince the Adobe Help
> Desk that you're not simply trying to pirate it.

I have CS3 installed on a laptop as well - so I'll be de-authorizing
here and re-auth on the new.

For license issues, Adobe want sworn signed affidavits. At least that
was the case when I transferred my CS3 license from the Windows machine
to the Mac in early 2008. (Had to, get this, "fax" it to them).

Hmm - I could re-install CS3 on the old machine but I suspect that would
be an unlicensed copy as it was the base for which CS5 was installed.

[Alan Browne]

On 2013.09.26 17:49 , David Empson wrote:
> Move the folders you don't want to migrate out of your user account home
> folder beforehand, and then don't select the "other files and folders"
> option.

It's not that I don't want to move them - it's that I want the new
system up and running to play with it asap. I guess I'll have to be
adult about it. Damnit.

--
"Political correctness is a doctrine, fostered by a delusional,
illogical minority, and rapidly promoted by mainstream media,
which holds forth the proposition that it is entirely possible

to pick up a piece of shit by the clean end."
-Unknown

[Savageduck]

That is true for the Creative Cloud Suite applications, but not for
Lightroom (also included in the CC) and CS5 to CS6 upgrades.

My PS CS6 upgrade was a download as Adobe did not, and would not have a
boxed upgrade to sell me. They have an odd download process, but it
works and if I log in check my Adobe purchase history it is there for
addition downloads if needed.

The biggest hoop I had to jump through was convincing customer service
that I wanted to upgrade from CS5 to CS6, without dealing with the CC
rental plan.


--
Regards,

Savageduck

[bi...@mix.com]

Alan Browne <alan....@freelunchvideotron.ca> writes:

> New iMac should be here tomorrow. Probably won't have time
> to do much with it until next week.

If you'll be using Boot Camp & Windows, read this first -

iMac (late 2013) EFI Update 2.1
http://support.apple.com/kb/DL1684

Billy Y..
--
sub #'9+1 ,r0 ; convert ascii byte
add #9.+1 ,r0 ; to an integer
bcc 20$ ; not a number

[Savageduck]

Correct.

> If the new computer breaks down, then you
> may get given a different machine and then you're stuck with no more
> activations. If the old computer breaks, then you won't be able to
> deactivate it later. Then you've got to try and convince the Adobe Help
> Desk that you're not simply trying to pirate it.

All of my copies of Adobe software are registered, and are on record
behind my Adobe user log in and password. On the one occasion, way back
with CS2 & a PPC Mac, I needed just that assistance after a serious HD
crash, Adobe customer service had me up and running in a few minutes.
Not one question concerning piracy as my credentials were/are good.



--
Regards,

Savageduck

[Alan Browne]

On 2013.09.26 18:51 , bi...@MIX.COM wrote:
> Alan Browne <alan....@freelunchvideotron.ca> writes:
>
>> New iMac should be here tomorrow. Probably won't have time
>> to do much with it until next week.
>
> If you'll be using Boot Camp & Windows, read this first -
>
> iMac (late 2013) EFI Update 2.1
> http://support.apple.com/kb/DL1684

Thx - but I'm buying a late 2012 (refurbished by Apple) and I run
Windows under VMWare Fusion, not bootcamp.

[David Empson]

Alan Browne <alan....@FreelunchVideotron.ca> wrote:

> On 2013.09.26 15:51 , JF Mezei wrote:
> > On 13-09-26 08:43, Alan Browne wrote:
> >
> >> My plan is to migrate-assist only apps and transfer user data in the BG
> >> when up and running.
> >
> > If that is the case, make sure yoiur new user account on the new machine
> > has the same GUID UUID as on the old machine. In unix security, username
> > doesn't count, its the numbers behind it.

I'm not aware of the UUID associated with the account being particularly
important as far as migration of accounts is concerned. It is the Unix
"User ID" of the account which causes complications if it gets changed.

> This is the sort of thing I was really looking for. Please clarify:
>
> - Setup assistant does this Y / N
>
> - Migration assistant does this Y / N.

They have exactly the same logic (and engine) for transferring accounts.

In both cases, if an account already exists on the destination machine
with the same User ID, Migration or Setup Assistant will automatically
assign the next available User ID and adjust file ownership accordingly
while doing the transfer.

The only "special case" is that if you use Setup Assistant to transfer
accounts on initial setup of a new Mac (or a freshly installed OS on a
bare drive), there is no possibility of there being a conflicting User
ID, so it is guaranteed to transfer your account with the same User IDs.

If you set up a new Mac without transferring accounts, Setup Assistant
asks for your details to set up a new account, and that account is
assigned User ID 501. Accounts subsequently created in System
Preferences have User IDs 502, 503, etc.

If your old computer only has one account, it is probably user ID 501.
If you created additional accounts and the one you normally use is not
the one that was created during initial setup, then it will have a
higher user ID and you are less likely to have problems with doing a
migration after initial setup.

You can check the user ID being used by your existing accounts via
System Preferences > Accounts (or Users & Groups). Unlock the padlock,
then Control-click on the account name and choose Advanced Options. This
shows various details like the home folder, user ID, etc. As noted
there, avoid changing anything as you are likely to break something if
you don't know how to do it safely.

There can also be issues with conflicting account names and/or a
conflicting home folder, even if the user IDs differ: Migration/Setup
Assistant will change the account name and adjust the name of the
transferred home folder if necessary (I vaguely recall seeing some
additional options the last time I ran into this).

The user visible long account name doesn't affect migration, doesn't
need to be unique, and can be changed at any time.

> - Are my user files (docs, pictures, etc.) on this machine the
> "property" of the UUID?

They are owned by the User ID. Each User ID is associated with a
particular account name on your system (but could be associated with a
different account name on a different system).

> - How would copied files (docs, pictures, music, etc.) be affected if I
> simply copied them from the old machine to the new? (Can't see why/how
> this could even be an issue).

As long as your accounts have the same user ID on both systems, this
won't be a problem.

If they have different user IDs, then the copy may fail due to
permission errors (or an inability to access the destination or source
folder at all).

> - does it affect file permissions after the transfer?

Not usually, provided the files are owned by the same user ID and there
aren't any ACLs on the destination folders which force changes.

If you copy files belonging to a different user ID, for which you have
read access, then the copies are owned by your user ID.

> > What you did not mention is whether the new machine will have same OS
> > version or not.
>
> My current iMac is 10.8.5 and I assume the new one will be 10.8.x.

Late 2012 iMac must be 10.8.2 or later.

The minor version (e.g. 10.8.2 vs 10.8.5) isn't important for migration,
but you can't migrate from a newer major version to an older one (e.g.
10.8.x to 10.7.x).

--
David Empson
dem...@actrix.gen.nz

[JF Mezei]

On 13-09-26 16:43, Alan Browne wrote:

> whether I want them to or not using "Setup Asst.". That is not
> preferable to me as I'll lose the machines during transfer (Pictures
> alone has close to half a TB in it as I save all my raw photo files).

On old machine, move such large folders in your home directory to
"/Transfer Later" in the disk root directory. This allows the Setup
Assistant to move your account seamlessly, and you can then move the
remainder of files at your leasure.

[Savageduck]

On 2013-09-26 14:55:06 -0700, Alan Browne

<alan....@FreelunchVideotron.ca> said:

> On 2013.09.26 17:32 , Your Name wrote:
>
>> Tehcnically true, but if you not going to still be using the old
>> computer, then it's best to deactivate it (especially if you're not
>> going to keep it of course). If the new computer breaks down, then you
>> may get given a different machine and then you're stuck with no more
>> activations. If the old computer breaks, then you won't be able to
>> deactivate it later. Then you've got to try and convince the Adobe Help
>> Desk that you're not simply trying to pirate it.
>
> I have CS3 installed on a laptop as well - so I'll be de-authorizing
> here and re-auth on the new.
>
> For license issues, Adobe want sworn signed affidavits. At least that
> was the case when I transferred my CS3 license from the Windows machine
> to the Mac in early 2008. (Had to, get this, "fax" it to them).

That is the case when switching operating systems.

> Hmm - I could re-install CS3 on the old machine but I suspect that
> would be an unlicensed copy as it was the base for which CS5 was
> installed.

From what you are saying your CS5 was an upgrade from CS3.
Per the license you have to retain the prior version or have the serial
number available if installing an upgrade on a fresh machine. When I
upgraded from CS3 to CS5 on this iMac when it was new, I had no version
of PS installed. That meant as part of the upgrade install process I
was required to enter the CS3 serial number. When I upgraded to CS6 I
did not have to do this as the prior version was installed.

I currently have CS2 on a "Goose-Neck" iMac & a "White" iBook, CS3 on a
G4 PowerBookPro, CS5 + CS6 on my MBP & this iMac.



--
Regards,

Savageduck

[JF Mezei]

When Adbobe announced its "cloud" buzzword-driven software subscription
offering, it was said that it would "soon" stop selling licences for
CS6. And when I called, the agent said that while no date had been set
for stop-sales, that it was expected to become end-of-sale soon.

But... looking at the Adobe web site I see this now:

##
While Adobe Creative Suite� 6 products will continue to be available for
purchase, Adobe has no plans for future releases of Creative Suite or
other CS products.
##

So it looks likle they got enough complaints to keep the licensed
software up for sale along with subscription versions. My guess is that
within a year, they'll probably review their "no more upgerades"
decision once they realise how much that decision has hurt their revenues.

BTW, when I login to my Adobe account, while it shows the list of Adobe
products I have purchased over the years, (including Page Maker version
1 serial number that had been needed to upgrade from Page Maker to
InDesign), it does not show how many machines the software was activated on.

[nospam]

In article <5244c1d5$0$34966$c3e8da3$4605...@news.astraweb.com>, JF

Mezei <jfmezei...@vaxination.ca> wrote:

> So it looks likle they got enough complaints to keep the licensed
> software up for sale along with subscription versions. My guess is that
> within a year, they'll probably review their "no more upgerades"
> decision once they realise how much that decision has hurt their revenues.

their revenue is not hurting and they aren't going to upgrade cs6.

they may tweak the plan options, such as price, but that's about it.

[Alan Browne]

It is still 501. Admin is 502. Guest is 201 (I don't think I ever ran
that).

Thanks David,

Unless I really misunderstood the UUID bit above, I assume that if the
new account on the new machine is UUID 501 (and that's what should be
created) and the current account on the current machine is also 501 that
all files in:

- Documents
- Music
- Pictures
- Movies
- Dropbox
- Public

can be manually copied after Migration and be usable by the "new" 501
(same permissions)

I assume the non-OS included apps will come with Migration (as I'll
leave that checked)

As to ACL's I could remove them from the old machine before the last
backup I suppose (I have a few folders there (Music, Movies, Dropbox,
Public, iTunes Music)) just to be clean.

This gives me more inclination to setup the account on the new machine
using Migration (for the apps, etc, but not my data) and then pull those
over at leisure. I'd just have to be sure the new Account is 501 before
copying the files.

Can (should) I rename my old machine "AlanMac" to something different first?

Can (shouldn't) I rename my old account "AB" to something different first?

Thanks!

[Alan Browne]

Sounds nice. What happens to the UUID's? (See David E's reply for
context).

[Alan Browne]

On 2013.09.26 19:08 , Savageduck wrote:
> On 2013-09-26 14:55:06 -0700, Alan Browne
> <alan....@FreelunchVideotron.ca> said:
>
>> On 2013.09.26 17:32 , Your Name wrote:
>>
>>> Tehcnically true, but if you not going to still be using the old
>>> computer, then it's best to deactivate it (especially if you're not
>>> going to keep it of course). If the new computer breaks down, then you
>>> may get given a different machine and then you're stuck with no more
>>> activations. If the old computer breaks, then you won't be able to
>>> deactivate it later. Then you've got to try and convince the Adobe Help
>>> Desk that you're not simply trying to pirate it.
>>
>> I have CS3 installed on a laptop as well - so I'll be de-authorizing
>> here and re-auth on the new.
>>
>> For license issues, Adobe want sworn signed affidavits. At least that
>> was the case when I transferred my CS3 license from the Windows
>> machine to the Mac in early 2008. (Had to, get this, "fax" it to them).
>
> That is the case when switching operating systems.

Was just in reply to YN's bit about Adobe piracy paranoia.

>
>> Hmm - I could re-install CS3 on the old machine but I suspect that
>> would be an unlicensed copy as it was the base for which CS5 was
>> installed.
>
> From what you are saying your CS5 was an upgrade from CS3.
> Per the license you have to retain the prior version or have the serial
> number available if installing an upgrade on a fresh machine. When I
> upgraded from CS3 to CS5 on this iMac when it was new, I had no version
> of PS installed. That meant as part of the upgrade install process I was
> required to enter the CS3 serial number. When I upgraded to CS6 I did
> not have to do this as the prior version was installed.

I keep all the old license keys so shouldn't be too much of an issue. I
suspect I may abandon Photoshop in the next 5 years in any case since I
an vehemently opposed to renting s/w by the month that only performs for
5 - 10 hours per month.

[JF Mezei]

On 13-09-26 20:20, Alan Browne wrote:

> Sounds nice. What happens to the UUID's? (See David E's reply for
> context).

When you create the "Transfer later" folder, set its owner to be you As
you copy your documents from inside your home directory to the "transfer
later", they should retain same ownership.

If you have not set any ACLs on files/directories, this should be very
straighforward.

[JF Mezei]

On 13-09-26 20:19, Alan Browne wrote:

> It is still 501. Admin is 502. Guest is 201 (I don't think I ever ran
> that).

As long as the GUID and UUID are the same, this is what counts.

ls -l -n -e of your home directory on old and new machines should
confirm they are the same or different.

( -l is long, -b is for numeric guid and uuid, -e shows ACLs)

> Unless I really misunderstood the UUID bit above, I assume that if the
> new account on the new machine is UUID 501 (and that's what should be
> created) and the current account on the current machine is also 501 that
> all files in:
>
> - Documents
> - Music
> - Pictures
> - Movies
> - Dropbox
> - Public
>
> can be manually copied after Migration and be usable by the "new" 501
> (same permissions)

In real life, correct. But pedantically, there are some caveats. You
also want the group ID to be the same. And ACLs may or may not be copied
depending on how you make the copy across the systems.

What is really frustrating about Finder copies is that if there is a
problem, you don't really know about it and you end up with a partially
opoulated directory and no way to know which file is partially copied in
it. using command line tools is better for such lareg copies since you
have a log of what was copied and why it didn't succeed on the last
file. dd and cp are your friends on that.

You can also try to zip files and copy the zipped file accross. For some
situations, they may save time because the time saved for the copy
operation is greater than time needed for zip/unzip. (or use compressed
.DMGs).

> Can (should) I rename my old machine "AlanMac" to something different first?

Because the rename isn't 100% complete when using the GUI, you are
better off naming yoru newborn with the right name first, and renaming
the older machine before. The old machine will retain a few hints of the
original name, mostly at the command/unix level.

> Can (shouldn't) I rename my old account "AB" to something different first?

Nop. You don't want to do that, and you don't need to do that. When you
use the ew machine to access your old machine via AFP, you authenticate
using the old machine,s credentials. And they can be the same as on your
new machine because they are in fact independent.

[David Empson]

Alan Browne <alan....@FreelunchVideotron.ca> wrote:

> On 2013.09.26 19:01 , David Empson wrote:

[...]

> > If your old computer only has one account, it is probably user ID 501.
>
> It is still 501. Admin is 502. Guest is 201 (I don't think I ever ran
> that).

The guest account has its home folder deleted each time it logs out, so
it isn't important for migration. Normal and admin accounts created by
System Preferences are numbered sequentially starting at 501.

Other methods of creating accounts may use different number ranges, e.g.
Workgroup Manager (for Mac OS X Server) seems to default to using 1001
and up, but you can specify the ID when creating the account.

[...]

> Thanks David,
>
> Unless I really misunderstood the UUID bit above, I assume that if the
> new account on the new machine is UUID 501

"UUID" and "User ID" are different things. The UUID is a Universally
Unique Identifier (basically a random 128-bit number) which is
guaranteed to be unique to all accounts on one system, and has a very
low probability of matching one generated elsewhere.

The "User ID" is a small number (may be limited to 16 bits, might be 32)
which has the same value on all systems for certain system accounts
(e.g. root) and almost always overlaps for user-created accounts on
different systems, but is unique per account within one system.

I don't know how Mac OS X uses the UUID for an account, but it is
visible in the Advanced Options for the account in System Preferences,
and I've been aware of its existence since Leopard (it may have been
introduced when Apple switched from NetInfo in 10.4 and earlier to
Directory Services in 10.5 and later).

> (and that's what should be created) and the current account on the current
> machine is also 501 that all files in:
>
> - Documents
> - Music
> - Pictures
> - Movies
> - Dropbox
> - Public
>
> can be manually copied after Migration and be usable by the "new" 501
> (same permissions)

Public has one issue to watch: the Drop Box in there has unusual
permissions (others can write but not read), and that might be modified
when copying using Finder, but the rest of those folders should be OK.

On further reflection, using Finder to do a manual migration is likely
to NOT preserve unusual permissions: it probably sets up default
permissions on all copied files. I tend to use cloning or command line
tools (as root) for this sort of operation, and they usually preserve
ownership and permissions.

The headache is the Library folder in the home folder on the source
machine. Migration/Setup Assistant knows which bits don't need to be
copied, but is a lot of fiddly work to get it right when copying
manually. You also can't copy some of it while logged in as that user on
the destination machine, because parts of it will be in use while you
are trying to replace them. That basically forces you to log into a
different account and use root privileges to copy the Library folder of
your user account, e.g. with something like ditto from the command line.

There are also likely to be several hidden files and folders in your
home folder, some of which might be important to copy.

Migration takes care of all of this, and gets most of it right. (My main
account has been migrated, upgraded or cloned from 10.2 through each
major OS version up to 10.8, spanning four computers and a few drive
replacements; I've had minor niggles once that I recall, relating to
some low level tweaks I'd done.)

If the downtime needed for migration during initial setup is a concern,
just move the contents of some big folders out of your home folder on
the source machine before doing the migration, and then you can copy
them at your leisure.

In this scenario, I'd recommend leaving the standard Documents, Music,
Pictures, Movies and Public folders where they are: they have special
permissions, which you might break by moving them, and could end up with
slightly incorrect ones created automatically on the new machine. Move
selected content out of those folders to a temporary folder somewhere
outside the home folder.

> I assume the non-OS included apps will come with Migration (as I'll
> leave that checked)

Yes. Migration/Setup Assistant knows not to copy the standard apps, also
which ones to skip that vary between OS versions (not applicable here).

> As to ACL's I could remove them from the old machine before the last
> backup I suppose (I have a few folders there (Music, Movies, Dropbox,
> Public, iTunes Music)) just to be clean.

Mac OS X sets up ACLs on several folders in your home folder, e.g. to
protect you against accidentally deleting Documents and similar folders.
I wouldn't recommend removing all ACLs.

> This gives me more inclination to setup the account on the new machine
> using Migration (for the apps, etc, but not my data) and then pull those
> over at leisure.

> I'd just have to be sure the new Account is 501 before copying the files.
>
> Can (should) I rename my old machine "AlanMac" to something different first?

The computer name must be unique on the network. If you transfer network
settings during setup it may try to copy the name, and end up with a
"(2)" on the end. Up to you whether you fix this before or after.

The computer name is also used in some contexts such as Time Machine. If
you connect the same backup drive to the new machine, TM will ask if you
want to inherit its backups and keep using the same drive, but this
sometimes results in glitches like only being able to see history for
your new machine, even though the older backups are still there. I've
tended to put my old TM backup drives into storage and started a new one
when I've done a switch to a new computer, especially if the old backup
drive was mostly full. My current one is much bigger so I'll probably
continue using it on my next computer upgrade (possibly next month, if I
like the new rMBPs).

> Can (shouldn't) I rename my old account "AB" to something different first?

I don't see any need to fiddle with the account name. Changing the
account name or home folder name is also something that has to be done
carefully or you will break something.

--
David Empson
dem...@actrix.gen.nz

[David Empson]

JF Mezei <jfmezei...@vaxination.ca> wrote:

> On 13-09-26 20:19, Alan Browne wrote:
>
> > It is still 501. Admin is 502. Guest is 201 (I don't think I ever ran
> > that).
>
> As long as the GUID and UUID are the same, this is what counts.

Please don't call them "GUID" and "UUID". That isn't what Apple calls
the fields you are referring to. The correct names are "Group ID" and
"User ID", which are shorted to "gid" and "uid" in some command line
tools (such as 'id').

GUID and UUID have specific meanings ("Globally Unique Identfier" and
"Universally Unique Identifier"). As it happens, accounts on Mac OS X do
have a "UUID", but it is not important for managing account migration,
and is not the same thing as the "User ID".

--
David Empson
dem...@actrix.gen.nz

[JF Mezei]

On 13-09-27 00:31, David Empson wrote:

> Please don't call them "GUID" and "UUID". That isn't what Apple calls
> the fields you are referring to. The correct names are "Group ID" and
> "User ID", which are shorted to "gid" and "uid" in some command line
> tools (such as 'id').

Thanks for reminder. I knew GUID didn't sound right. It is also used to
refer to EFI comptible disk partitions.

[Andreas Rutishauser]

Salut Alan

In article <PdCdnf7sI9icsdnP...@giganews.com>,

Alan Browne <alan....@FreelunchVideotron.ca> wrote:

> New iMac should be here tomorrow. Probably won't have time to do much
> with it until next week.
>

> My plan is to migrate-assist only apps and transfer user data in the BG
> when up and running.

if "BG" means background your idea won't work, as Migration Assistant
will be the only application that is allowed to run on both machines.

> That's the huge bulk of the machine in any case
> and there is cruft I'd probably leave behind. That would get me my apps
> quickly while leaving user data for a more leisurely transfer via the
> ethernet network (and available if needed via same) while I fool around,
> er, carefully explore the new machine. Comments?

I would use Setup Assistant from the very beginning.
I would not use Ethernet, I prefer FireWire (a Thunderbolt to FireWire
Adapter might be needed if you don't have one already) Target Disk mode.

Be aware that with this method you are not tranferring from another Mac,
but from a Volume on this Mac.

>
> - What happens to licensed s/w such as Photoshop? Do I have to
> de-authorize on the source and authorize on target?

Adobe allows installaion on 2 computers afaik, but 1 should be a
portable...

You might also think of iTuned registration, still 5 devices max on the
same Apple ID

Cheers
Andreas

--
MacAndreas Rutishauser, <http://www.MacAndreas.ch>
EDV-Dienstleistungen, Hard- und Software, Internet und Netzwerk
Beratung, Unterstuetzung und Schulung
<mailto:and...@MacAndreas.ch>, Fon: 044 / 721 36 47

[Your Name]

In article <5244c1d5$0$34966$c3e8da3$4605...@news.astraweb.com>, JF
Mezei <jfmezei...@vaxination.ca> wrote:

> When Adbobe announced its "cloud" buzzword-driven software subscription
> offering, it was said that it would "soon" stop selling licences for
> CS6. And when I called, the agent said that while no date had been set
> for stop-sales, that it was expected to become end-of-sale soon.
>
> But... looking at the Adobe web site I see this now:
>
> ##
> While Adobe Creative Suite� 6 products will continue to be available for
> purchase, Adobe has no plans for future releases of Creative Suite or
> other CS products.
> ##
>
> So it looks likle they got enough complaints to keep the licensed
> software up for sale along with subscription versions.

More likely it's simply a case of supporting the boxes still sitting on
reseller shelves.

Technically Adobe had stopped selling it, but I got a boxed copy of
InDesign 2 PageMaker Upgrade extremely cheaply via an auction house
selling off old boxes for a reseller (possibly even the Adobe New
Zealand distributor at that time).

> My guess is that within a year, they'll probably review their "no
> more upgerades" decision once they realise how much that decision
> has hurt their revenues.

If the subscription system fails (which is unlikely unfortunately),
they'll simply start selling boxed copies of whatever the latest
version is at the time, along with the usual upgrade deal from the most
recent version(s).

> BTW, when I login to my Adobe account, while it shows the list of Adobe
> products I have purchased over the years, (including Page Maker version
> 1 serial number that had been needed to upgrade from Page Maker to
> InDesign), it does not show how many machines the software was activated on.

You upgraded from PageMerk *1* to InDesign?!? I would have thought the
upgrade cut-off was Pagemker 7 or maybe strecth to 6, but all the way
back to version 1 seems extremely generous, especially for Adobe.

[JF Mezei]

On 13-09-27 03:08, Your Name wrote:

> You upgraded from PageMerk *1* to InDesign?!?

Page marker preserved the serial number from the first version you
bought. So despite having had the last version of Page Maker, my serial
number dated back to when Page Maker was on 1 diskette. The serial
number would not validate on the software, but Adobe did have it on file
and they had a "trick" to validate the number.

[Savageduck]

On 2013-09-27 00:08:35 -0700, Your Name <Your...@YourISP.com> said:

> In article <5244c1d5$0$34966$c3e8da3$4605...@news.astraweb.com>, JF
> Mezei <jfmezei...@vaxination.ca> wrote:
>
>> When Adbobe announced its "cloud" buzzword-driven software subscription
>> offering, it was said that it would "soon" stop selling licences for
>> CS6. And when I called, the agent said that while no date had been set
>> for stop-sales, that it was expected to become end-of-sale soon.
>>
>> But... looking at the Adobe web site I see this now:
>>
>> ##
>> While Adobe Creative Suite� 6 products will continue to be available for
>> purchase, Adobe has no plans for future releases of Creative Suite or
>> other CS products.
>> ##
>>
>> So it looks likle they got enough complaints to keep the licensed
>> software up for sale along with subscription versions.
>
> More likely it's simply a case of supporting the boxes still sitting on
> reseller shelves.
>
> Technically Adobe had stopped selling it, but I got a boxed copy of
> InDesign 2 PageMaker Upgrade extremely cheaply via an auction house
> selling off old boxes for a reseller (possibly even the Adobe New
> Zealand distributor at that time).

"Adobe New Zealand"?? I don't believe there is an Adobe New Zealand. I
thought that it was Adobe Australia that was gouging most of the
Southern Hemisphere & SE-Asia by bumping the USA price to its customers.


--
Regards,

Savageduck

[Your Name]

In article <2013092707443742612-savageduck1@REMOVESPAMmecom>,

Savageduck <savageduck1@{REMOVESPAM}me.com> wrote:

Adobe products were (still are?) distributed in New Zealand by
Rennaissance, who were also the only official Apple distributor, but
both of those contracts changed a while back now.

[Alan Browne]

I added "remove ACL's" to my pre-transfer checklist.

But in the end I used Setup Assistant - took a little over 5 hours.

[Alan Browne]

On 2013.09.27 02:33 , Andreas Rutishauser wrote:
> Salut Alan
>
> In article <PdCdnf7sI9icsdnP...@giganews.com>,
> Alan Browne <alan....@FreelunchVideotron.ca> wrote:
>
>> New iMac should be here tomorrow. Probably won't have time to do much
>> with it until next week.
>>
>> My plan is to migrate-assist only apps and transfer user data in the BG
>> when up and running.
>
> if "BG" means background your idea won't work, as Migration Assistant
> will be the only application that is allowed to run on both machines.

That meant: Migrate assist w/o transferring the user data files; then
when in the normal environment of OS X on both machines, transfer the
user data while also doing other things on the new computer.

>> That's the huge bulk of the machine in any case
>> and there is cruft I'd probably leave behind. That would get me my apps
>> quickly while leaving user data for a more leisurely transfer via the
>> ethernet network (and available if needed via same) while I fool around,
>> er, carefully explore the new machine. Comments?
>
> I would use Setup Assistant from the very beginning.
> I would not use Ethernet, I prefer FireWire (a Thunderbolt to FireWire
> Adapter might be needed if you don't have one already) Target Disk mode.

I used Ethernet as I don't yet have the Thunderbolt adapter.

> Be aware that with this method you are not tranferring from another Mac,
> but from a Volume on this Mac.

Nice distinctions. Thanks.

In the end I used Setup Assistant.

>>
>> - What happens to licensed s/w such as Photoshop? Do I have to
>> de-authorize on the source and authorize on target?
>
> Adobe allows installaion on 2 computers afaik, but 1 should be a
> portable...

Already done a few years ago. My question was really "will the
authorization follow the migration". Easier though to deauth one and
auth the new one.

>
> You might also think of iTuned registration, still 5 devices max on the
> same Apple ID

Good point - but I'll be abandoning the current iMac so I'd rather keep
the iTunes devmax clean.

[Paul Sture]

In article <V-OdnZOvwqL5JtnP...@giganews.com>,

Alan Browne <alan....@FreelunchVideotron.ca> wrote:

> On 2013.09.26 18:51 , bi...@MIX.COM wrote:
> > Alan Browne <alan....@freelunchvideotron.ca> writes:
> >
> >> New iMac should be here tomorrow. Probably won't have time
> >> to do much with it until next week.
> >
> > If you'll be using Boot Camp & Windows, read this first -
> >
> > iMac (late 2013) EFI Update 2.1
> > http://support.apple.com/kb/DL1684
>
> Thx - but I'm buying a late 2012 (refurbished by Apple) and I run
> Windows under VMWare Fusion, not bootcamp.

Are you aware that you can use VMware Fusion run to Windows from the
Bootcamp partition? It's a best of both worlds thing apparently - run
Windows on its own or as a VM within OS X.

<https://pubs.vmware.com/fusion-4/index.jsp?topic=/com.vmware.fusion.gett
ing_started.doc/fusion_getting_started_print.2.9.html>

--
Paul Sture

[Paul Sture]

In article <5244e8d5$0$50639$c3e8da3$92d0...@news.astraweb.com>,

JF Mezei <jfmezei...@vaxination.ca> wrote:

> On 13-09-26 20:19, Alan Browne wrote:
>
> > It is still 501. Admin is 502. Guest is 201 (I don't think I ever ran
> > that).
>

> ls -l -n -e of your home directory on old and new machines should
> confirm they are the same or different.
>

> ( -l is long, -n is for numeric guid and uuid, -e shows ACLs)

As a quick sanity check:

ls -ln /Users

will give you a list of your users' gid and uid values. Printing this
list out when preparing for a migration provides a useful reference.

If you have external or network volumes containing user data, get a
printout of "ls -ln" of that too. While Migration Assistant and Setup
Assistant can be expected to get the ownership of files in /Users
correct, it is doubtful that it looks at other volumes (and indeed you
wouldn't want it to change the ownership of files on a cloned backup).

> What is really frustrating about Finder copies is that if there is a
> problem, you don't really know about it and you end up with a partially
> opoulated directory and no way to know which file is partially copied in
> it. using command line tools is better for such lareg copies since you
> have a log of what was copied and why it didn't succeed on the last
> file. dd and cp are your friends on that.

Indeed. If you copy by clicking on a folder, that whole folder should be
copied but unless you use something like Tinkertool to reveal hidden and
system files, going into the folder, selecting all files, copying then
pasting elsewhere isn't going to include the hidden and system files.

For example, looking in my home directory, I not only have things like
.bashrc (my bash initialisation file), but .dropbox (containing Dropbox
configuration details), .ssh (my ssh keys), .mysql_history,
.sqlite_history and other useful stuff.

> You can also try to zip files and copy the zipped file accross. For some
> situations, they may save time because the time saved for the copy
> operation is greater than time needed for zip/unzip. (or use compressed
> .DMGs).

I prefer to use tar instead of zip, but that may be due to historical
problems with zip/unzip.

There was (still is?) a problem with Finder's Archive/Unarchive utility
when it came to merging files into an existing directory. I came across
this with (IIRC) the perl distribution where the main source contains a
skeleton /doc hierarchy, and the full documentation comes in a separate
tarball. Using Finder's Unarchive tool, restoring the documentation
tarball would overwrite the /doc hierarchy which came in the source
tarball, and the result wouldn't build.

--
Paul Sture

[Paul Sture]

In article <1l9v0gj.cfgks0197ecj9N%dem...@actrix.gen.nz>,

dem...@actrix.gen.nz (David Empson) wrote:

> Other methods of creating accounts may use different number ranges, e.g.
> Workgroup Manager (for Mac OS X Server) seems to default to using 1001
> and up, but you can specify the ID when creating the account.

Other systems such as Linux have varying allocation schemes too.

For example, an openSUSE instance here assigns all users to group
"users", but a Scientific Linux (a free version of Red Hat) instance
creates a separate group for each user (user Empson gets group Empson).

The numbering schemes are also different. On openSUSE, uids start at
1000 and the "users" gid is 100. On (my instance of) Scientific Linux
uids start at 500 and the gid defaults to the same value as the uid,
though it can get a different value if that gid is already in use when
you create the account.

Where you are planning on using network login credentials to access
files for the same user across systems it shouldn't matter, but if you
want to do things like move disks from one system to another it makes
sense to coordinate the uid and gid pairs across systems.

[...]

>
> The "User ID" is a small number (may be limited to 16 bits, might be 32)
> which has the same value on all systems for certain system accounts
> (e.g. root) and almost always overlaps for user-created accounts on
> different systems, but is unique per account within one system.

My account on a FreeBSD system has a uid of >120,000. I just checked on
my Mountain Lion system and it copes with a value of 68000, so it's 32
bit (or greater).

> I don't know how Mac OS X uses the UUID for an account, but it is
> visible in the Advanced Options for the account in System Preferences,
> and I've been aware of its existence since Leopard (it may have been
> introduced when Apple switched from NetInfo in 10.4 and earlier to
> Directory Services in 10.5 and later).

I notice that the Advanced Options dialogue of Users and Groups has the
option to create a new value for the UUID (but at this time on a Sunday
evening I don't feel brave enough to see what happens).

--
Paul Sture

[Alan Browne]

On 2013.09.29 11:02 , Paul Sture wrote:

> Are you aware that you can use VMware Fusion run to Windows from the
> Bootcamp partition? It's a best of both worlds thing apparently - run
> Windows on its own or as a VM within OS X.

Yes, had the discussion here with, IIRC, JR and a few others. While it
has it merits, what I do in Windows (which isn't often) doesn't require
all that much oomph. Besides managing the backup of the Windows setup
and data is just a matter of dragging the virtual machine over to one of
my external disks. (about 60 GB) for that blob).

[JF Mezei]

Here is a different slant to the original question:

Say I have a Mac with all sorts of tweeks.

Say it is at same OSX version as what a newer machine supports.

Could I not buy a new Mac when it comes out, and litterally clone the
disk of the old MacPro onto the new machine ?

That would fully preserve my environment, no worries about recreating
it, changed user permissions, forgetting about tweaks I had done etc etc.

[Your Name]

In article <5249117b$0$50705$c3e8da3$92d0...@news.astraweb.com>, JF

I wouldn't do that.

Technically if it's the exact same model of computer it should work,
but if there's a difference in hardware then it's possible that the old
one doesn't haven't something in the OS the new one requires - when a
new computer is released, Apple often has to tweak the OS.

[David Empson]

JF Mezei <jfmezei...@vaxination.ca> wrote:

> Here is a different slant to the original question:
>
> Say I have a Mac with all sorts of tweeks.
>
> Say it is at same OSX version as what a newer machine supports.
>
> Could I not buy a new Mac when it comes out, and litterally clone the
> disk of the old MacPro onto the new machine ?

In most cases, not if it is a brand new machine that was just released,
but it is possible a few months later.

When a new Mac is released, it is almost always supplied with a custom
build of Mac OS X that includes an updated kernel, addtional drivers and
possibly other software needed to support that model.

The general distribution of the same nominal version of OS X is missing
those customizations and does not support the new models (the OS might
work, but poorly; in many cases it won't even boot).

Those custom modifications are usually rolled into the general
distribution of the OS (i.e. the full installer, software update, delta
and combo updates) when the next minor version is released, but
sometimes this doesn't happen until the second subsequent minor version,
and I recall one occasion where it took three minor versions before the
general release caught up.

On rare occasions when Apple has timed a new model release coinciding
with an OS X major or minor version release _and_ that new model is
relatively minor update of an existing one (in particular, it has the
same model identifier, e.g. just updated with a faster CPU in the same
family and a better GPU), the new model comes with a standard build of
the new OS.

For example, if Apple releases the new MacBook Pro, Mac Pro and Mac Mini
at the same time as Mavericks, it is almost certain that the new Mac Pro
will have a custom build of Mavericks (otherwise all of its support code
would need to be in the golden master); the MacBook Pro and Mac Mini
will have a new processor generaion and probably a new model identifier,
so they will probably also have a custom build.

That means an existing machine updated to 10.9.0 would be missing
support files for the late 2013 Mac Pro, MacBook Pro and Mac Mini.

Once the 10.9.1 update is released, it is likely to include all the
necessary support files for the new models, therefore you will probably
be able to update an existing machine to 10.9.1, clone it onto one of
the new models, and everything will work.

If 10.9.1 turns out to be a rapid bug fix release, Apple might do a
general release of 10.9.1 as well as a custom release for the new
models, and put off integrating support for the new models into the
general release until 10.9.2.

It is very likely that any install of 10.9.2 will support the new
models, and almost certain that 10.9.3 would (all assuming the new
models come with 10.9.0).

> That would fully preserve my environment, no worries about recreating
> it, changed user permissions, forgetting about tweaks I had done etc etc.

Even if you wait until the general release has support for the new
models, there might still be some things missing, e.g. new applications
bundled only with new models outside of the OS distribution, but I'd
expect them to be re-downloadable from App Store.

For example, if Apple releases a new major version of the iLife apps
coinciding with Mavericks, they would be bundled with the new models,
but your clone would have older versions. It should be possible to
download the newer versions for free from App Store on the new Mac.
--
David Empson
dem...@actrix.gen.nz