From owner-freebsd-hackers Mon May 18 15:15:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA19444 for freebsd-hackers-outgoing; Mon, 18 May 1998 15:15:47 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [148.81.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA19316 for ; Mon, 18 May 1998 15:15:10 -0700 (PDT) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.8.8/8.8.5) with SMTP id AAA00940; Tue, 19 May 1998 00:16:54 +0200 (CEST) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Tue, 19 May 1998 00:16:54 +0200 (CEST) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: "Jordan K. Hubbard" cc: Dan Janowski , freebsd-hackers@FreeBSD.ORG Subject: Re: system config database... In-Reply-To: <28331.895515604@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 On Mon, 18 May 1998, Jordan K. Hubbard wrote: > If you're going to offer one-stop shopping then you need to just toss > an umbrella over it all. The proliferation of little scripts which > "just don't quite fit" into the overall framework is what makes > debugging a system startup failure such a bear on the more complex > rc.d-using systems and what we want to avoid. You want to think of > the entire startup process, from init's first gasp to the very last > "rc.local" type of action, as a single system with a decent API for > adding, deleting and editing the objects it manages. I'll put my 0.02pln into this: I've been thinking lately about something similar, in light of recent discussions on building a FreeBSD-based router box... One can argue for or against the Cisco IOS interface, but it has exactly this feature: all configuration is stored in just one file, and even though you don't edit it directly, it's still readable... It would be great to have something like this _instead_ of the whole /etc. As it is now, it's a nightmare for any tool to build consistent config files from user-supplied parameters - it needs to parse, edit, re-create several config files, each with it's own different syntax... Also, current scheme is inefficient IMHO (especially when system is low on memory) - each script starts a shell... Anyway, if you go in the direction of single config file, I'm with you... :-) Andrzej Bialecki --------------------+--------------------------------------------------------- abial@nask.pl | if(halt_per_mth > 0) { fetch("http://www.freebsd.org") } Research & Academic | "Be open-minded, but don't let your brains to fall out." Network in Poland | All of the above (and more) is just my personal opinion. --------------------+--------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message