From owner-freebsd-stable Wed Jan 24 10:46:50 2001 Delivered-To: freebsd-stable@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 1A35837B69C for ; Wed, 24 Jan 2001 10:46:23 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f0OIkMl69319; Wed, 24 Jan 2001 10:46:22 -0800 (PST) (envelope-from dillon) Date: Wed, 24 Jan 2001 10:46:22 -0800 (PST) From: Matt Dillon Message-Id: <200101241846.f0OIkMl69319@earth.backplane.com> To: Guy Harris Cc: Guy Harris , Matthias Andree , Linux NFS mailing list , FreeBSD Stable Subject: Re: [NFS] Incompatible: FreeBSD 4.2 client, Linux 2.2.18 nfsv3 server, read-only export References: <20010123015612.H345@quadrajet.flashcom.com> <20010123162930.B5443@emma1.emma.line.org> <20010123111005.D344@quadrajet.flashcom.com> <20010124001701.F344@quadrajet.flashcom.com> <200101241828.f0OIS2m68965@earth.backplane.com> <20010124103103.E344@quadrajet.flashcom.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :On Wed, Jan 24, 2001 at 10:28:02AM -0800, Matt Dillon wrote: :> This particular problem, however, is entirely Linux's problem to fix. : :Umm, could somebody *PLEASE* show me *ANY* place where I argued that it :wasn't a Linux bug? I can show at least one mail message where I :said it *WAS* a Linux bug.... : :(Heck, are there any places where *anybody* argued that this wasn't a :Linux bug?) I didn't mean to say that someone argued it wasn't :-). I'm just saying that in the world of interoperability, it may actually be more of a problem hacking a solution into the FreeBSD client side then waiting for a solution on the Linux side. Even though a FreeBSD hack could be made to work, introducing that sort of pollution into the client code will only make interoperability testing between various systems (Linux, FreeBSD, solaris, NetApp, HPUX, and a host of other systems) more difficult and less definitive. NFSv3 is an industry standard today mainly because vendors have worked hard towards fixing interoperability problems, and one of the things that makes this possible is to enforce error reporting & failure conditions on the client-side. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message