Date: Tue, 9 Sep 2014 17:29:40 -0400 (EDT) From: Rick Macklem <rmacklem@uoguelph.ca> To: Simon Toedt <simon.toedt@gmail.com> Cc: freebsd-hackers@freebsd.org, Richard Yao <ryao@gentoo.org>, Jordan Hubbard <jkh@ixsystems.com>, Jan Bramkamp <crest@rlwinm.de>, Lionel Cons <lionelcons1972@gmail.com> Subject: Re: Tool to access ZFS/NFSv4 alternate data streams on FreeBSD? Message-ID: <220565922.34288992.1410298180362.JavaMail.root@uoguelph.ca> In-Reply-To: <CAPL6_jR8O4W6Ad_yDR_khJvUV-mgsDW1AM7aWF=K3JTfA9AiYg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Simon Toedt wrote: > On Tue, Sep 9, 2014 at 1:47 PM, Rick Macklem <rmacklem@uoguelph.ca> > wrote: > > Jordan Hubbard wrote: > >> 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=E2=80= =99s > >> backing them up / copying them around that gets more involved, and > >> if you can=E2=80=99t back up certain attributes then you=E2=80=99re no= t likely to > >> get anyone to want to use them, at which point the whole =E2=80=9Cshar= ing=E2=80=9D > >> aspect kind of takes a back seat. > >> > > Yep. I strongly suspect you are correct. > > > > The question then becomes: > > - Do we wait and see if someone chooses to get around to doing all > > the hard userland work. >=20 > Solaris tools already have support for this. Also AT&T AST from David > Korn have support for O_XATTR, too. >=20 Hopefully others will correct me if I have this incorrect, but I thought CDDL code could only be used for optional components of FreeBSD? I suspect tar and friends are considered core components and that code for this would have to be written by someone (ie. couldn't use CDDL code?). (I'm assuming that these tools are in OpenSolaris.) Be aware that most of FreeBSD's development is done by volunteers in their spare time, so I have no idea if someone is interested in doing this. rick > > or > > - Do the easy part in the kernel and then hope someone does the > > hard userland work because they need it. > > or > > - Just decide that the Linux style extended attributes are adequate > > and not do resource forks at all? >=20 > -1 for adopting the Linux junk. Basically, as they evolve, they go > and > evolve into Solaris's O_XATTR in the next ten years, with the pain of > constant API changes on the way. Each month someone cries about size > limit in the Linux style extended attributes or that listing or tar > support doesn't work etc >=20 > Solaris O_XATTR support has the beauty that it works now and is even > supported on NFSv4 and is compatible to both Windows and MacOS > resource forks. >=20 > Simon >=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?220565922.34288992.1410298180362.JavaMail.root>