From owner-freebsd-hackers Fri Dec 12 08:22:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA01438 for hackers-outgoing; Fri, 12 Dec 1997 08:22:49 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from webserver.smginc.com (webserver.smginc.com [204.170.176.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA01413 for ; Fri, 12 Dec 1997 08:22:35 -0800 (PST) (envelope-from AdamT@smginc.com) Received: from smginc.com ([204.170.177.4]) by webserver.smginc.com (post.office MTA v2.0 0813 ID# 0-13723) with SMTP id AAA279; Fri, 12 Dec 1997 11:24:33 -0500 Received: by smginc.com with Microsoft Mail id <34918F3E@smginc.com>; Fri, 12 Dec 97 11:23:42 PST From: Adam Turoff To: "'jkh@time.cdrom.com'" , "'j_mini@efn.org'" Cc: "'freebsd-hackers@FreeBSD.ORG'" Subject: Kernel Config datafile... Date: Fri, 12 Dec 97 11:22:00 PST Message-ID: <34918F3E@smginc.com> Encoding: 12 TEXT X-Mailer: Microsoft Mail V3.0 Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I don't want to start a flame war here, but I've heard the topic of a configuration file that needed to be both ASCII and vi/emacs editable as well as store relational data as well. Allow me to spread the evangelism a wee tad and mention SGML/XML. This would give the advantage of encoding multiple aspects of the kernel config data in a single ASCII (technically, Unicode) file. -- Adam.