From owner-freebsd-ports  Mon Sep 25 16:07:16 1995
Return-Path: owner-ports
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id QAA28644
          for ports-outgoing; Mon, 25 Sep 1995 16:07:16 -0700
Received: from rocky.sri.MT.net (sri.MT.net [204.94.231.129])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id QAA28617
          ; Mon, 25 Sep 1995 16:07:07 -0700
Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id RAA12073; Mon, 25 Sep 1995 17:09:11 -0600
Date: Mon, 25 Sep 1995 17:09:11 -0600
From: Nate Williams <nate@rocky.sri.MT.net>
Message-Id: <199509252309.RAA12073@rocky.sri.MT.net>
To: Terry Lambert <terry@lambert.org>
Cc: kelly@fsl.noaa.gov (Sean Kelly), freebsd-hackers@FreeBSD.ORG,
        freebsd-ports@FreeBSD.ORG
Subject: Re: ports startup scripts
In-Reply-To: <199509252251.PAA06113@phaeton.artisoft.com>
References: <9509252244.AA11640@emu.fsl.noaa.gov>
	<199509252251.PAA06113@phaeton.artisoft.com>
Sender: owner-ports@FreeBSD.ORG
Precedence: bulk

Terry Lambert writes:
> >     Terry> If /etc is read-only, well, then you're SOL.
> > 
> > But the more experienced user who's given himself a read-only /etc
> > should know what to do.
> 
> But the more experienced user who's manually manipulating the startup
> and cron directories instead of using an administrative tool should
> know what to do.

No way, no how.  I've been adminstering BSD systems for years and years,
and I still have problems on SysV boxes trying to find things.

Your way requires change (ie; more work), while Sean is arguing for the
less work case.  The average FreeBSD user won't gain anything with the
change (asserting that the Desktop is lost), so why give ourselves more
work being different just to be different?


Nate