From owner-freebsd-current Thu Jul 29 15:25:14 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id D276D15650 for ; Thu, 29 Jul 1999 15:25:07 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id PAA79422; Thu, 29 Jul 1999 15:24:34 -0700 (PDT) (envelope-from dillon) Date: Thu, 29 Jul 1999 15:24:34 -0700 (PDT) From: Matthew Dillon Message-Id: <199907292224.PAA79422@apollo.backplane.com> To: Bill Paul Cc: peter@netplex.com.au, crossd@cs.rpi.edu, current@FreeBSD.ORG Subject: Re: IRIX 6.5.4 NFS v3 TCP client + FreeBSD server = bewm References: <199907292222.SAA17350@skynet.ctr.columbia.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :Okay. I committed the fix to the length calculation to -current and :-stable (I just love one-line patches that stop panics). I just got :done patching my NFS server machines and they all seem to get along :nicely with the SGI now. Now I can upgrade the other SGIs without :worrying about them clobbering my FreeBSD machines. : :Hm. I wonder what would happen if the FreeBSD host was the client :and the SGI was the server. : :-Bill :============================================================================= :-Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu And here is something *really* scary. For the last month I've been running NFS over TCP without even realizing it. I had set up my machines to run NFS/TCP as a test instead of NFS/UDP and then forgot to change it back! -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message