From owner-freebsd-current@FreeBSD.ORG Wed Apr 27 00:45:26 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 74DFB1065677; Wed, 27 Apr 2011 00:45:26 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 1D9CE8FC1E; Wed, 27 Apr 2011 00:45:25 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApwEALllt02DaFvO/2dsb2JhbACEUqINiHCtF5EdgSmDUH0EjkGOPA X-IronPort-AV: E=Sophos;i="4.64,271,1301889600"; d="scan'208";a="119591198" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 26 Apr 2011 20:45:25 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 2BEEEB3FA5; Tue, 26 Apr 2011 20:45:25 -0400 (EDT) Date: Tue, 26 Apr 2011 20:45:25 -0400 (EDT) From: Rick Macklem To: John Baldwin Message-ID: <1653029545.617817.1303865125121.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <201104260926.05033.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.201] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - IE7 (Win)/6.0.10_GA_2692) Cc: "O. Hartmann" , freebsd-current@freebsd.org Subject: Re: Heads Up: default NFS server changing to the new one X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 27 Apr 2011 00:45:26 -0000 > > Actually, I think we should switch GENERIC in HEAD to the new client > and > kernel very soon. The goal is to get current users testing the new > client and > server so they can uncover any bugs. If problems crop up during the > testing > that can't be resolved, we can always revert to the older > client/server for > the release. > Well, I think the client is now ready. I believe that the recent commits have fixed diskless booting and the old mount syscall (nfs_cmount()). So, I am planning on doing the client switchover soon. rick