From owner-freebsd-fs@FreeBSD.ORG Fri Apr 15 13:18:10 2011 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 75C87106564A for ; Fri, 15 Apr 2011 13:18:10 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.mail.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 332B68FC16 for ; Fri, 15 Apr 2011 13:18:09 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AoAHAGI9qE2DaFvO/2dsb2JhbACET5NwjjezDpErgSmDTXgEjXg X-IronPort-AV: E=Sophos;i="4.64,219,1301889600"; d="scan'208";a="117507863" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-annu-pri.mail.uoguelph.ca with ESMTP; 15 Apr 2011 08:49:10 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 335D3B3F24 for ; Fri, 15 Apr 2011 08:49:10 -0400 (EDT) Date: Fri, 15 Apr 2011 08:49:10 -0400 (EDT) From: Rick Macklem To: freebsd-fs@freebsd.org Message-ID: <1369404502.72409.1302871750151.JavaMail.root@erie.cs.uoguelph.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.202] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - IE7 (Win)/6.0.10_GA_2692) Subject: RFC: make the experimental NFS subsystem the default one X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Apr 2011 13:18:10 -0000 Hi, I think that the experimental NFS server is now ready for generic use and that the experimental NFS client will be soon, after some commits over the next week or so. How do folks feel w.r.t. making these the default? My plan is to make the server the default first (the "-e" option on mountd and nfsd would become a no-op) and a new option on mountd and nfsd ("-o" sound ok?) would be needed to run what is currently the regular server. (I am not proposing taking out the regular client/server at this time, simply making them the non-default ones.) For the client, "newnfs" would become "nfs" and what is now "nfs" would become "oldnfs" for file system type. (This wouldn't happen until a series of commits bring "newnfs" in line with "nfs" for various things, including default mount options, plus diskless booting for NFSv3 gets fixed.) So, comments w.r.t. this would be appreciated, rick