From owner-freebsd-current  Fri Feb 28 02:06:51 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id CAA18245
          for current-outgoing; Fri, 28 Feb 1997 02:06:51 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA18237
          for <freebsd-current@FreeBSD.ORG>; Fri, 28 Feb 1997 02:06:45 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id VAA07490; Fri, 28 Feb 1997 21:02:01 +1100
Date: Fri, 28 Feb 1997 21:02:01 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199702281002.VAA07490@godzilla.zeta.org.au>
To: bde@freefall.freebsd.org, michaelh@cet.co.jp
Subject: Re: cvs commit:  src/sys/conf options
Cc: freebsd-current@FreeBSD.ORG
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>>   Branch:      sys/conf  RELENG_2_2
>>   Modified:    sys/conf  options
>>   Log:
>>   YAMFC (everything except INCLUDE_CONFIG_FILE, CHILD_MAX, OPEN_MAX and
>>   ARP_PROXYALL.  This merge is mainly to start nuking EXTRAVNODES.  It
>>   also removes some non-optional MSG* and SEM* "options" and sorts the
>>   options).

>Is the intent to be able to increase vnodes via sysctl?  The ability to
>decrease will likely break a lot of assumptions made in the code. 

Changing the number vnodes via sysctl is a standard 4.4BSD (Lite1) feature.
Decreasing the number below the current number allocated has no effect
except to inhibit future allocations.  The limit is fuzzy anyway.

Bruce