From owner-freebsd-bugs@FreeBSD.ORG Tue Apr 29 17:02:05 2003 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 131F237B401; Tue, 29 Apr 2003 17:02:05 -0700 (PDT) Received: from meitner.wh.uni-dortmund.de (meitner.wh.Uni-Dortmund.DE [129.217.129.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2CFE743F75; Tue, 29 Apr 2003 17:02:04 -0700 (PDT) (envelope-from michaelnottebrock@gmx.net) Received: from lofi.dyndns.org (pc2-105.intern.meitner [10.3.12.105]) by meitner.wh.uni-dortmund.de (Postfix) with ESMTP id 0D6A71675A3; Wed, 30 Apr 2003 01:57:28 +0200 (CEST) Received: from kiste.my.domain (kiste.my.domain [192.168.8.4]) (authenticated bits=0) by lofi.dyndns.org (8.12.6p2/8.12.6) with ESMTP id h3U0224G029309 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Wed, 30 Apr 2003 02:02:02 +0200 (CEST) (envelope-from michaelnottebrock@gmx.net) From: Michael Nottebrock To: "Bruce A. Mah" Date: Wed, 30 Apr 2003 02:02:00 +0200 User-Agent: KMail/1.5.1 References: <200304200100.h3K10R6C057892@freefall.freebsd.org> <200304292032.35266.michaelnottebrock@gmx.net> <20030429213145.GA8037@intruder.bmah.org> In-Reply-To: <20030429213145.GA8037@intruder.bmah.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200304300202.02026.michaelnottebrock@gmx.net> X-Virus-Scanned: by amavisd-new cc: freebsd-bugs@freebsd.org Subject: Re: bin/47496: amd cannot mount 5.0-RELEASE nfs-exports X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Apr 2003 00:02:05 -0000 Oh, this looks very much like it indeed. Sorry, I don't know what exactly I looked at ... I've sent my previous message some two weeks ago - and it got stuck in a dead mail relay and was returned to me today. I just resent it without looking at the Errata again. I can't update the machine in question to -CURRENT right now, but I will get back to this PR once can.