On Mon, Mar 21, 2016 at 04:19:17PM -0400, Richard Yao wrote: > Maybe I should clarify that the idea is to allow read/write/list of > extended attributes via read/write/readdir so that those that want > extended attributes that are alternative data streams can have them. I > do not want to see extended attributes and alternative data streams be > different things. I think there are differences between the two that make this awkward. Does anyone actually use alternative data stream for anything that makes the effort worthwhile? > Alternative data streams are in the NFSv4 specification, so I thought > that the developers of the NFS client driver would want something like > this. Somebody would have to make a convincing argument that it's worthwhile. Note there's also a proposal to add extended attributes to the NFSv4 protocol: https://tools.ietf.org/html/draft-ietf-nfsv4-xattrs-02 That also has some more discussion of mismatches between the named- and extended- attribute interfaces: https://tools.ietf.org/html/draft-ietf-nfsv4-xattrs-02#section-5 --b. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
