Date: Mon, 18 May 1998 14:09:29 -0400 (EDT) From: Dan Janowski <danj@3skel.com> To: "Jordan K. Hubbard" <jkh@time.cdrom.com> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: system config database... Message-ID: <Pine.BSF.3.96.980518140136.22495F-100000@fnur.3skel.com> In-Reply-To: <28192.895513853@time.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
About 90% of what has to get done at startup is a simple invocation with dependancies and order being the only constraints. These can be encapsulated in a configuration. There are a few things that are too arbitrary, mostly cleanup stuff like ptmp, and vi -r. Those things seem better in their own scripts, no? For these purposes, the meta-file could call a script just as easily as anything else. Dan On Mon, 18 May 1998, Jordan K. Hubbard wrote: > > It seems that there still a need for a per service > > set of scripted instruction for startup. > > I'm not arguing that at all, I'm simply saying that the current system > needlessly separates the configuration data from the actions > associated with it. It's like having a shopping list where on one > side you have "items to get: 1, 3, 2, 6, 9 and 5" and on the other you > have "1 = milk, 2 = celery, 3 = ..." :-) > > The information needs to be combined and sh unfortunately isn't really > "expressive" enough for that - a metaformat which gets compiled into > sh or is even run by some sort of helper program, e.g. /etc/rc becomes > a one liner: > > /sbin/systemrc /etc/rc.sys > > > An /etc/rc.d with mini-scripts for features. Some > > Ick, no, wrong direction again! ;-) > -- 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980518140136.22495F-100000>