From owner-freebsd-bugs  Mon May  6 21:15:00 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id VAA08161
          for bugs-outgoing; Mon, 6 May 1996 21:15:00 -0700 (PDT)
Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id VAA08152
          for <bugs@freebsd.org>; Mon, 6 May 1996 21:14:55 -0700 (PDT)
Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id AAA03014; Tue, 7 May 1996 00:13:45 -0400
From: Bill Paul <wpaul@skynet.ctr.columbia.edu>
Message-Id: <199605070413.AAA03014@skynet.ctr.columbia.edu>
Subject: Re: Installing SNAPs with NFS /usr doesn't work
To: joerg_wunsch@uriah.heep.sax.de
Date: Tue, 7 May 1996 00:13:43 -0400 (EDT)
Cc: bugs@freebsd.org
In-Reply-To: <199605062215.AAA07033@uriah.heep.sax.de> from "J Wunsch" at May 7, 96 00:15:31 am
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-bugs@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Of all the gin joints in all the world, J Wunsch had to walk into mine 
and say:

> As Bill Paul wrote:
> 
> > I must be doing something wrong, but I can't figure out what...
> 
> Something's really broken with NFS installations (but only
> installations as it seems).  I've done two SNAP installs lately (from
> the WC CDROM), one to a Toshiba laptop that didn't work (not even with
> ``NFS slow''), and one to a plain ``standard PC'' that worked fine.
> 
> Puzzling.

This seems to suggest that NFS works with the GENERIC kernel but not
the BOOTMFS kernel. This being the case, there are a couple of
possibilities that leap to mind, neither of which I'm equipped to debug 
(yet). The first is that with the BOOTMFS kernel, MAXUSERS is reduced 
from 10 to 4. It was 10 in 2.1.0-RELEASE. Second, BOOTMFS also uses 
'options NFS_NOSERVER' in order to avoid pulling in the NFS server 
support code and thus reduce the size of the kernel image.

Maybe making MAXUSERS that small impacts NFS in a nasty way. Maybe 
'options NFS_NOSERVER' breaks something in the client support code. Maybe 
both are interacting in an unusual way.

Or maybe it's something completely different. In any event, I won't
know until I can get the stupid thing bootstrapped. *sigh* I really
don't want to do a 'make world.'

-Bill

-- 
=============================================================================
-Bill Paul            (212) 854-6020 | System Manager
Work:         wpaul@ctr.columbia.edu | Center for Telecommunications Research
Home:  wpaul@skynet.ctr.columbia.edu | Columbia University, New York City
=============================================================================
License error: The license for this .sig file has expired. You must obtain
a new license key before any more witty phrases will appear in this space.
=============================================================================