From owner-freebsd-current@FreeBSD.ORG Thu Apr 28 23:30:35 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 0674A1065672 for ; Thu, 28 Apr 2011 23:30:35 +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 B64808FC12 for ; Thu, 28 Apr 2011 23:30:34 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApwEAGn3uU2DaFvO/2dsb2JhbACEUKIoiHCsNpEpgSmDUH0EjlyOJw X-IronPort-AV: E=Sophos;i="4.64,283,1301889600"; d="scan'208";a="119856433" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 28 Apr 2011 19:30:33 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 929217CBF8; Thu, 28 Apr 2011 19:30:33 -0400 (EDT) Date: Thu, 28 Apr 2011 19:30:33 -0400 (EDT) From: Rick Macklem To: Craig Rodrigues Message-ID: <1700824816.743816.1304033433592.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <20110428002743.GA31514@crodrigues.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: FreeBSD Current Subject: Re: Heads up: default nfs client switched to 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: Thu, 28 Apr 2011 23:30:35 -0000 > On Wed, Apr 27, 2011 at 07:39:17PM -0400, Rick Macklem wrote: > > > Hi, > > > > > > Is there any impact on /usr/sbin/amd? > > > > > I'll admit I haven't tested it (I've never used the FreeBSD amd). I > > will > > do so once I figure out how to set it up, but I'm hoping others will > > report > > any problems. If you can test it, that would be appreciated. (I > > can't think > > of why it wouldn't work, but...) > > Hi, > > I'll try and test amd and give feedback. > > -- > Craig Rodrigues > rodrigc@crodrigues.org > Thanks to Craig's testing, there is now a fix in head that makes the new client work with amd. rick