From owner-freebsd-current  Fri Jul 11 21:43:05 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id VAA19440
          for current-outgoing; Fri, 11 Jul 1997 21:43:05 -0700 (PDT)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA19430
          for <current@FreeBSD.ORG>; Fri, 11 Jul 1997 21:43:01 -0700 (PDT)
Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.6/8.6.9) with ESMTP id VAA03325; Fri, 11 Jul 1997 21:41:53 -0700 (PDT)
To: "Louis A. Mamakos" <louie@TransSys.COM>
cc: asami@cs.berkeley.edu (Satoshi Asami), current@FreeBSD.ORG,
        hans@brandinnovators.com
Subject: Re: Heads up and and a call for a show of hands. 
In-reply-to: Your message of "Fri, 11 Jul 1997 23:51:36 EDT."
             <199707120351.XAA18977@whizzo.TransSys.COM> 
Date: Fri, 11 Jul 1997 21:41:53 -0700
Message-ID: <3321.868682513@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> I've used it locally to handle [incr tcl] which is installed in a different
> location and it sure beats having to edit a file, etc.  And using the
> /usr/local/etc/rc.d script, you can invoke arbitrary policy (see if a
> directory that might be on removable media exists, etc) before adding
> directories to the list.

Heh - actually, I also forgot to mention that the whole rc.d script
thing has some inherent limitations as currently implement: What if,
for example, you require that certain initialization be done in a
given order?  Not at all a far-fetched scenario.

					Jordan