From owner-freebsd-hackers Sat Dec 13 00:29:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA04657 for hackers-outgoing; Sat, 13 Dec 1997 00:29:01 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from word.smith.net.au (ppp5.portal.net.au [202.12.71.105]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA04651 for ; Sat, 13 Dec 1997 00:28:53 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id SAA01759; Sat, 13 Dec 1997 18:53:18 +1030 (CST) Message-Id: <199712130823.SAA01759@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Terry Lambert cc: mike@smith.net.au (Mike Smith), jb@freebsd1.cimlogic.com.au, hackers@freebsd.org Subject: Re: Kernel Config datafile... In-reply-to: Your message of "Sat, 13 Dec 1997 03:21:54 -0000." <199712130321.UAA27603@usr04.primenet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 13 Dec 1997 18:53:17 +1030 From: Mike Smith Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Apollo did it *much* better, and it's beginning to sound like LDAP will > > inherit the mantle. > > Not if it can't do transactions. ... > Really, LDAP is not mature enough at this point, except for embedded > systems where you can guarantee the behaviour of the back end, and > the back end is either not write-cached, or understands the > significance of container objects implicit by hierarchy. What you appear to be saying is that you cannot perform complex atomic transactions, nor are transactions guaranteed to be serialised. There, I did it in two lines. 8) mike