From owner-freebsd-current  Sat Jul 12 00:11:40 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id AAA23778
          for current-outgoing; Sat, 12 Jul 1997 00:11:40 -0700 (PDT)
Received: from silvia.HIP.Berkeley.EDU (ala-ca32-05.ix.netcom.com [199.35.209.69])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA23773
          for <current@FreeBSD.ORG>; Sat, 12 Jul 1997 00:11:36 -0700 (PDT)
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.6/8.6.9) id AAA00868; Sat, 12 Jul 1997 00:10:48 -0700 (PDT)
Date: Sat, 12 Jul 1997 00:10:48 -0700 (PDT)
Message-Id: <199707120710.AAA00868@silvia.HIP.Berkeley.EDU>
To: jkh@time.cdrom.com
CC: louie@TransSys.COM, current@FreeBSD.ORG, hans@brandinnovators.com
In-reply-to: <3321.868682513@time.cdrom.com> (jkh@time.cdrom.com)
Subject: Re: Heads up and and a call for a show of hands.
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

 * 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.

They are run in alphabetical (actually shell globbing) order -- that's 
why modula-3 installs one with digits in front (you need the shared
libraries to be added before you start cvsupd, for instance).

We're not saying that that is a perfect mechanism, but I have yet to
see a real world example of why it doesn't work.  Besides, we're not
talking about how to handle automatic startup scripts now (we've gone
through that one already) -- it works pretty well for adding shared
library paths, and that's all that this is about.

Satoshi