From owner-freebsd-questions@FreeBSD.ORG Wed Mar 2 22:56:27 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 697EC16A4CE for ; Wed, 2 Mar 2005 22:56:27 +0000 (GMT) Received: from scorpion.eng.ufl.edu (scorpion.eng.ufl.edu [128.227.116.10]) by mx1.FreeBSD.org (Postfix) with SMTP id D69AC43D1D for ; Wed, 2 Mar 2005 22:56:26 +0000 (GMT) (envelope-from bob89@eng.ufl.edu) Received: (qmail 10234 invoked from network); 2 Mar 2005 22:56:26 -0000 Received: from scanner.engnet.ufl.edu (HELO ?128.227.152.221?) (128.227.152.221) by scorpion.eng.ufl.edu with SMTP; 2 Mar 2005 22:56:26 -0000 Message-ID: <4226449A.40904@eng.ufl.edu> Date: Wed, 02 Mar 2005 17:56:26 -0500 From: Bob Johnson Organization: University of Florida User-Agent: Mozilla Thunderbird 1.0 (X11/20050131) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bob Johnson References: <42262EF2.8070503@eng.ufl.edu> In-Reply-To: <42262EF2.8070503@eng.ufl.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD NFS client and Netware 6.5 NFS server X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2005 22:56:27 -0000 Bob Johnson wrote: > As explained in the message below, a trace of the NFS server activity > shows that the FreeBSD client implements ls -l as a series of > operations (whatever that is) followed by an , while a Solaris > client does a series of operations (those are the Netware > abbreviations for the operations). The Solaris client does not exhibit > any of these problems. I don't know if that is meaningful with regard > to this problem, but clearly the Solaris client is doing things very > differently than the FreeBSD client. The difference in the trace (which operations the clients perform) is the difference between NFSv2 and NFSv3. The problem persists regardless of the NFS version, though. - Bob