From owner-freebsd-current Mon Apr 12 13:58:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 3BD0F14E89 for ; Mon, 12 Apr 1999 13:58:22 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA06590; Mon, 12 Apr 1999 13:55:56 -0700 (PDT) (envelope-from dillon) Date: Mon, 12 Apr 1999 13:55:56 -0700 (PDT) From: Matthew Dillon Message-Id: <199904122055.NAA06590@apollo.backplane.com> To: Matthew Jacob Cc: freebsd-current@FreeBSD.ORG Subject: Re: we still have NFS problems in -current? References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Probably- but this is sure amusing (not!): : :Compiling a kernel... directory is NFS mounted on a solaris 2.6 machine: : :.... : :cd9660_bmap.o: file not recognized: File format not recognized :*** Error code 1 I found it. The problem was introduced when we committed the mmap() zero-invalid-areas patch. !@#$@#$#$%#%#@%@#%#@ NFS is such a fragile piece of junk! NFS is doing some illegal shit. I'll get a patch out ASAP. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message