From owner-freebsd-hackers Sat Apr 18 01:34:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA24818 for freebsd-hackers-outgoing; Sat, 18 Apr 1998 01:34:37 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA24811 for ; Sat, 18 Apr 1998 08:34:33 GMT (envelope-from tlambert@usr01.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id BAA22379; Sat, 18 Apr 1998 01:34:27 -0700 (MST) Received: from usr01.primenet.com(206.165.6.201) via SMTP by smtp01.primenet.com, id smtpd022355; Sat Apr 18 01:34:19 1998 Received: (from tlambert@localhost) by usr01.primenet.com (8.8.5/8.8.5) id BAA08866; Sat, 18 Apr 1998 01:34:11 -0700 (MST) From: Terry Lambert Message-Id: <199804180834.BAA08866@usr01.primenet.com> Subject: Re: Discussion : Using DHCP to obtain configuration. To: mike@smith.net.au (Mike Smith) Date: Sat, 18 Apr 1998 08:34:11 +0000 (GMT) Cc: cshenton@it.hq.nasa.gov, mike@smith.net.au, archie@whistle.com, hackers@FreeBSD.ORG In-Reply-To: <199804171907.MAA00403@dingo.cdrom.com> from "Mike Smith" at Apr 17, 98 12:07:49 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > The way UNIX piles random configuration information all into /etc > > > > has always bugged the crap out of me. Ideally, /etc should go away > > > > because nothing should be "miscellaneous".. it should all be organized. > > > > > > ... in a database. Go visit Terry's cube tomorrow. Say "LDAP?" and > > > wait for the lecture. Apparently Mike has spies everywhere... 8-). > > No, not just any database -- a "registry"! :-) > > Yeah, and? Ask anyone that's administered a network of Apollo systems > how useful the registry is. > > > (shudder, cringe, vomit) > > Isn't it nice to have your ideas judged on the merits of someone else's > implementation? What's even better is when they start pointing at the things that some idiot in his wisdom decided to store in the other implementations key values, and assume that the content is a result of the technology being fundamentally flawed as opposed to blaming the idiot for a poor schema definition. 8-). FreeBSD *does* have a schema *right now*. It's just not documented anywhere, and it's not in third normal form, so there is data duplication, and modifying data doesn't transparently cause everything that depends upon the value of the data to "do the right thing" (wouldn't it be nifty if you chould change your IP address, and not care that it had changed because you knew that all daemons bound to the altered interface would just "do the right thing"?). Basically, it's a big cache coherency problem; all the data that gets changed and results in the wrong thing happening is "cached" in the program doing the wrong thing. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message