From owner-freebsd-fs@FreeBSD.ORG Wed Apr 20 22:57:13 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E520D1065674; Wed, 20 Apr 2011 22:57:13 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 8CEEA8FC1B; Wed, 20 Apr 2011 22:57:13 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApwEACxkr02DaFvO/2dsb2JhbACEUKFtiG+tUJEOgSmDTnoEjiI X-IronPort-AV: E=Sophos;i="4.64,248,1301889600"; d="scan'208";a="118163484" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 20 Apr 2011 18:57:12 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 798B1B3F3A; Wed, 20 Apr 2011 18:57:12 -0400 (EDT) Date: Wed, 20 Apr 2011 18:57:12 -0400 (EDT) From: Rick Macklem To: Pawel Jakub Dawidek Message-ID: <1382687340.380996.1303340232443.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <20110420222523.GJ1907@garage.freebsd.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.202] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Cc: freebsd-fs@freebsd.org Subject: Re: question on extended attributes X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2011 22:57:14 -0000 > > Hmm. NFSv4 supports the resource forks model, too. (They called them > > named attributes.) I suppose that there would have to be some new > > VOPs > > though. For example, the NFSv4 server needs to be able to get all > > the > > attribute names, so it can generate a reply to the client (in that > > ugly > > readdir xdr format) and I don't think there's a way in the current > > VFS > > to ask "give me all the extended attribute names", is there? > > You mean all extended attribute names in the entire file system? Nope. All for one object. > That doesn't seem sensible. You can still list extended attributes of > the given file system object with VOP_LISTEXTATTR(9). > Ok, I didn't know about this. It is probably doable then. Won't get to it for a while though. Thanks for the info, rick ps: It's a fair bit of coding, because the "list" of attributes for an object looks like a directory, then the items can be "look'd up", "open'd", "read" and "written" like ordinary files.