Date: Tue, 27 Mar 2001 11:20:49 -0800 From: Jordan Hubbard <jkh@osd.bsdi.com> To: DougB@DougBarton.net Cc: freebsd-arch@FreeBSD.ORG Subject: Re: configuration files Message-ID: <20010327112049F.jkh@osd.bsdi.com> In-Reply-To: <3AC06153.EEBF632E@DougBarton.net> References: <20010327081943.EE95A37B718@hub.freebsd.org> <20010327004317J.jkh@osd.bsdi.com> <3AC06153.EEBF632E@DougBarton.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> Can someone please, just for fun, define the actual _problem_ you're trying > to solve. All I've seen so far are solutions [sic], but no real good > definition of the goals you're trying to achieve. Without this, continuing > to talk about solutions is futile. I think the "problem" is pretty obvious, Doug. We have a whole bunch of system and application configuration data living in /etc and a few other places. Almost every configuration file has its own unique format and set of rules about how you're supposed to edit it or what utility (foo_mkdb) you're supposed to run after editing it so that its backing database, if it has one, is updated. It is, in short, a highly ad-hoc system which has evolved over time rather than benefitting from a single coherent design strategy. Somehow retrofitting a single coherent design strategy into this mess without pissing off all the legacy people *is* the goal people are discussing here. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010327112049F.jkh>