From owner-freebsd-hackers Mon Sep 25 20:51:54 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id UAA09322 for hackers-outgoing; Mon, 25 Sep 1995 20:51:54 -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 UAA09308 for ; Mon, 25 Sep 1995 20:51:48 -0700 Received: from Taronga.COM by UUCP-GW.CC.UH.EDU with UUCP id AA19436 (5.67a/IDA-1.5 for hackers@FreeBSD.ORG); Mon, 25 Sep 1995 22:47:50 -0500 Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id WAA27407 for hackers@FreeBSD.ORG; Mon, 25 Sep 1995 22:42:58 -0500 From: peter@taronga.com (Peter da Silva) Message-Id: <199509260342.WAA27407@bonkers.taronga.com> Subject: Re: ports startup scripts To: hackers@FreeBSD.ORG Date: Mon, 25 Sep 1995 22:42:57 -0500 (CDT) In-Reply-To: <199509251441.KAA12169@healer.com> from "Coranth Gryphon" at Sep 25, 95 10:41:35 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 482 Sender: owner-hackers@FreeBSD.ORG Precedence: bulk > > Ordering guarantees within a single run level/state are hard to provide > > with the single monolithic file model. > Actually, a single file is the easiest to control ordering in. Not if you're adding to it from a script. > Last I checked, line 1 always came before line 2. :-) Yeh, but does "httpd" come before or after "nfsiod"? It's much easier to do "ln -s ../init.d/httpd S95httpd" than to figure out where in the middle of a user-hacked script a command needs to go.