From owner-freebsd-chat Thu Oct 2 09:48:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA07717 for chat-outgoing; Thu, 2 Oct 1997 09:48:38 -0700 (PDT) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA07706 for ; Thu, 2 Oct 1997 09:48:30 -0700 (PDT) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.7/8.8.7) with SMTP id LAA00750; Thu, 2 Oct 1997 11:48:09 -0500 (EST) Date: Thu, 2 Oct 1997 11:48:08 -0500 (EST) From: John Fieber To: Troy Settle cc: chat@FreeBSD.ORG Subject: Re: SQL Interface - very wild idea (WAS: Browser interface) In-Reply-To: <199710021253.IAA10563@radford.i-plus.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-chat@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 2 Oct 1997, Troy Settle wrote: > Having an extensible SQL/ODBC system would be ideal for both local and > network configuration, user management, etc... The only drawback, would be ... > - a user's database could be used for many things, password files, access > logs (local, radius, etc). This would be especially useful in an ISP or > academic environment. > - a host database could be used for local configuration information > (fstab, host info, dns info, network database info, manpath, checksums, > etc...) > - a network database, consisting of all your hosts' databases and more, > could be used to keep all your network configurations handy and in order Isn't this more or less the sort of thing LDAP is designed to address? -john