From: Trond Myklebust Subject: Re: Questions about NFS over TCP Date: Wed, 23 Apr 2003 17:44:26 +0200 Sender: nfs-admin@lists.sourceforge.net Message-ID: <16038.46298.261383.948440@charged.uio.no> References: <3EA66B58.2B1E4A45@moving-picture.com> <3EA6A7AE.4F5200E7@moving-picture.com> Reply-To: trond.myklebust@fys.uio.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: nfs@lists.sourceforge.net Return-path: Received: from pat.uio.no ([129.240.130.16]) by sc8-sf-list1.sourceforge.net with esmtp (Exim 3.31-VA-mm2 #1 (Debian)) id 198MQB-0002W5-00 for ; Wed, 23 Apr 2003 08:44:32 -0700 To: James Pearson In-Reply-To: <3EA6A7AE.4F5200E7@moving-picture.com> Errors-To: nfs-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Id: Discussion of NFS under Linux development, interoperability, and testing. List-Unsubscribe: , List-Archive: >>>>> " " == James Pearson writes: > Thanks for the info - do you know what the 'best' combination > of (2.4.X) kernel/patches gives the most stable NFS over TCP > support? As far as the client is concerned, 2.4.21-rc1 on its own should suffice. I have no outstanding NFS over TCP patches beyond what I've already fed to Linus and Marcelo. Neil might have some further server side fixes though. I suggest that you check his website. Cheers, Trond ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ NFS maillist - NFS@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nfs