Date: Mon, 8 Sep 2014 21:47:42 -0700 From: Jordan Hubbard <jkh@ixsystems.com> To: Rick Macklem <rmacklem@uoguelph.ca> Cc: freebsd-hackers@freebsd.org, Richard Yao <ryao@gentoo.org>, Lionel Cons <lionelcons1972@gmail.com>, Jan Bramkamp <crest@rlwinm.de> Subject: Re: Tool to access ZFS/NFSv4 alternate data streams on FreeBSD? Message-ID: <9F4D2C26-F077-4CA7-A532-BA4CE562C50D@ixsystems.com> In-Reply-To: <755175739.33844219.1410217844431.JavaMail.root@uoguelph.ca> References: <755175739.33844219.1410217844431.JavaMail.root@uoguelph.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
Yep. I was just describing the experience that OS X went through in implementing 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’s backing them up / copying them around that gets more involved, and if you can’t back up certain attributes then you’re not likely to get anyone to want to use them, at which point the whole “sharing” aspect kind of takes a back seat. On Sep 8, 2014, at 4:10 PM, Rick Macklem <rmacklem@uoguelph.ca> wrote: > Last time this came up for discussion, Jordan Hubbard got quite involved > along the lines of ``most of the work is in userland, for archive tools, etc``. > I can`t remember what the mailing list thread was called, but it was started > by a guy who was a ``resource fork`` advocate (associated with CERN if I recall), > where they use Gbyte extended attributes.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9F4D2C26-F077-4CA7-A532-BA4CE562C50D>