From owner-freebsd-hackers Mon May 18 10:15:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA16106 for freebsd-hackers-outgoing; Mon, 18 May 1998 10:15:11 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from aaka.3skel.com (aaka.3skel.com [207.240.212.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA16049 for ; Mon, 18 May 1998 10:14:50 -0700 (PDT) (envelope-from danj@3skel.com) Received: from fnur.3skel.com (fnur.3skel.com [192.168.0.8]) by aaka.3skel.com (8.8.5/8.8.2) with ESMTP id NAA07506; Mon, 18 May 1998 13:14:51 -0400 (EDT) Received: from localhost (danj@localhost) by fnur.3skel.com (8.8.8/8.8.2) with SMTP id NAA22771; Mon, 18 May 1998 13:14:50 -0400 (EDT) Date: Mon, 18 May 1998 13:14:50 -0400 (EDT) From: Dan Janowski To: "Jordan K. Hubbard" cc: freebsd-hackers@FreeBSD.ORG Subject: Re: system config database... In-Reply-To: <27848.895508536@time.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is in line with my current thinking. As sick as this may sound, it will be a little smit-ish (ever use AIX?). Me thinks the major parsing and generation of directives (what should happen next) should not be shell based; too hazardous. It seems that there still a need for a per service set of scripted instruction for startup. An /etc/rc.d with mini-scripts for features. Some similarites with SysV, but with out rc2.d rc1.d. Encapsulation and easy interface to the meta-data through a static binary that will run the boot process, allow for general queries and updates. It would be an atomic replacement for the current rc stuff, but not to spell a dead end for the old way, as you suggest. Dan On Mon, 18 May 1998, Jordan K. Hubbard wrote: [snip] > (generally) be expected to edit it directly but rather use one or more > browsing tools for displaying and editing each "startup object" in a > friendlier form, that perhaps looking something like this: > > name: amd > desc: The Auto Mount Daemon for NFS filesystems. > enabled: no > class: net > order: 9 > requires: is_enabled nfs_client && is_enabled network > v_exec: amd > v_flags: -a /net -c 1800 -k i386 -d ${domain} -l syslog /host /etc/amd.map > command: ${v_exec} ${v_flags} > > The attribute names are somewhat contrived, but basically you want > each startup entity to be something which describes itself (thus > eliminating the grotty in-line comments in /etc/rc.conf) and gives you [snip] -- danj@3skel.com Dan Janowski Triskelion Systems, Inc. Bronx, NY To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message