From owner-freebsd-current Mon Apr 12 14: 2:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id A374614F04 for ; Mon, 12 Apr 1999 14:02:43 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id NAA24817; Mon, 12 Apr 1999 13:59:59 -0700 Date: Mon, 12 Apr 1999 13:59:59 -0700 (PWT) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: we still have NFS problems in -current? In-Reply-To: <199904122055.NAA06590@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 12 Apr 1999, Matthew Dillon wrote: > :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! Why do you say that? :-) Bob Lyon still says: +Date: Mon, 22 Mar 1999 22:00:47 -0800 +From: Bob Lyon +To: mjacob@feral.com +Subject: Re: NFS - Will it ever be fixed? (fwd) + + +NFS is perfect. It needs no fixing. (Unless, we mean +"fix" as in what we do to dogs. + +/Bob > > NFS is doing some illegal shit. I'll get a patch out ASAP. Awesome. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message