From owner-freebsd-current  Mon Apr 15 20:59:40 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id UAA05244
          for current-outgoing; Mon, 15 Apr 1996 20:59:40 -0700 (PDT)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id UAA05237
          for <freebsd-current@FreeBSD.org>; Mon, 15 Apr 1996 20:59:37 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id UAA22884; Mon, 15 Apr 1996 20:58:18 -0700 (PDT)
To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
cc: freebsd-current@FreeBSD.org (FreeBSD-current users)
Subject: Re: NFS timing (Was: Just how stable is current) 
In-reply-to: Your message of "Mon, 15 Apr 1996 20:59:52 +0200."
             <199604151859.UAA12685@uriah.heep.sax.de> 
Date: Mon, 15 Apr 1996 20:58:18 -0700
Message-ID: <22882.829627098@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

> This seems to be identical with the observation that all recent SNAPs
> have increased timing problems (up to totally unusable) when
> installing over NFS.

Yes, I hate to admit it but I just managed to reproduce it myself -
NFS installs are pretty broken in -current.

Sigh.  Any clues from the kernel gurus?

					Jordan