From owner-freebsd-current  Mon Sep  9 19:38:43 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id TAA07830
          for current-outgoing; Mon, 9 Sep 1996 19:38:43 -0700 (PDT)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id TAA07824
          for <freebsd-current@FreeBSD.ORG>; Mon, 9 Sep 1996 19:38:40 -0700 (PDT)
Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with ESMTP id TAA02021; Mon, 9 Sep 1996 19:38:19 -0700 (PDT)
To: Karl Denninger <karl@Mcs.Net>
cc: henrich@crh.cl.msu.edu, freebsd-current@FreeBSD.ORG
Subject: Re: Grrr. NFS to a Sun (Slowaris 5.5.1) 
In-reply-to: Your message of "Mon, 09 Sep 1996 14:17:44 CDT."
             <199609091917.OAA16267@Jupiter.mcs.net> 
Date: Mon, 09 Sep 1996 19:38:19 -0700
Message-ID: <2019.842323099@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> > You'd be right in that impression - NFS clientry is now one of the
> > easiest way to crash yourself in -current.
> 
> Uh, why is it that my news server, which NFS serves the spool to some 30
> clients, doesn't blow up? :-)

Well, for one thing it's not the server I'm worried about.  NFS
*service* seems to work quite well, it's just the 2.2 clients which
worry me.

Simple test:

	22box# cd /usr/src
	22box# make world
	22box# mount foo:/some/big/disk /mnt
	22box# cd /usr/src/release
	22box# make release CHROOTDIR=/mnt/release BUILDNAME=2.2-BLOW_ME_UP 

If it actually gets all the way through this, please, send me mail.
I'd be interested to know.

Also, to be fair, this doesn't *exactly* match my test environment
as the NFS server is being mounted via AMD, but I strongly doubt
that has anything to do with it.

					Jordan