|
|
Symbolic links, paths, and rsync's -l option
Note: rsync's -a (same as --archive) option turns on the -l switch, i.e. it implies/includes/activates -l. Most often when folks use this utility, the -a is chosen (my second-most-used options have been -H and -u).
Also, in general when we create symlinks, they should always be composed relatively; the only exception to that in my experience has been a symlink which needs to refer to a different volume (filesystem) ... in which case it's got to be absolute (an NFS-rooted pathname, etc.) Larry. (Note: for OS X we need to have the resource-fork-capable rsync such as hfsrsync; http://hfsrsync.darwinports.com)
rsyncx
Is hfsrsync different again from rsyncx?
rsyncx
I guess not -- they seem to use the same source code (at OpenDarwin) for rsync, although I believe these are different packaging styles (i.e. the installation and package file placement). I didn't see a page for rsyncx under the new blog format at macosxlabs.org ... but their rsyncx main page is still available at
this page.
For more basic (non-sync) transfers (including the resource forks), I use ditto --rsrc or sometimes Helios xtar. And, I'm setting up netatalk on my Linux system at home, to make some sort of AFP-geared backup system; Larry. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks 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.05 seconds |
|