From owner-freebsd-current Mon Sep 9 20:50:17 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA10789 for current-outgoing; Mon, 9 Sep 1996 20:50:17 -0700 (PDT) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA10784 for ; Mon, 9 Sep 1996 20:50:13 -0700 (PDT) Received: (from henrich@localhost) by crh.cl.msu.edu (8.7.5/8.7.3) id XAA02210; Mon, 9 Sep 1996 23:47:39 -0400 (EDT) From: Charles Henrich Message-Id: <199609100347.XAA02210@crh.cl.msu.edu> Subject: Re: Grrr. NFS to a Sun (Slowaris 5.5.1) To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 9 Sep 1996 23:47:39 -0400 (EDT) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <1858.842321274@time.cdrom.com> from "Jordan K. Hubbard" at "Sep 9, 96 07:07:54 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> What I dont understand is if no one is working on NFS, how is it going >> downhill? I mean, cant we just revert back to the NFS that was in 0612, it >> seemed to work very well. > > I think it's more a question of dependencies. You don't need to > change *anything* in the NFS code to make it break, after all, there > being so many other things it depends on which can change. As a logical note, I've been doing heavy NFS client activity on 0801 since about 0801 :) and its been stable, its never ever nuked my machine, it just gets in these states where it takes about 30 seconds for something to timeout, then it comes back to life.. -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich