Date: Thu, 25 Jan 2001 01:11:12 +0100 From: Matthias Andree <matthias.andree@stud.uni-dortmund.de> To: Guy Harris <gharris@flashcom.net> Cc: Mike Smith <msmith@freebsd.org>, Matthias Andree <ma@dt.e-technik.uni-dortmund.de>, Linux NFS mailing list <nfs@lists.sourceforge.net>, FreeBSD Stable <freebsd-stable@freebsd.org> Subject: Re: [NFS] Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, read-only export Message-ID: <20010125011111.A12526@emma1.emma.line.org> In-Reply-To: <20010124101007.A344@quadrajet.flashcom.com>; from gharris@flashcom.net on Wed, Jan 24, 2001 at 10:10:07 -0800 References: <20010124001701.F344@quadrajet.flashcom.com> <200101241104.f0OB4sS10071@mass.dis.org> <20010124101007.A344@quadrajet.flashcom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 24 Jan 2001, Guy Harris wrote:
> I'm not sure "Permission denied" is all that useful, either; if the file
> has permissions rw-r--r-- and is owned by me, "Permission denied" is a
> bit of a weird error - I'd rather have the message the program shows me
> or logs to a file or whatever say "Read-only file system", as that tells
> me that the underlying problem is that *something* is read-only, even if
> it doesn't tell me whether it's the client machine's fault for
> NFS-mounting it read-only or the server's fault for {locally mounting
> it, exporting it} read-only.
You're wasting your time. Access permissions may map differently on
different systems, and may be changed by the server at any time.
> 2.4.0, which is definitely not an ancient release, still appears, from
> looking at the code in question, to have that buggy behavior.
There has been a mail on the Linux-kernel mailing list claiming
otherwise, I haven't tested it.
--
Matthias Andree
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?20010125011111.A12526>