From owner-freebsd-current@FreeBSD.ORG Fri Oct 24 16:17:40 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 B23EE6DF; Fri, 24 Oct 2014 16:17:40 +0000 (UTC) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 23917A40; Fri, 24 Oct 2014 16:17:39 +0000 (UTC) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.14.9/8.14.9) with ESMTP id s9OGHZ3Y002963 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 24 Oct 2014 19:17:35 +0300 (EEST) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.9.2 kib.kiev.ua s9OGHZ3Y002963 Received: (from kostik@localhost) by tom.home (8.14.9/8.14.9/Submit) id s9OGHZtT002962; Fri, 24 Oct 2014 19:17:35 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Fri, 24 Oct 2014 19:17:35 +0300 From: Konstantin Belousov To: Robert Watson Subject: Re: RFC: getting rid of oldnfs Message-ID: <20141024161735.GB1877@kib.kiev.ua> References: <691948956.6194558.1414090646089.JavaMail.root@uoguelph.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.0 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on tom.home Cc: Rick Macklem , 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 16:17:40 -0000 On Fri, Oct 24, 2014 at 04:43:28PM +0100, Robert Watson wrote: > 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 > :-). I remember the main reason for keeping oldnfs, both server and client, around in HEAD was to facilitate MFC of fixes to the branches which still use oldnfs, i.e. stable/8. If this reason is still valid, oldnfs have to stay in HEAD till stable/8 is supported or interested for developers. I usually do not like direct commits into the stable branches. Otherwise, I see no reason to keep oldnfs around.