From owner-freebsd-hackers  Mon Sep 25 22:54:02 1995
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id WAA13023
          for hackers-outgoing; Mon, 25 Sep 1995 22:54:02 -0700
Received: from ref.tfs.com (ref.tfs.com [140.145.254.251])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id WAA13013
          for <hackers@FreeBSD.ORG>; Mon, 25 Sep 1995 22:53:59 -0700
Received: (from julian@localhost) by ref.tfs.com (8.6.11/8.6.9) id WAA08945; Mon, 25 Sep 1995 22:52:57 -0700
From: Julian Elischer <julian@ref.tfs.com>
Message-Id: <199509260552.WAA08945@ref.tfs.com>
Subject: Re: ports startup scripts
To: patl@asimov.volant.org
Date: Mon, 25 Sep 1995 22:52:56 -0700 (PDT)
Cc: terry@lambert.org, gryphon@healer.com, hackers@FreeBSD.ORG,
        jmb@kryten.atinc.com, peter@taronga.com
In-Reply-To: <9509260253.AA29658@asimov.volant.org> from "patl@asimov.volant.org" at Sep 25, 95 07:53:15 pm
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Content-Length: 656       
Sender: owner-hackers@FreeBSD.ORG
Precedence: bulk


The thing about the old Sunos system (/etc/rc)
was that every time yu added or subtracted a package you contributed to the
entropy in that file..
things got shuffled etc.

with the sysV approach you keep the details hidden in the files and 
the directory is an overview..

I'm sure we can do something similar to both..
the OSF systems (OSF on a PC) I run here use the SYSV
approach.
It's not bad.
 slightly complex but it's good having the symbolic links
in /sbin/rc3.d pointing to /sbin/init.d
it means you can delete the symlink if you don't want it
and the directory gets cleaner..
it's easy to se what's going on at a glance.
and it's easy to undo..