From owner-freebsd-hackers Sat Sep 23 06:18:52 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id GAA03396 for hackers-outgoing; Sat, 23 Sep 1995 06:18:52 -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 GAA03391 for ; Sat, 23 Sep 1995 06:18:48 -0700 Received: from Taronga.COM by UUCP-GW.CC.UH.EDU with UUCP id AA29164 (5.67a/IDA-1.5 for hackers@freebsd.org); Sat, 23 Sep 1995 08:02:54 -0500 Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id HAA16496 for hackers@freebsd.org; Sat, 23 Sep 1995 07:45:22 -0500 From: peter@taronga.com (Peter da Silva) Message-Id: <199509231245.HAA16496@bonkers.taronga.com> Subject: Re: ports startup scripts To: hackers@freebsd.org Date: Sat, 23 Sep 1995 07:45:21 -0500 (CDT) In-Reply-To: <199509230324.XAA05317@healer.com> from "Coranth Gryphon" at Sep 22, 95 11:24:00 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1495 Sender: owner-hackers@freebsd.org Precedence: bulk > But keeping a set of directories for the sole purpose of linking > to one common directory is hellishly redundant. It's just like /usr/share/zoneinfo. And no, it's not "hellishly redundant". It's actually very convenient. Much more so than referencing via a file: + Adding or deleting a script can be done without editing a file. + Files accumulate cruft. There's always a temptation to put more than a script name in there. And the benefit over just having the run-level directories is it makes it convenient to start up or shut down a single service. SVR2 didn't have the common directory. I don't think SVR3 did, either. It was very nice when they added it. I'm not going to cry if it's not implemented, but it's not a monstrosity. > Original issue: What do we allow ports and packages to modify? Answer: We let them put a file in a directory. > SysV uses a combination of 2 and 4 (inittab plus dirs). Inittab provides additional services which are currently provided by ttys. It would be nice to make ttys run-level-aware, but I don't think that's vital. It'd be nice... > This is the "how much of /etc/rc" do I implement. > On going up, run anything <= level with argument "start". > On going down, run anything > level with argument "stop". You may need separate start and stop entries because the order of execution may be important and not always obvious. Putting start and stop in the same directory is nice, but make sure you run the stops in reverse order at least.