Date: Fri, 15 Mar 2013 09:46:28 -0400 From: John Baldwin <jhb@freebsd.org> To: freebsd-current@freebsd.org Cc: rmacklem@uoguelph.ca, Andre Oppermann <andre@freebsd.org> Subject: Re: NewNFS vs. oldNFS for 10.0? Message-ID: <201303150946.29100.jhb@freebsd.org> In-Reply-To: <514324E8.30209@freebsd.org> References: <514324E8.30209@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday, March 15, 2013 9:40:56 am Andre Oppermann wrote:
> Hi Rick, all,
>
> is there a plan to decide for one NFS implementation for FreeBSD 10.0,
> or to keep both around indefinately?
>
> I'm talking about:
> oldNFS in sys/{nfs, nfsclient, nfsserver} NFSv2+NFSv3
> newNFS in sys/fs/{nfs, nfsclient, nfsserver} NFSv2+NFSv3+NFSv4
>
> NewNFS supports newer NFS standards and seems to have proven itself in
> some quite heavy traffic environments.
>
> Is there any reason to keep oldNFS around other than nostalgic?
It can probably be removed. It's kind of handy to keep around as long as 8.x
is around since it uses oldNFS by default as it makes merging bugfixes to the
NFS client a bit easier (you fix both clients in HEAD and can then just svn
merge both of those to 8 and 9). Having several fixes to the NFS client
recently and being in a position of still using 8.x with oldNFS in production,
I would prefer to not remove it quite yet.
--
John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201303150946.29100.jhb>