Date: Tue, 9 Sep 2014 17:53:20 +0200 From: Simon Toedt <simon.toedt@gmail.com> To: Jordan Hubbard <jkh@ixsystems.com> Cc: freebsd-hackers@freebsd.org, Richard Yao <ryao@gentoo.org>, Rick Macklem <rmacklem@uoguelph.ca>, Lionel Cons <lionelcons1972@gmail.com>, Jan Bramkamp <crest@rlwinm.de> Subject: Re: Tool to access ZFS/NFSv4 alternate data streams on FreeBSD? Message-ID: <CAPL6_jQAxQbw9a=6yV_1VQdv_cnTxSpQdnOzGqqsjzmC3wCz6w@mail.gmail.com> In-Reply-To: <9F4D2C26-F077-4CA7-A532-BA4CE562C50D@ixsystems.com> References: <755175739.33844219.1410217844431.JavaMail.root@uoguelph.ca> <9F4D2C26-F077-4CA7-A532-BA4CE562C50D@ixsystems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Sep 9, 2014 at 6:47 AM, Jordan Hubbard <jkh@ixsystems.com> wrote: > Yep. I was just describing the experience that OS X went through in impl= ementing extattrs / legacy resource fork support. To recap it very briefly= : Having NFSv4 support extattrs (or even named streams, if you want to go = that far) is the comparatively easy part. It=E2=80=99s backing them up / c= opying them around that gets more involved, and if you can=E2=80=99t back u= p certain attributes then you=E2=80=99re not likely to get anyone to want t= o use them, at which point the whole =E2=80=9Csharing=E2=80=9D aspect kind = of takes a back seat. The native Solaris tools (tar/pax) and the AT&T AST - written by David Korn himself and used widely within AT&T and customers (i.e. cloud) support resource forks via O_XATTR. CERN also has a large set of applications which rely on O_XATTR, so it seems this is not so uncommon. Simon P.S: Solaris UFS and tmpfs support resource forks via O_XATTR and cd -@ in bash4.3
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPL6_jQAxQbw9a=6yV_1VQdv_cnTxSpQdnOzGqqsjzmC3wCz6w>