Date: Tue, 23 Jan 2001 23:41:54 +0100 (CET) From: wolfgang@lyxys.ka.sub.org (Wolfgang Zenker) To: Bjoern Groenvall <bg@sics.se> Cc: FreeBSD Stable <freebsd-stable@FreeBSD.ORG>, Linux NFS mailing list <nfs@lists.sourceforge.net>, Guy Harris <gharris@flashcom.net>, Neil Brown <neilb@cse.unsw.edu.au>, matthias.andree@stud.uni-dortmund.de Subject: Re: [NFS] Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, read-only export Message-ID: <m14LC8Q-003pdoC@lyxys.ka.sub.org> In-Reply-To: <wuofwynsj5.fsf_-_@bg.sics.se> "from Bjoern Groenvall at Jan 23, 2001 05:26:54 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> Matthias> The question remains: Linux kernel problem or FreeBSD client > Matthias> problem? > Or perhaps we should blame RFC1813? I don't think so, because .. > However, 1813 says that ACCESS > should return one of the following errors > NFS3ERR_IO > NFS3ERR_STALE > NFS3ERR_BADHANDLE > NFS3ERR_SERVERFAULT > ,and "The client encodes the > set of permissions that are to be checked in a bit mask. > The server checks the permissions encoded in the bit mask. > A status of NFS3_OK is returned along with a bit mask > encoded with the permissions that the client is allowed.". The wording here is totally clear: The client is not allowed write access on a read-only filesystem, so return NFS3_OK with the write bits turned off. > It also says > "NFS3ERR_ROFS > Read-only file system. A modifying operation was > attempted on a read-only file system." As ACCESS is not a "modifying operation", there is no contradiction here. Wolfgang To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m14LC8Q-003pdoC>