Date: Wed, 21 Jan 2009 22:10:38 -0800 From: Tim Kientzle <kientzle@freebsd.org> To: a134qaed@gmail.com Cc: freebsd-current@freebsd.org Subject: Re: Extattr portability? Message-ID: <49780DDE.2090800@freebsd.org> In-Reply-To: <bdf82f800901101456x57c1c1ecmba32e6af6f627622@mail.gmail.com> References: <4965927D.1060507@freebsd.org> <alpine.BSF.2.00.0901091525300.78432@fledge.watson.org> <bdf82f800901092341y2459b8bcyd706a6f9aabb47ea@mail.gmail.com> <4968EF7E.5040002@freebsd.org> <bdf82f800901101456x57c1c1ecmba32e6af6f627622@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
a134qaed@gmail.com wrote: > On 1/10/09, Tim Kientzle <kientzle@freebsd.org> wrote: >>Dylan Cochran wrote: >> >>Wonderful! Care to help test? > > Absolutely. First draft of this is available on Googlecode right now: http://libarchive.googlecode.com/ The FreeBSD support only archives/restores attributes in the user namespace right now. They get stored in the archive as PAX attributes with the name LIBARCHIVE.xattr.user.<name> with the actual value base-64 encoded for portability. Non-ASCII characters in the name are encoded using URL-style %XX hex encoding. All attributes are always recorded when you create the archive; the extended attributes are only restored with the -p flag. I haven't tested this yet, but bsdtar should now be able to move user extended attributes between Linux and FreeBSD portably. I've started reading up on the MacOS extended attribute support but doubt I'll have time to try implementing the OS-specific parts of that. If anyone else wants to take a shot, it's a pretty well isolated piece of code that shouldn't take long at all to implement. The tedious part will be the testing. Ditto for Solaris. Tim
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49780DDE.2090800>