From owner-freebsd-hackers Mon Nov 30 23:44:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA27005 for freebsd-hackers-outgoing; Mon, 30 Nov 1998 23:44:22 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA26994 for ; Mon, 30 Nov 1998 23:44:20 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id XAA03898; Mon, 30 Nov 1998 23:43:55 -0800 (PST) (envelope-from dillon) Date: Mon, 30 Nov 1998 23:43:55 -0800 (PST) From: Matthew Dillon Message-Id: <199812010743.XAA03898@apollo.backplane.com> To: ADRIAN Filipi-Martin Cc: Dan Busarow , Eivind Eklund , hackers@FreeBSD.ORG Subject: Re: System V init (was: Linux to be deployed in Mexican schools; Where was FreeBSD?) References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :> get set? I don't recognize that as a shell builtin. : : : $(command) == `command` : : $() is the POSIX way and a lot less prone for confusion with the :single quote. : : Adrian :-- :[ adrian@ubergeeks.com -- Ubergeeks Consulting -- http://www.ubergeeks.com/ ] Not to detract from the other threads I'm trying to push commits through, but... oh damn, I just can't pass it up: Why not organize an RC system based on the specification of a set of dependancies? For example, require a '#DEPENDS/RETURNS' line (or equivalent) in the first 2 lines of each rc file. ---- some rc.xxx file ---- #!/bin/sh #DEPENDS(network,sendmail,...) RETURNS(atm) # ... -------------------------- Forget trying to sort RC files, rc.conf would have a variable that specifies a list of rc files and directories and the rc script figures out the dependancy tree and executes the RC files from there, in the appropriate order based on the dependancies and exit codes. It could even run non-conflicting RC files in parallel, now wouldn't that be cool! /etc/rc would be somewhat more complex (or we could write a C program to run through the dependancy list), but that's all hidden from the user. The user simply plops down his RC script with a reasonable DEPENDS and RETURNS directive on line #2 and the system does the rest. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message