From owner-freebsd-current Tue Feb 26 23:13:31 2002 Delivered-To: freebsd-current@freebsd.org Received: from mail.tgd.net (mail.tgd.net [209.81.25.10]) by hub.freebsd.org (Postfix) with ESMTP id 956E337B402 for ; Tue, 26 Feb 2002 23:13:25 -0800 (PST) Received: by mail.tgd.net (Postfix, from userid 1001) id C677B20F07; Tue, 26 Feb 2002 23:13:24 -0800 (PST) Date: Tue, 26 Feb 2002 23:13:24 -0800 From: Sean Chittenden To: Kevin Way Cc: current@freebsd.org Subject: Re: NetBSD-style rc.d Project Message-ID: <20020226231324.A57917@ninja1.internal> References: <20020226051811.K52727@blossom.cjclark.org> <20020226191104.A55023@ninja1.internal> <20020227053942.B91597@bean.overtone.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020227053942.B91597@bean.overtone.org>; from "kevin.way@overtone.org" on Wed, Feb 27, 2002 at = 05:39:42AM X-PGP-Key: 0x1EDDFAAD X-PGP-Fingerprint: C665 A17F 9A56 286C 5CFB 1DEA 9F4F 5CEF 1EDD FAAD X-Web-Homepage: http://sean.chittenden.org/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > I'm about to dive into doing some work for an rc system for the ports > > (${PREFIX}/etc/defaults && ${PREFIX}/etc/rc.conf) and have an interest > > in learning about the way they've done things. Does their paradigm > > completely obsolete the rc.conf concept? Were there any docs/project > > pages regarding the RC effort that I could peruse for ideas? -sc > > No, the NetBSD paradigm doesn't obsolete the rc.conf concept at all, > in fact rc.conf is still used in a functionally identical manner, though > NetBSD and FreeBSD don't share a common set of variables for the file. Very cool. [snip] > The NetBSD rc.d rystem is a wonderfully simple concept. Instead of > having a large rc script, that's hard to modify programmatically, > you have a a collection of small scripts, each of which contains a > line stating what it provides, and what it requires. An external > program, rcorder, parses these small scripts, takes the PROVIDE and > REQUIRE lines, and performs a topological sort, thus making it much > easier to be assured that services are started in the proper order, > and that all dependancies are fulfilled. Even more cool. > Please, please, please, do not make yet another attempt to expand > the scope of the project into something which will not be easily > implemented and accepted. No problems there: I only want to get a way to distribute an rc.conf to all systems and have it configure the optionally installed ports on the various systems. Beyond that, I'm not going to touch anything that deals with /etc/rc.conf and friends: I was only wondering if they'd implemented a new paradigm for rc scripts or found some way of starting up programs/services that was worth noting: it doesn't sound too radical, but rcorder does sound very interesting and sounds like something to play with. Thanks for the site and info, I'll hopefully come back with some useful patches. -sc -- Sean Chittenden To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message