From owner-freebsd-hackers@FreeBSD.ORG Tue Sep 9 21:29:42 2014 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8298C308 for ; Tue, 9 Sep 2014 21:29:42 +0000 (UTC) Received: from esa-annu.net.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 46C6BB1A for ; Tue, 9 Sep 2014 21:29:41 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AsAEAOtwD1SDaFve/2dsb2JhbABZhDcEgnjOegGBI3iEAwEBBAEjVhsYAgINGQJLAQ0GE4g6CKdWlWYBF4EsjUojATMHgnmBUwWpFokLg30hL4EHQYEHAQEB X-IronPort-AV: E=Sophos;i="5.04,493,1406606400"; d="scan'208";a="153930307" Received: from muskoka.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.222]) by esa-annu.net.uoguelph.ca with ESMTP; 09 Sep 2014 17:29:40 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 5B32EB3EE4; Tue, 9 Sep 2014 17:29:40 -0400 (EDT) Date: Tue, 9 Sep 2014 17:29:40 -0400 (EDT) From: Rick Macklem To: Simon Toedt Message-ID: <220565922.34288992.1410298180362.JavaMail.root@uoguelph.ca> In-Reply-To: Subject: Re: Tool to access ZFS/NFSv4 alternate data streams on FreeBSD? MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Originating-IP: [172.17.91.203] X-Mailer: Zimbra 7.2.6_GA_2926 (ZimbraWebClient - FF3.0 (Win)/7.2.6_GA_2926) Cc: freebsd-hackers@freebsd.org, Richard Yao , Jordan Hubbard , Jan Bramkamp , Lionel Cons X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Sep 2014 21:29:42 -0000 Simon Toedt wrote: > On Tue, Sep 9, 2014 at 1:47 PM, Rick Macklem > 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