From owner-freebsd-config  Sun Apr 19 16:54:50 1998
Return-Path: <owner-freebsd-config@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id QAA13445
          for freebsd-config-outgoing; Sun, 19 Apr 1998 16:54:50 -0700 (PDT)
          (envelope-from owner-freebsd-config@FreeBSD.ORG)
Received: (from jmb@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id QAA13393;
          Sun, 19 Apr 1998 16:54:38 -0700 (PDT)
          (envelope-from jmb)
From: "Jonathan M. Bresler" <jmb>
Message-Id: <199804192354.QAA13393@hub.freebsd.org>
Subject: Re: (was Discussion : Using DHCP) - Now 'Config Databases'
In-Reply-To: <353A87D5.6F4A8737@tdx.co.uk> from Karl Pielorz at "Apr 20, 98 00:25:09 am"
To: kpielorz@tdx.co.uk (Karl Pielorz)
Date: Sun, 19 Apr 1998 16:54:36 -0700 (PDT)
Cc: config@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-config@FreeBSD.ORG
Precedence: bulk

Karl Pielorz wrote:
> Terry Lambert wrote:
> > If you use an API with get/set semantics, and it does the set as a
> > transaction, then you are not liable to corruption unless your
> > physical media goes bad.
> 
> Ok - granted - Maybe we should be more concerned with 'applications'
> corrupting the database - and if so have a nicer way to correct it (Ok, read
> - 'anyway' to correct it) unlike Windows '95 / NT - in which the registry is
> largely seen as an unindexed black whole...

	more than once i have damaged my computer's configuration
	enough that i was unable to complete booting.
	only being able to edit the flatfiels saved me from having
	to rip out the internal disk and connect that disk to 
	another machine.

	any registry or LDAP database or what have you, needs 
	an ascii "save my ass please" mode.

	without that its a great leap backward into the abyss ;)
jmb

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