From owner-freebsd-questions@FreeBSD.ORG Thu Jun 22 10:28:10 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 EEDD616A47B for ; Thu, 22 Jun 2006 10:28:10 +0000 (UTC) (envelope-from xfb52@dial.pipex.com) Received: from smtp-out4.blueyonder.co.uk (smtp-out4.blueyonder.co.uk [195.188.213.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5CF3943D5A for ; Thu, 22 Jun 2006 10:28:09 +0000 (GMT) (envelope-from xfb52@dial.pipex.com) Received: from [172.23.170.142] (helo=anti-virus02-09) by smtp-out4.blueyonder.co.uk with smtp (Exim 4.52) id 1FtMPw-0001CF-FS; Thu, 22 Jun 2006 11:28:08 +0100 Received: from [82.41.34.175] (helo=[192.168.0.2]) by asmtp-out5.blueyonder.co.uk with esmtp (Exim 4.52) id 1FtMPv-0002Nu-VB; Thu, 22 Jun 2006 11:28:07 +0100 Message-ID: <449A70B7.6060904@dial.pipex.com> Date: Thu, 22 Jun 2006 11:28:07 +0100 From: Alex Zbyslaw User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-GB; rv:1.7.13) Gecko/20060515 X-Accept-Language: en MIME-Version: 1.0 To: DSA - JCR References: <3044.217.114.136.133.1150793055.squirrel@llca513-a.servidoresdns.net> In-Reply-To: <3044.217.114.136.133.1150793055.squirrel@llca513-a.servidoresdns.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: NFS Server and MS Windows X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jun 2006 10:28:11 -0000 DSA - JCR wrote: > >I have read it and downloaded, but it seems to be something obsolete (v. >3.5 is from 2004) and I suspect they hasn't made nothing new. > > It supports NFSv3 and TCP mounts which (right now) is all you want. We'll see if MS start to support NFSv4, but right now, IIRC, even BSD may not support that fully. The thing about software, is that if it works, it doesn't need updating. NFS does not get 38 new features a fortnight so doesn't need patching all the time. If the software worked in 2004, and the standard didn't change, MS would have no need to update anything. I cannot say that MS NFS works fine, because I am still evaluating it myself. I can say that googling *didn't* turn up millions of problems. So it's probably the case that since this is a relatively straightforward protocol with a well defined standard (RFC), even MS could find competent programmers to implement it. --Alex