> Of course it wasn't done blindly. The NFS community > is one that > communicates regularly and civilly. Andreas > Gruenbacher has > worked on NFSv4 ACLs for Linux off/on for awhile. > One presentation found of his is here: > ttp://www.suse.de/~agruen/agruen-nfs4acl.pdf
I had seen it. Very interesting, in particular his comment on ZFS on page 6, and well, his conclusions about the need of mapping between POSIX and NFSv4 ACLs. > You are. Sun, Netapp, EMC, AIX have chosen to > provide > NFSv4 ACLs natively. It is the end users that will > have the most voice in convincing implementors to > make a choice. Sometimes, I just enjoy being told I'm wrong :-) Still, it's only the server-side of things. > Which brings us to your original problem and how > OpenSolaris > can help solve it. Let's review that again... Oh, my problem can be summed up as "how can I build the best file server ever". ZFS *is* a compelling choice, but how to access it over a network introduced many new quirks. And that's the rub: no way to deploy it if it can't replace the existing features of Solaris 9 or Linux servers, while adding new ones. It's easier to replace a single server than its dozens of heterogeneous clients: I can't ask them all to switch overnight to a new version. So maybe, at this point, Solaris+ZFS is the best choice if basic file serving is enough. And Linux+Ext3 or Solaris+UFS if advanced features are needed. There again, I'd like to be proven wrong, but I'm simply being pragmatic. Laurent This message posted from opensolaris.org
