OISX copy
- Thread starter Ken
- Start date
Jadey
sosumi
On the command line (Terminal), copy is done by typing:
cp source destination
To copy everything, with correct permissions and such, you'll need to add a few flags to clarify exactly what you want done.
In a terminal, if you type: man cp this will bring up the manual entry for copy.
cp -p /Users/username/somefiles/ /mnt/volumes/computer2/somefiles
for example would copy those files including permission, ownership, etc.
There are other flags which ensure you copy a directory and subdirectories, force overwrites, etc.
copying just / would copy all files, you'd just need to see which flags would best suit your job.
If there is an easier, less command-line way to do this, someone else please shout it out
cp source destination
To copy everything, with correct permissions and such, you'll need to add a few flags to clarify exactly what you want done.
In a terminal, if you type: man cp this will bring up the manual entry for copy.
cp -p /Users/username/somefiles/ /mnt/volumes/computer2/somefiles
for example would copy those files including permission, ownership, etc.
There are other flags which ensure you copy a directory and subdirectories, force overwrites, etc.
copying just / would copy all files, you'd just need to see which flags would best suit your job.
If there is an easier, less command-line way to do this, someone else please shout it out
My understanding is that the 'cp' command does not copy resource forks, only data forks. I'm not sure if any OS X system files use resource forks, but if you have any Classic applications on the drive you are backing up, you will definitely run into problems if you use 'cp'.
A better solution is to use 'CpMac', which is included in the Developer Tools (and gets installed in /Developer/Tools ).
A better solution is to use 'CpMac', which is included in the Developer Tools (and gets installed in /Developer/Tools ).
My understanding is that the 'cp' command does not copy resource forks, only data forks. I'm not sure if any OS X system files use resource forks, but if you have any Classic applications on the drive you are backing up, you will definitely run into problems if you use 'cp'.
A better solution is to use 'CpMac', which is included in the Developer Tools (and gets installed in /Developer/Tools ).
A better solution is to use 'CpMac', which is included in the Developer Tools (and gets installed in /Developer/Tools ).