From owner-freebsd-current Tue Jul 25 19:34:56 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.11/8.6.6) id TAA27571 for current-outgoing; Tue, 25 Jul 1995 19:34:56 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.cdrom.com (8.6.11/8.6.6) with ESMTP id TAA27560 for ; Tue, 25 Jul 1995 19:34:53 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.11/8.6.9) with SMTP id TAA29103; Tue, 25 Jul 1995 19:33:52 -0700 To: Garrett Wollman cc: "Rodney W. Grimes" , current@freebsd.org Subject: Re: Knobs in /etc/sysconfig In-reply-to: Your message of "Tue, 25 Jul 1995 10:19:38 EDT." <9507251419.AA06573@halloran-eldar.lcs.mit.edu> Date: Tue, 25 Jul 1995 19:33:52 -0700 Message-ID: <29101.806726032@time.cdrom.com> From: "Jordan K. Hubbard" Sender: current-owner@freebsd.org Precedence: bulk > If you're going to go this far in the SysV direction (and in this one > particular case it's not unreasonable), I would far rather have > something like: > > if [ -d /etc/rc.local.d ]; then > for script in /etc/rc.local.d/*.sh; do > [ -x $script ] && $script start > done > fi > > if [ -x /etc/rc.local ]; then > /etc/rc.local > 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 :-). > I don't like the idea of /etc/sysconfig.local as a dumping-ground for > third-party software configuration options. Either there should be a > third-party section in the real /etc/sysconfig, or there should be a > separate config file for each service (/etc/rc.local.d/$service.cf?). > I lean towards the former. I can live with this too. Unless I hear some significant argument to the contrary, I will "make it so" in a day or so.. Jordan