From owner-freebsd-arch  Mon Mar 26 20:43:30 2001
Delivered-To: freebsd-arch@freebsd.org
Received: from katin.codeconcepts.com (smtz3-038.dfw.tx.bbnow.net [24.219.83.38])
	by hub.freebsd.org (Postfix) with ESMTP id 007BC37B718
	for <freebsd-arch@FreeBSD.ORG>; Mon, 26 Mar 2001 20:43:27 -0800 (PST)
	(envelope-from greg@codeconcepts.com)
Received: from katin.codeconcepts.com (localhost.codeconcepts.com [127.0.0.1])
	by katin.codeconcepts.com (8.11.1/8.11.1) with ESMTP id f2R4eRr88969;
	Mon, 26 Mar 2001 22:40:27 -0600 (CST)
	(envelope-from greg@katin.codeconcepts.com)
Message-Id: <200103270440.f2R4eRr88969@katin.codeconcepts.com>
To: Jack Rusher <jar@integratus.com>
Cc: Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca>,
	Andrew Reilly <areilly@bigpond.net.au>,
	Jordan Hubbard <jkh@osd.bsdi.com>, jonathan@graehl.org,
	freebsd-arch@FreeBSD.ORG
Subject: Re: configuration files, XML? 
Date: Mon, 26 Mar 2001 22:40:06 -0600
From: greg <greg@codeconcepts.com>
Sender: owner-freebsd-arch@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


> > Rather than stand in the way of progress, having the new config file
> > format adopted by most of the major vendors would go a long way to
> > mitigate many fears people have about a new super-config file format.
> 
> We would obviously want everybody to join us in using the new
> configuration format/tools.  I do think somebody needs to belly up to
> the bar and order the first drink, though.
> 
> > Another way we can mitigate these concerns is to support two formats
> > until the other popular UNIX systems (Solaris, AIX, Tru64-UNIX, HP/UX,
> 
> This strikes me as hard for the subsystems that don't have an API in
> place that governs how they access files.  What are some of your ideas
> of how you would do this?


I apologize for not having followed this thread closely enough, but
it seems to reak of AIX/ODM.  If for nothing other than the sake of
completeness, the merits and shortcomings of IBM's solution should be
taken into account.  At the very least it would shed some light onto
the sheer magnitude of such an undertaking.

Greg

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message