From owner-freebsd-hackers Sun Sep 24 07:49:15 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id HAA29050 for hackers-outgoing; Sun, 24 Sep 1995 07:49:15 -0700 Received: from UUCP-GW.CC.UH.EDU (root@UUCP-GW.CC.UH.EDU [129.7.1.11]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id HAA29045 for ; Sun, 24 Sep 1995 07:49:08 -0700 Received: from Taronga.COM by UUCP-GW.CC.UH.EDU with UUCP id AA05504 (5.67a/IDA-1.5 for hackers@freebsd.org); Sun, 24 Sep 1995 09:48:08 -0500 Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id JAA09429 for hackers@freebsd.org; Sun, 24 Sep 1995 09:34:56 -0500 From: peter@taronga.com (Peter da Silva) Message-Id: <199509241434.JAA09429@bonkers.taronga.com> Subject: Re: ports startup scripts To: hackers@freebsd.org Date: Sun, 24 Sep 1995 09:34:56 -0500 (CDT) In-Reply-To: from "Jonathan M. Bresler" at Sep 24, 95 09:13:56 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1830 Sender: owner-hackers@freebsd.org Precedence: bulk > solves the rename problem. not the 'is it the same of is it not, > i have to did deeper' problem. Sure. If you do it right you just need to make sure it's a symlink. > startup and shutdown are inherently complicated with strict order > dependencies (eg mount, nfs, ifconfig, routing, ......) That's why the file names start with a number. > a single file (that may well invoke others to do the work) serves > as a clear outline of the startup/shutdown process. So does a directory. > should, but you question consistency and ability of those > writing install scripts. same question applies to files, contents, and > filenames. But those are easy: In /etc/daily: find /etc/rc*.d -type f -print > /tmp/$$ if [ ! -s /tmp/$$ ] then echo "Warning... files in /etc/rc.d" cat /tmp/$$ fi rm /tmp/$$ > i expect the ports-meister and packages-master to enforce that > level of consistency. You're assuming that only official ports are going to use this. Bad assumption. > > (If I had my druthers I'd have an /etc/inetd.d as well) > no master file?? what executes the individual files and > determines the order of execution....ascii sort order in a shell script? Yes. > thats a master file which is generated on the fly. Yes. Your point being? > and must rely on > numerics to determine execution order rather than names. (eg 67 vs > named, we could use 67named, at least. Exactly. That's precisely what System V does. Actually, it has: S67named K45named So you can have different startup/shutdown orders. I don't know that's necessary. > master file could be a shell script, but in place of ascii sort > order, a shell variable and a 'for x in $daemons' loop. That's not a master file that has to be edited. > (are we much closer to agreement than i realize?) I suspect so.