From owner-freebsd-current@FreeBSD.ORG Wed Dec 17 01:04:39 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7ECEB657; Wed, 17 Dec 2014 01:04:39 +0000 (UTC) Received: from esa-annu.net.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 26B55D48; Wed, 17 Dec 2014 01:04:38 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: As8EACTWkFSDaFve/2dsb2JhbABahDSDAsYfgk0CgTIBAQEBAX2EDQEFI1YbDgoCAg0ZAlkGiD++c5YcAQEBAQEBAQMBAQEBAQEBG4EhjW8RARw0B4JogUEFiUKOQIJeh0OCVYM4IoQKIIE8OX4BAQE X-IronPort-AV: E=Sophos;i="5.07,590,1413259200"; d="scan'208";a="178884266" Received: from muskoka.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.222]) by esa-annu.net.uoguelph.ca with ESMTP; 16 Dec 2014 20:04:10 -0500 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 1AE483CE1D; Tue, 16 Dec 2014 20:04:10 -0500 (EST) Date: Tue, 16 Dec 2014 20:04:10 -0500 (EST) From: Rick Macklem To: Bryan Drewery Message-ID: <1629848501.14187170.1418778250097.JavaMail.root@uoguelph.ca> In-Reply-To: <5490CB8E.8010606@FreeBSD.org> Subject: Re: old NFS stripped out in a few days MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.203] X-Mailer: Zimbra 7.2.6_GA_2926 (ZimbraWebClient - FF3.0 (Win)/7.2.6_GA_2926) Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Dec 2014 01:04:39 -0000 Bryan Drewery wrote: > On 12/16/2014 4:58 PM, Rick Macklem wrote: > > FYI, I am planning on stripping the old NFS code out of head > > on about Mon. Dec 22. This has been discussed before and most > > seemed to be in favour of it. > > > > If you see a big problem with this, please email soon with > > your concerns. > > > > rick > > Mind clarifying briefly the impact of this? Does the oldnfs code > offer a > single benefit over the current NFS code? > Well, I remember one person reporting that they still use the old NFS server and that they had problems with the new one. Unfortunately, these servers were used in production and they didn't have time to update them or try and isolate what problem(s) they experienced with the new server. No one else has reported problems with the new code that they avoid with the old code. (One other site has a lot of local patches for the old NFS server, but I think they will just have to port those to the new server if/when they want to upgrade to FreeBSD11.) Unless you use "-o" on nfsd to run the old server or do "mount -t oldnfs ..." to use the old client, there shouldn't be any impact, since you aren't using the old NFS client/server. If you try and do "nfsd -o" after it is removed, nfsd replies that the server isn't available and doesn't start. For "mount -t oldnfs ...", it fails after the code is removed. I, personally, don't care if it removed, but others have suggested it (I suspect to reduce "code bloat" and the fact keeping it means maintaining two NFS subsystems.) rick > -- > Regards, > Bryan Drewery > >