Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'You CAN do this, but at some risk' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
You CAN do this, but at some risk
Authored by: SOX on Oct 23, '02 12:30:48PM

For moving plain files rsync works fine as long as you dont mind losing creator codes and icons. So like you say nothing to fear there.

But when moving applications or complex documents with creator codes there is much to fear.

For example one I had to reformat my hard disk, so I made the bad mistake of tarring up all of my files and moving them over a linux machine.
when I untarred not a single one of my applications worked!!! and some of my documents could not be opened by their original apps.

So their is lots to fear since rsync works the same as tar. the good news is that this warning mostly applies to classic apps which heavily use the resource forks. Mac OS X apps have a different structure and thus tend not to have too many problems when they are rsynced.

Note if you dont want to use RsyncX there is an interesting workaround that works great. Create a UFS partion. this can be a real partition or virtual one created by disk copy. drag all of your files into this partion and then use rsync. This will work perfectly because when you drag the files from the HFS+ disk to the UFS disk, the mac dumps the HFS database entryies and resource forks in to a real separate (hidden with a ._ prefix) file that rsync handles correctly as long as you remember to copy it too



[ Reply to This | # ]