On 4/7/07, Wayne Davison <[EMAIL PROTECTED]> wrote:
On Sat, Apr 07, 2007 at 09:18:50AM -0700, Wayne Davison wrote:
> There is already compatibility code in place that makes sure that
> everyone is transmitting xattrs in a namespace, so Mac xattrs get
> transmitted with a "user" namespace prefixed
On Sat, Apr 07, 2007 at 09:18:50AM -0700, Wayne Davison wrote:
> There is already compatibility code in place that makes sure that
> everyone is transmitting xattrs in a namespace, so Mac xattrs get
> transmitted with a "user" namespace prefixed.
I should also point out that xattrs from non-user n
On Sat, Apr 07, 2007 at 07:13:16AM -0400, Victor Shoup wrote:
> But: will it allow backup from a file system that supports xattrs, to
> one that does not?
Not as currently envisioned. It would not be hard to add some
compatibility code into lib/sysxattrs.c that would allow an alternate
storage
I see that rsync will eventually support extended attributes, which
will be great.
But: will it allow backup from a file system that supports xattrs, to
one that does not?
For this to work, rsync would have to represent the xattrs on the
destination machine
in some special format, I suppose,
On Sat, Mar 31, 2007 at 07:33:26PM +0200, [EMAIL PROTECTED] wrote:
> Missing abbreviated xattr value, com.apple.ResourceFork, for "/Users/
> alan/Desktop/folder2/.details.textClipping.SbLEk6"
This turned out to be a general problem with the requesting of truncated
xattr values for new files. I j
