From owner-freebsd-hackers Thu Mar 19 17:27:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA18730 for freebsd-hackers-outgoing; Thu, 19 Mar 1998 17:27:21 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA18678; Thu, 19 Mar 1998 17:27:02 -0800 (PST) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id RAA19653; Thu, 19 Mar 1998 17:26:42 -0800 (PST) (envelope-from jkh@time.cdrom.com) To: Dan Janowski cc: eivind@yes.no, FreeBSD-Hackers@FreeBSD.ORG, jkh@FreeBSD.ORG, Studded@dal.net Subject: Re: Discussion about script to update /etc, etc. In-reply-to: Your message of "Thu, 19 Mar 1998 19:44:25 EST." <199803200044.TAA04352@fnur.3skel.com> Date: Thu, 19 Mar 1998 17:26:42 -0800 Message-ID: <19649.890357202@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > By what do we mean template based? I have a running M4 based > system that does rc.conf, uucp, ppp, and a bunch of other crap. > I have also (a long time ago) made a mechanism oriented around > a /etc/config directory similar to the IRIX 'chkconfig' > mechanism. That's one way - I'm basically thinking of a system that will allow you, for each given entity, to specify: 1. A documentation string for it. 2. An enable bit ("am I enabled?") 3. One or more commands and their arguments to run when the feature is enabled. 4. The default setting for the feature if not set. 5. Any other entities this one depends on (so you can not enable feature z if x and y are not). Whether that's done with m4 or something more complex is up to the implementor. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message