Re: [nfsv4] NFSv4 ACLs: {READ,WRITE}_NAMED_ATTRIBUTES

New Message Reply About this list Date view Thread view Subject view Author view Attachment view

From: Theodore Ts'o (tytso@mit.edu)
Date: 12/16/04-08:56:46 PM Z


Date: Thu, 16 Dec 2004 21:56:46 -0500
From: "Theodore Ts'o" <tytso@mit.edu>
Subject: Re: [nfsv4] NFSv4 ACLs: {READ,WRITE}_NAMED_ATTRIBUTES
Message-ID: <20041217025646.GA5145@thunk.org>

On Thu, Dec 16, 2004 at 11:42:26AM -0800, Gordon Waidhofer wrote:
> 
> Ultimately, everybody should steer toward Solaris
> style named subfiles. Solaris should rename the
> mechanism. So should NFSv4.

I disagree.  I can very easily forsee a future where filesystems have
both "extended attributes" (i.e., an atomic set/get facility for small
metadata items) and "sub-files".  Of course, as soon as sub-files
start having permissions and access controls associated with them,
then files with subfiles start looking an awful lot like a directory
with a default file if the directory is opened as a file instead of a
directory.  NTFSv5 has both facilities, for example.

The two provide different semantics, and can have very different
performance implications.  If it weren't too late, I'd argue that
NFSv4 NAMED_ATTRIBUTES should be renamed to something less confusing,
and that adding an EXTENDED_ATTRIBUTES extension which has an atomic
set/get facility would be a good thing.

						- Ted

_______________________________________________
nfsv4 mailing list
nfsv4@ietf.org
https://www1.ietf.org/mailman/listinfo/nfsv4


New Message Reply About this list Date view Thread view Subject view Author view Attachment view

This archive was generated by hypermail 2.1.2 : 03/04/05-02:13:49 AM Z CST