Re: HFS+

[prev] [thread] [next] [lurker] [Date index for 2005/05/13]

From: Michael G Schwern
Subject: Re: HFS+
Date: 23:31 on 13 May 2005
On Fri, May 13, 2005 at 03:29:55PM -0500, Peter da Silva wrote:
> > I just uploaded a text file with a resource fork from my Mac using rsyncx
> > to my Debian machine.  It went across fine with no resource fork.  rsyncx 
> > is 2.1 (2.6.0 protocol 27) and on the Debian side its 2.6.4 protocol 29.
> 
> You apparently didn't tell rsyncx to "handle resource forks". If you don't
> ask it to do its "x" stuff, it acts just like standard rsync. I don't remember
> the option now, but it's not on by default.

I don't see anything in the man page or --help listing about "fork" or 
"resource" but rsyncx seems to have the habit of not documenting its new,
magic switches.  Hate.  When I do an rsync to a local filesystem 
it does copy the resource fork... but then again so does "cp".  I don't have 
a remote Mac to try it out to see if this also happens in a remote rsync but
I suspect you're right.

However, using the Quick RsyncX Script Generator the script it generates
has a mysterious --eahfs option.  If I use that it just doesn't work because
the remote rsync doesn't have that switch.  It also uses some --showtogo
option which the Debian rsync also doesn't know, desite being a newer rsync. 
That's hateful.

But if it doesn't do it by default isn't that the right thing to do?
If you asked it to send resource forks to a filesystem which can't handle
them... well, its your gun and you pointed it at your foot.... but how did
you manage that?


Speaking of hate, the RsyncX Script Generator has the interesting option to
"scp rsync to Destination First" which would seem to nicely handle the
problem of incompatible versions of rsync or the remote not having rsync at
all.  I expected it to go into /tmp/username or something.  It tries to put 
it into /usr/local/bin!!!  GAH!  Only my lack of permissions to do so
saved me from that fate.  There's a "Test Mode - Dry Run Only" option.  If I 
choose that it STILL tries to copy rsync into dest:/usr/local/bin!

Finally, this Quick RsyncX Script Generator doesn't actually generate a
script.  I expected some way to save the resulting script so I could run
it later rather than having to run it immediately, kill it and copy it from
the terminal window.


-- 
Michael G Schwern     schwern@xxxxx.xxx     http://www.pobox.com/~schwern
Ahh email, my old friend.  Do you know that revenge is a dish that is best 
served cold?  And it is very cold on the Internet!
There's stuff above here

Generated at 23:00 on 18 May 2005 by mariachi 0.52