From owner-freebsd-current  Wed Jul 26 04:57:51 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.11/8.6.6) id EAA17097
          for current-outgoing; Wed, 26 Jul 1995 04:57:51 -0700
Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181])
          by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id EAA17090
          for <current@freebsd.org>; Wed, 26 Jul 1995 04:57:49 -0700
Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.6.11/8.6.9) id EAA10190; Wed, 26 Jul 1995 04:57:37 -0700
Date: Wed, 26 Jul 1995 04:57:37 -0700
Message-Id: <199507261157.EAA10190@silvia.HIP.Berkeley.EDU>
To: jkh@time.cdrom.com
CC: wollman@halloran-eldar.lcs.mit.edu, rgrimes@gndrsh.aac.dev.com,
        current@freebsd.org
In-reply-to: <29101.806726032@time.cdrom.com> (jkh@time.cdrom.com)
Subject: Re: Knobs in /etc/sysconfig
From: asami@cs.berkeley.edu (Satoshi Asami)
Sender: current-owner@freebsd.org
Precedence: bulk

 * > 	if [ -d /etc/rc.local.d ]; then
 * > 		for script in /etc/rc.local.d/*.sh; do
 * > 			[ -x $script ] && $script start
 * > 		done
 * > 	fi

 * I can live with that..  I read Satoshi's "all singing, all dancing"
 * proposal and have to say that this mechanism looks more reasonable,
 * albeit less flexible.  I'm usually all for flexibility, but it's
 * possible to take it too far (like I did with bsd.port.mk :-).

This isn't any different from my proposal as far as I can tell, except
that everything gets started in one chunk.  If there is one place in
the bootup sequence that we can reliably start all the ports stuff,
that's all fine for me.

Satoshi