From owner-freebsd-current Sun Jul 4 12:25:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 37DC014EA2 for ; Sun, 4 Jul 1999 12:25:44 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.8.8) with ESMTP id MAA18980 for ; Sun, 4 Jul 1999 12:25:22 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199907041925.MAA18980@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-current@FreeBSD.ORG Subject: LDAPed FreeBSD Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 04 Jul 1999 12:25:22 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am playing around with configuring the system and providing a CLI , programmatic interface and a html interface . Floating in my mind is to present a uniform configuration repository similar to windows registery however the information repository is implemented with LDAP. See http://www.openldap.org for info on LDAP. The tough part is creating the LDAP schemas for the various daemons or services. Got lucky and found an IETF draft : An LDAP Schema for Dynamic Host Configuration Protocol Service http://www.ietf.org/internet-drafts/draft-gu-dhcp-ldap-schema-00.txt I am using the above draft to explore configuring dhcpd. My first cut at configuring dhcpd via LDAP is to extract all the configuration information from the LDAP server and writing the information to dhcpd's configuration file and then have dhcpd parse the configuration file. This approach minimizes the changes to dhcpd and provides persistent configuration information for dhcpd. The start of my html interface is at: http://www.star-gate.com/dhcpd.html Thats just a dummy front end . The real interface is being implemented as a servlet and will provide a more rich presentation --- help files , How To, etc... The CLI interface can be as easy as using the existing ldap shell tools. The programmatic interface is simply the LDAP C and Java interface available from : http://www.mozilla.org/directory So far I have a simple ldap schema based upon the IETF draft which I can manage from my servlet and query from dhcpd. What do you guys think? -- Amancio Hasty ahasty@mindspring.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message