for those who care,
the yodl pkg, a prereq for building rsync3-cvs docs (& more?), had
'issues' @ version <= v2.04 with building cleanly on osx.
it's been updated today to v2.10,
http://sourceforge.net/project/showfiles.php?group_id=126615
v2.10 builds clealy, without req'd patching or error
just fyi, with help from the YODL-ers (thanks Frank & Karel!), here's
what _works_ for me with to build the
icmake-v700
yodl-v204
prereqs to rsync3 on osx 10.4.87.
# ICMAKE #
cd /path/to
rm -rf icmake*
wget ftp://ftp.rug.nl/contrib/frank/software/linux/icmake/icmake_7.
hi,
as it's been awhile since my last attempts w/ v269, i'm building the
latest rsync3-svs on osx 10.4.8; looking to see what's evolved re:
acls & xattrs support on osx ...
@ build, i note complaint abt a missing yodl2man, which originates with YODL.
YODL, then requires icmake.
as neither is a
Sorry I haven't looked into this, but atm I just don't have the time.
thanks for the update. personally, atm, i'd love to see just HEAD's
mtime (finished?) support rolled into a 'official;' rsync release.
It also seems like any solution will necessarily drop information.
osx keeps track of se
just for anyone's interest, in context -- & given that OSX apparently
has no #$&^!!! man page for "fsaclctl" :-( -- there's a bit of an
intro to osx's acl implementation that i found helpful, here:
http://www.afp548.com/article.php?story=20050506085817850
--
To unsubscribe or change options: http
First, to be clear, you are building rsync on Mac OS X, right?
You need at least Tiger.
absolutely. i've an up-to-date osx 10.4.8 install, w/ latest XTools
etc from Apple.
Don't enable acl support on osx. It doesn't work. You probably don't
have ACLs on your files anyways as it has to be enab
> will these dependencies be resolved -- either by bundling req'd
> headers with the distro, or by finding/using osx equivalents?
What dependencies? The acl and xattr headers are simply part of a
normal osx install with developer tools. No fink/etc needed.
really? then, perhaps, i'm misundersta
wayne,
thanks for the explanation.
i've noticed no mention of the new rsync work (xattr/acl) on appple's
boards ... probably not surprising as the current release is rsync
v2.6.3 + *their* patches, and they're notoriously tight-lipped about
unreleased products.
anyway, i've got a mostly-working
and the 'lartmaker' fix (iteself, slightly fixed ...):
applied.
What exactly did you have to fix ?
after applying,
http://www.opensource.apple.com/darwinsource/10.4.8.ppc/rsync-24/patches/EA.diff
http://www.opensource.apple.com/darwinsource/10.4.8.ppc/rsync-24/patches/PR-
i've built up rsync on both opensuse & osx from src.
on osx, it's v2.6.3 w/ both apple's "Extended Attributes" patches:
http://www.opensource.apple.com/darwinsource/10.4.8.ppc/rsync-24/patches/EA.diff
http://www.opensource.apple.com/darwinsource/10.4.8.ppc/rsync-24/patches/PR-3945747-endia
aha! i think ...
re: http://www.mail-archive.com/rsync@lists.samba.org/msg17509.html
--> rsync-2.6.9/patches/xattrs.diff
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
hi,
it seems there's a more-recent solution, referenced here:
http://www.lartmaker.nl/rsync/
that points out:
"Since OS X 10.4 (aka Tiger) the MacOS ships with a modified
version of rsync. An added option, -E, enables the transfer of
extended attributes."
exploring, the current apple pa
hi,
i've been coming up to speed on rsync+ssh, incremental backups, etc etc.
atm, all working great across *NIX boxes.
but, i've recently been reminded that there are 'issues' with
poor/failed backup of osx-files' metadata, w/ rsync & other tools:
http://blog.plasticsfuture.org/2006/04/23/mac
ok, so this is not entirely an rsync question. but, it seems the
'crowd' most familiar w/ hard-linking are the rsync crowd. so ...
i'm doing rsync + incremental backups to a local drive.
the incremental steps, currently, use the
rsync REMOTE_DIR OLD_DIR
... time passes ...
cp -al OLD_DIR NE
hello,
> but, although the creation times/dates are maintained, the user:group
> are NOT ... changed, instead to "unknown":"unknown"
Since you specified that users & groups should be transferred using
numeric IDs, you should check to see what the IDs are on the files.
the IDs for users & grou
hello,
i've rsync installed:
rsync version 2.6.9pre3 protocol version 29
Capabilities: 64-bit files, socketpairs, hard links, symlinks,
batchfiles,
inplace, no IPv6, 32-bit system inums, 64-bit internal inums
i'm PULLing via rsync+ssh from BoxA to BoxB, eg:
16 matches
Mail list logo