From owner-freebsd-current Mon May 20 16:46:05 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA29491 for current-outgoing; Mon, 20 May 1996 16:46:05 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA29483 for ; Mon, 20 May 1996 16:46:03 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id JAA22823; Tue, 21 May 1996 09:29:16 +0930 From: Michael Smith Message-Id: <199605202359.JAA22823@genesis.atrad.adelaide.edu.au> Subject: Re: NFS bustedness... To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Tue, 21 May 1996 09:29:15 +0930 (CST) Cc: phk@critter.tfs.com, msmith@atrad.adelaide.edu.au, current@freebsd.org In-Reply-To: <4977.832628368@time.cdrom.com> from "Jordan K. Hubbard" at May 20, 96 02:39:28 pm 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 Jordan K. Hubbard stands accused of saying: > > > No I belive it is need for sysinstall, as I understood Michael he's using > > it in some other context. > > I thought he was testing it to see why NFS installs fail. :-) Yup. Or more to the point, why NFS on some of my -current systems was busted but not others. NFS_NOSERVER was only being used on the small ones, and they were the only ones sgiwing the symptoms. I can't build -current at the moment as John's VM megacommit hasn't percolated properly yet, but I had GENERIC falling over by just adding NFS_NOSERVER and reading from an NFS-mounted filesystem. > Jordan -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[