From owner-freebsd-hackers@FreeBSD.ORG Fri Oct 17 16:52:24 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.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C694B5D3 for ; Fri, 17 Oct 2014 16:52:24 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9BDEAFE2 for ; Fri, 17 Oct 2014 16:52:24 +0000 (UTC) Received: from ralph.baldwin.cx (pool-173-70-85-31.nwrknj.fios.verizon.net [173.70.85.31]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 7A508B91E; Fri, 17 Oct 2014 12:52:23 -0400 (EDT) From: John Baldwin To: freebsd-hackers@freebsd.org Subject: Re: Tool to access ZFS/NFSv4 alternate data streams on FreeBSD? Date: Fri, 17 Oct 2014 11:58:04 -0400 Message-ID: <61546786.Po81nNR1Xh@ralph.baldwin.cx> User-Agent: KMail/4.12.5 (FreeBSD/10.1-BETA2; KDE/4.12.5; amd64; ; ) In-Reply-To: References: <102210795.47541414.1410995911907.JavaMail.root@uoguelph.ca> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Fri, 17 Oct 2014 12:52:23 -0400 (EDT) Cc: Rick Macklem , Jan Bramkamp , Simon Toedt , Jordan Hubbard , Lionel Cons , Richard Yao 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: Fri, 17 Oct 2014 16:52:24 -0000 On Wednesday, October 15, 2014 12:21:43 AM Lionel Cons wrote: > On 18 September 2014 01:18, Rick Macklem wrote: > > Well, first I believe the FreeBSD project (I refer to it as the > > "collective" for want of a better word) needs to come to a consensus > > that this should be done. > > > > As I understand it, the first step towards that is a post on > > freebsd-arch@ proposing this work and why you think it is a good idea. > > > > Then, based upon the discussion/comments in response to this post, it will > > hopefully become fairly clear if the "collective" is in favour > > of doing this or not. > > > > Then, if the consensus is in favour, someone needs to do the > > coding. (I have volunteered to at least look at the kernel changes, > > but only the kernel changes.) > > Okay. I've just got the go-ahead, and initial funding :) Do you have a proposed design for how you plan to implement O_XATTR? Also, are you targeting a specific filesystem (e.g. ZFS?) -- John Baldwin