From owner-freebsd-stable@FreeBSD.ORG Wed Jan 5 11:01:24 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1D86C1065670 for ; Wed, 5 Jan 2011 11:01:24 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id F08EA8FC15 for ; Wed, 5 Jan 2011 11:01:23 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id p05B1C3H069967 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 5 Jan 2011 03:01:12 -0800 (PST) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id p05B1CMH069966; Wed, 5 Jan 2011 03:01:12 -0800 (PST) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA12608; Wed, 5 Jan 11 02:56:14 PST Date: Wed, 05 Jan 2011 02:55:53 -0800 From: perryh@pluto.rain.com To: marek_sal@wp.pl, rmacklem@uoguelph.ca Message-Id: <4d244e39.KoPcOoMaWed+H5De%perryh@pluto.rain.com> References: <1036681015.111502.1294189339355.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <1036681015.111502.1294189339355.JavaMail.root@erie.cs.uoguelph.ca> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org, milu@dat.pl, jyavenard@gmail.com Subject: Re: NFSv4 - how to set up at FreeBSD 8.1 ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jan 2011 11:01:24 -0000 Rick Macklem wrote: > ... one of the fundamental principals for NFSv2, 3 was a stateless > server ... Only as long as UDP transport was used. Any NFS implementation that used TCP for transport had thereby abandoned the stateless server principle, since a TCP connection itself requires that state be maintained on both ends.