Date: Fri, 12 Sep 2014 17:12:58 -0400 (EDT) From: Rick Macklem <rmacklem@uoguelph.ca> To: Lionel Cons <lionelcons1972@gmail.com> Cc: Freebsd hackers list <freebsd-hackers@freebsd.org>, Simon Toedt <simon.toedt@gmail.com>, Jordan Hubbard <jkh@ixsystems.com>, Richard Yao <ryao@gentoo.org>, Jan Bramkamp <crest@rlwinm.de> Subject: Re: Tool to access ZFS/NFSv4 alternate data streams on FreeBSD? Message-ID: <1757754054.35708274.1410556378584.JavaMail.root@uoguelph.ca> In-Reply-To: <CAPJSo4WiZm7peHL7g0C-XbADhWip2q7H5k7=%2BFnm4yzw4EJ0Pw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Lionel Cons wrote: > On 9 September 2014 23:29, Rick Macklem <rmacklem@uoguelph.ca> wrote: > > 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= not likely > >> >> to > >> >> get anyone to want to use them, at which point the whole > >> >> =E2=80=9Csharing=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. > >> > >> Solaris tools already have support for this. Also AT&T AST from > >> David > >> Korn have support for O_XATTR, too. > >> > > 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.) >=20 > I don't think you FreeBSD should *copy* the code. But it can be used > for reference how the extended tar headers for filesystem forks > should > look like. That's all. >=20 > > > > 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. >=20 > If anyone can get the kernel parts I think we can sponsor someone to > do the userland work. >=20 Hmm, well others that are more familiar with the traditions of the FreeBSD will need to comment. I have never figured out how the "collective" makes technical direction decisions. I think that you might want to email on freebsd-arch@ proposing that suppor= t for openat()/resource forks be added to FreeBSD. Then, based on what respon= ses occur to this "big picture" proposal, whether or not to do it may become apparent? If the collective thinks it is appropriate, I can probably find time to do the kernel bits for NFSv4/ZFS. (I have no interest in trying to add support to UFS or doing the userland bits.) rick > Lionel > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to > "freebsd-hackers-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1757754054.35708274.1410556378584.JavaMail.root>