Welcome to the MacNN Forums.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

You are here: MacNN Forums > Software - Troubleshooting and Discussion > Mac OS X > Problem with ditto

Problem with ditto
Thread Tools
Fresh-Faced Recruit
Join Date: Jan 2003
Status: Offline
Reply With Quote
Jan 5, 2003, 12:44 AM
 
I have been unable to copy the resource forks of files using ditto. I type a command like this:

sudo ditto -V-rsrcFork 'Documents/Documentation' '/Volumes/Firewire HD 20/Documentation'

This copies the files over to my backup hard drive, but when I look at the files in the Finder, it doesn't seem to have copied the resource fork. Many of the icons are blank and when I look at them in Get Info, they have no file type assigned to them.

Am I doing something wrong, or is there something wrong with my system?

I'm not sure if this is related, but maybe it offers a clue to the solution of my problem: when I type man ditto, I get the following message before the manual text is displayed:

mdoc warning: list open at EOF! A .Bl directive has no matching .El

Thanks
     
Senior User
Join Date: Jan 2000
Status: Offline
Reply With Quote
Jan 5, 2003, 08:05 PM
 
Do you have the dev tools installed? If so, try using CpMac until you get your ditto problems sorted out.

The warning you get when you view the ditto manpage is telling you that the nroff formatting of the page is slightly broken, much like a webpage missing a closing </B> tag.
     
Mac Enthusiast
Join Date: Nov 2001
Location: Adelaide, South Australia
Status: Offline
Reply With Quote
Jan 6, 2003, 06:50 PM
 
Originally posted by mateo:
I type a command like this:

sudo ditto -V-rsrcFork 'Documents/Documentation' '/Volumes/Firewire HD 20/Documentation'

This copies the files over to my backup hard drive, but when I look at the files in the Finder, it doesn't seem to have copied the resource fork.
Maybe it's just a typo, but if you're not leaving any space between the two options it might explain the behaviour that's occurring. That is, try inserting a space between the -V and the -rsrcFork in the command quoted above, rather than jamming them together. It certainly *looks* wonky to me, and doesn't work for other utilities (try, eg, ls -l-a versus ls -l -a or even ls -la).

Cheers,
Paul
     
mateo  (op)
Fresh-Faced Recruit
Join Date: Jan 2003
Status: Offline
Reply With Quote
Jan 6, 2003, 10:12 PM
 
Originally posted by Paul McCann:
Maybe it's just a typo, but if you're not leaving any space between the two options it might explain the behaviour that's occurring. That is, try inserting a space between the -V and the -rsrcFork in the command quoted above, rather than jamming them together. It certainly *looks* wonky to me, and doesn't work for other utilities (try, eg, ls -l-a versus ls -l -a or even ls -la).

Cheers,
Paul
Thanks, Paul, It does turn out to be a typo. I've got it working now.
     
   
Thread Tools
Forum Links
Forum Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Top
Privacy Policy
All times are GMT -5. The time now is 09:57 AM.
All contents of these forums © 1995-2011 MacNN. All rights reserved.
Branding + Design: www.gesamtbild.com
vBulletin v.3.8.7 © 2000-2011, Jelsoft Enterprises Ltd., Content Relevant URLs by vBSEO 3.3.2