From owner-freebsd-current  Mon Sep  9 14:34:49 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id OAA21309
          for current-outgoing; Mon, 9 Sep 1996 14:34:49 -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 OAA21292
          for <freebsd-current@freebsd.org>; Mon, 9 Sep 1996 14:34:41 -0700 (PDT)
Received: (from henrich@localhost) by crh.cl.msu.edu (8.7.5/8.7.3) id RAA01021; Mon, 9 Sep 1996 17:33:16 -0400 (EDT)
From: Charles Henrich <henrich@crh.cl.msu.edu>
Message-Id: <199609092133.RAA01021@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 17:33:16 -0400 (EDT)
Cc: freebsd-current@freebsd.org
In-Reply-To: <21765.842293313@time.cdrom.com> from "Jordan K. Hubbard" at "Sep 9, 96 11:21:53 am"
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

> You'd be right in that impression - NFS clientry is now one of the
> easiest way to crash yourself in -current.
>
> > Hints anyone?
>
> Find us an NFS guru with a little free time? :-) The #1 problem with
> FreeBSD and NFS isn't a technical one, it's a personnel problem.  The
> number of people who truly understand that code can literally be
> counted on one hand, and all of them are in high demand. :-(

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.

-Crh

       Charles Henrich     Michigan State University     henrich@msu.edu

                         http://pilot.msu.edu/~henrich