From: Mikael Pettersson <mikpe@csd.uu.se>
To: neilb@cse.unsw.edu.au
Cc: linux-kernel@vger.kernel.org
Subject: NFS ACL compatibility [was: Re: [2.6] The List, pass #2]
Date: Thu, 1 Aug 2002 13:03:23 +0200 (MET DST) [thread overview]
Message-ID: <200208011103.NAA01989@harpo.it.uu.se> (raw)
On Thu, 1 Aug 2002 10:34:23 +1000 (EST), Neil Brown wrote:
>Well, given that the protocol specification isn't 100% finalised, it's
>not clear that pushing for inclusion now is entirely sensible. We
>don't want people to be using an NFSv4 on Linux that is incompatible
>in some subtle way with other vendors.
>
>Also, I suspect that NFSv4 will be fairly localised in the changes it
>makes and could well go in to 2.6.10 of whatever (afterall, reiserfs
>went in at 2.4.2).
>
>There are some changes that NFSv4 would like to make that affect
>common code, such as making open(,O_EXCL) work for a networked
>filesystem, but we can live without that (as we do with NFSv3), but
>hopefully that functionality will get in before halloween anyway.
Speaking of NFS compatibility: can Linux' NFS server implement ACLs
in a way that's compatible with Solaris NFS clients?
A sysadmin over here says this isn't the case, because Sun apparently
stepped outside of the NFSv3 protocol and handles ACLs with a
separate RPC program.
The significance of this is that unless Linux' NFS server can be made
fully compatible with Solaris NFS clients, we can't use Linux for the
new high-performance NFS servers we need to install this fall, forcing
us to go with Solaris and fairly expensive Sun HW.
/Mikael
next reply other threads:[~2002-08-01 10:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-01 11:03 Mikael Pettersson [this message]
2002-08-01 11:18 ` Neil Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200208011103.NAA01989@harpo.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®