From owner-freebsd-current@FreeBSD.ORG Fri Oct 24 15:43:34 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 80FB39D8 for ; Fri, 24 Oct 2014 15:43:34 +0000 (UTC) Received: from cyrus.watson.org (cyrus.watson.org [198.74.231.69]) by mx1.freebsd.org (Postfix) with ESMTP id 5B0E5659 for ; Fri, 24 Oct 2014 15:43:34 +0000 (UTC) Received: from fledge.watson.org (fledge.watson.org [198.74.231.63]) by cyrus.watson.org (Postfix) with ESMTPS id 4C45246B43; Fri, 24 Oct 2014 11:43:28 -0400 (EDT) Date: Fri, 24 Oct 2014 16:43:28 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Rick Macklem Subject: Re: RFC: getting rid of oldnfs In-Reply-To: <691948956.6194558.1414090646089.JavaMail.root@uoguelph.ca> Message-ID: References: <691948956.6194558.1414090646089.JavaMail.root@uoguelph.ca> User-Agent: Alpine 2.11 (BSF 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed 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: Fri, 24 Oct 2014 15:43:34 -0000 On Thu, 23 Oct 2014, Rick Macklem wrote: > Someone just pinged me on this and I figured I should bring it up. > > 1 - Is anyone out there still using oldnfs due to unresolved > problems with the new one? (I am not aware of any outstanding > issues in the new nfs that don't exist in the oldnfs.) > 2 - Does anyone see a problem with getting rid of oldnfs for > FreebSD-11? > 3 - If I get rid of it in -head, I can do it either in mid-December > or mid-April. (I can't do commits during the winter.) > Does anyone have a rough idea when the 11.0 release cycle will > start, so I can choose which of the above would be preferable? > (I figured I'd wait until after the last 10.n release that happens > before 11.0, since it will be easier to MFC before the removal of > oldnfs.) > > Thanks in advance for any comments, rick > ps: John, I've cc'd you since I thought you are the guy most likely to > need to do commits/MFCs to oldnfs. I think removing it is fine, but as early as possible (as John says) to give our -CURRENT users time to stop working around bugs and start reporting them :-). Robert