Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 24 Jan 2001 10:46:22 -0800 (PST)
From:      Matt Dillon <dillon@earth.backplane.com>
To:        Guy Harris <gharris@flashcom.net>
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:  <200101241846.f0OIkMl69319@earth.backplane.com>
References:  <20010123015612.H345@quadrajet.flashcom.com> <20010123162930.B5443@emma1.emma.line.org> <20010123111005.D344@quadrajet.flashcom.com> <m3r91t8vxv.fsf@emma1.emma.line.org> <20010124001701.F344@quadrajet.flashcom.com> <200101241828.f0OIS2m68965@earth.backplane.com> <20010124103103.E344@quadrajet.flashcom.com>

next in thread | previous in thread | raw e-mail | index | archive | help

:
: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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200101241846.f0OIkMl69319>