From owner-freebsd-current  Thu Dec 28 14:13:23 1995
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id OAA03929
          for current-outgoing; Thu, 28 Dec 1995 14:13:23 -0800 (PST)
Received: from linus.demon.co.uk (linus.demon.co.uk [158.152.10.220])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA03924
          for <current@FreeBSD.ORG>; Thu, 28 Dec 1995 14:13:12 -0800 (PST)
Received: (from mark@localhost) by linus.demon.co.uk (8.7.3/8.7.3) id VAA01984; Thu, 28 Dec 1995 21:26:23 GMT
Message-Id: <199512282126.VAA01984@linus.demon.co.uk>
From: mark@linus.demon.co.uk (Mark Valentine)
Date: Thu, 28 Dec 1995 21:26:22 +0000
In-Reply-To: "Jordan K. Hubbard"'s message of Dec 27, 11:08pm
X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95)
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Subject: Re: pcnfsd..
Cc: current@FreeBSD.ORG
Sender: owner-current@FreeBSD.ORG
Precedence: bulk

> From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
> Date: Wed 27 Dec, 1995
> Subject: Re: pcnfsd..

> Sigh.  It's really annoying that we can't just bundle gated.

This might be handled as a special "would-be-in-the-base-system-if-we-could-
do-it" package class, rather than a straight "port".

Include all the hooks and configuration knobs for it, with the instructions
for obtaining and installing it supplied with the base system.  (Note: this
class of package probably shouldn't touch /usr/local by default; ideally, as
"almost" part of the base system, it shouldn't require the administrator to
subscribe to the "ports" way of doing things.)

> And what do you say about pcnfsd, which perturbs the starting of
> mountd?  Should we bring it in and keep our exposure down to one
> port?

I like the way you have it now, with a (sort of) general-purpose knob in
sysconfig to tweak the behaviour of the base system.  Add-on packages might
be taught to know about such knobs, and either instruct the administrator
to turn it on, or offer to turn it on for him.

		Mark.