|
|
cp and rsrc forks
Be careful with "cp"--it will not move Resource forks, which, depending on the Application and depending on the file--are still used.
cp and rsrc forks
"cp --rsrc [source] [destination]" will handle resource forks. It's undocumented, but it works.
ditto
Use ditto instead. It's part of the default install and it handles resource forks and metadata. You use the --rsrc flag to tell it to handle the resource forks and metadata. In this hint you would replace the line:
cp and rsrc forks
I had never heard that you could use -rsrc with cp (with ditto, yes, but cp...hmmm). Use cp for files that don't have resource forks or metadata. Use CpMac (comes with the Developer Tools) for things that have these. For me, this means copy photos with CpMac in order to preserve the image metadata. You can also use these to copy huge files to other machines on your network. It is faster to copy with cp or CpMac than it is to drag and drop. For example, you have a giant CAD project that needs to go to your bosses machine. Use CpMac to copy it to a network accesible directory on his machine and the file will copy faster than drag and drop. ---
cp -R and rsrc forks
on a file that you know has a resource fork. Now try
Go to another/location and list its resource fork. It is there! -Mark |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.09 seconds |
|