From owner-freebsd-arch Fri Apr 6 8:19:37 2001 Delivered-To: freebsd-arch@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id E6E2037B43F for ; Fri, 6 Apr 2001 08:19:32 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from [127.0.0.1] (helo=softweyr.com ident=241abc72570a024ff9ff8064a8756d93) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 14lY0F-000060-00; Fri, 06 Apr 2001 09:18:23 -0600 Message-ID: <3ACDDE3E.79BBBDAC@softweyr.com> Date: Fri, 06 Apr 2001 09:18:22 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Andrew Reilly Cc: Jack Rusher , jonathan@graehl.org, freebsd-arch@FreeBSD.ORG Subject: Re: configuration files, XML, Mac OS X release References: <20010325170513Z.jkh@osd.bsdi.com> <3ABEB519.CA9F1029@integratus.com> <20010326181443.A75840@gurney.reilly.home> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrew Reilly wrote: > > On Sun, Mar 25, 2001 at 07:18:49PM -0800, Jack Rusher wrote: > > Jordan Hubbard wrote: > > > > > > The project has a Mac (eatmorepie.freebsd.org) running the OS X > > > release candidate, though it appears to be down at the moment (I'll > > > fix that). Someone can certainly log into it at some point and > > > look this stuff over. > > > > I took a look at the release during the big pre release party at > > Apple. It looks like the only XML DTD they have in the system is a > > property list DTD designed to allow them to store groups of key/value > > pairs as the backing store for application configuration data. > > > > I remain willing to help integrate a lightweight BSD license XML based > > configuration management system into FreeBSD. Does anybody really want > > such a beast? > > I really like the idea of a uniform and configurator-friendly > config management system. I'm not crazy about XML, but my > opinion on the subject hardly matters. The problem with XML is that it is an entirely adequate language to export to and import from, but quite ugly to store in, since every setting is arbitrarily long. This isn't much different from what we have now, with rc.conf et al, but we don't really edit the existing script files programmatically. In order to change a setting using XML, you end up parsing the entire file, changing the setting in-memory, then re-writing the file, which is less than elegant. I'd sure like to see us come up with a better solution before plunging off down this path. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message