From owner-freebsd-current@FreeBSD.ORG  Wed Jul  6 23:57:34 2011
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id B302F1065672
	for <freebsd-current@freebsd.org>; Wed,  6 Jul 2011 23:57:34 +0000 (UTC)
	(envelope-from sgk@troutmask.apl.washington.edu)
Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu
	[128.95.76.21]) by mx1.freebsd.org (Postfix) with ESMTP id 7E2FE8FC14
	for <freebsd-current@freebsd.org>; Wed,  6 Jul 2011 23:57:34 +0000 (UTC)
Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu
	[127.0.0.1])
	by troutmask.apl.washington.edu (8.14.4/8.14.4) with ESMTP id
	p66NvYUd071344
	for <freebsd-current@freebsd.org>; Wed, 6 Jul 2011 16:57:34 -0700 (PDT)
	(envelope-from sgk@troutmask.apl.washington.edu)
Received: (from sgk@localhost)
	by troutmask.apl.washington.edu (8.14.4/8.14.4/Submit) id
	p66NvYZK071343
	for freebsd-current@freebsd.org; Wed, 6 Jul 2011 16:57:34 -0700 (PDT)
	(envelope-from sgk)
Date: Wed, 6 Jul 2011 16:57:34 -0700
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: freebsd-current@freebsd.org
Message-ID: <20110706235733.GA71278@troutmask.apl.washington.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.3i
Subject: Can options NFSD and NFSSERVER exist in the same kernel?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Jul 2011 23:57:34 -0000

So, I upgraded a system from Feb 10 -current to today's
-current code.  In doing so, I changed the kernel config
options from

options         NFSCLIENT               # Network Filesystem Client
options         NFSSERVER               # Network Filesystem Server

to 

options         NFSCL                # Network Filesystem Client
options         NFSD                 # Network Filesystem Server

rebuild and install the kernel.  Upon rebooting, I'm greeted
with a

Jul  6 16:09:41 node16 root: /etc/rc: WARNING: Unable to load 
kernel module nfsserver

Of course, it can't load nfsserver because I don't use modules
nor build them.  So, why is the system trying to load a nfsserver
module?  Because, my /etc/rc.conf contains

nfs_client_enable="YES"
nfs_server_enable="YES"

if I change this to 

nfs_client_enable="YES"
nfsv4_server_enable="YES"

The system no longer tries to load nfsserver upon rebooting.
Unfortunately, this has the effect that no nfsd daemons are
started.  Well, I can start the daemons post-booting.

node16:root[139] /etc/rc.d/nfsd start
Cannot 'start' nfsd. Set nfs_server_enable to YES in /etc/rc.conf or use 'onestart' instead of 'start'.

Whoops.  

-- 
Steve