From owner-freebsd-hackers  Thu Sep 28 18:50:28 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id SAA13058
          for hackers-outgoing; Thu, 28 Sep 1995 18:50:28 -0700
Received: from UUCP-GW.CC.UH.EDU (root@UUCP-GW.CC.UH.EDU [129.7.1.11])
          by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id SAA13052
          for <hackers@freebsd.org>; Thu, 28 Sep 1995 18:50:25 -0700
Received: from Taronga.COM by UUCP-GW.CC.UH.EDU with UUCP id AA24678
  (5.67a/IDA-1.5 for hackers@freebsd.org); Thu, 28 Sep 1995 20:47:52 -0500
Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id UAA20335 for hackers@freebsd.org; Thu, 28 Sep 1995 20:22:43 -0500
From: peter@taronga.com (Peter da Silva)
Message-Id: <199509290122.UAA20335@bonkers.taronga.com>
Subject: Re: ports startup scripts
To: hackers@freebsd.org
Date: Thu, 28 Sep 1995 20:22:42 -0500 (CDT)
In-Reply-To: <199509281423.KAA24338@healer.com> from "Coranth Gryphon" at Sep 28, 95 10:23:40 am
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Content-Length: 683       
Sender: owner-hackers@freebsd.org
Precedence: bulk

> We can only avoid editing files so much. Password files, inetd.conf, services.
> These have to be editied, or we have to throw them out and replace them
> with another model. At some point, you either have to allow auto-editing
> of system files, or just leave some stuff to hand-configuration.

inetd.conf and services don't need to be auto-edited. You auto-generate them
based on the templates in /etc/packages/*/inetd.conf and .../services. 

You will have to remember to edit /etc/packages/*/inetd.conf instead of
inetd.conf itself if you need to tune it. Most people don't.

The only file I can think of that can't be done this way without a lot of
pain is /etc/master.passwd