Date: Thu, 25 Jan 2001 01:14:52 +0100 From: Matthias Andree <matthias.andree@stud.uni-dortmund.de> To: Mike Smith <msmith@freebsd.org> Cc: Guy Harris <gharris@flashcom.net>, 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: <20010125011452.C12526@emma1.emma.line.org> In-Reply-To: <200101242030.f0OKUTI00828@mass.dis.org>; from msmith@freebsd.org on Wed, Jan 24, 2001 at 12:30:29 -0800 References: <20010124104216.F344@quadrajet.flashcom.com> <200101242030.f0OKUTI00828@mass.dis.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Oh. "Joy". > > > If you do want to work around the Linux bug, you'd probably have to send > > another ACCESS request over the wire, with the write bits turned off; > > I'm not sure whether that's worth the effort or not. > > Based on that; no. I think if people want to run v3 against a Linux > server, they will just have to turn the ACCESS cache off. In the > meantime, is there any constructive way we can encourage the Linux NFS > folks to fix this behaviour? No need to, a patch that makes my boxes work has been published on the Linux-kernel mailing list and I think it may be integrated into 2.2.19 if someone asks Alan to merge it, and Linus would certainly not reject a similar fix for 2.4.1 if needed. > 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?20010125011452.C12526>