From owner-freebsd-chat Thu Oct 2 05:56:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA23844 for chat-outgoing; Thu, 2 Oct 1997 05:56:46 -0700 (PDT) Received: from radford.i-plus.net (root@Radford.i-Plus.net [206.99.237.6]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA23839 for ; Thu, 2 Oct 1997 05:56:44 -0700 (PDT) Received: from totally.nutty.net (insane@totally.nutty.net [206.99.237.44]) by radford.i-plus.net (8.8.6/8.8.5) with SMTP id IAA10563 for ; Thu, 2 Oct 1997 08:53:40 -0400 (EDT) Message-Id: <199710021253.IAA10563@radford.i-plus.net> Reply-To: "Troy Settle" From: "Troy Settle" To: Subject: SQL Interface - very wild idea (WAS: Browser interface) Date: Thu, 2 Oct 1997 09:01:27 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1008.3 X-MimeOle: Produced By Microsoft MimeOLE Engine V4.71.1008.3 Sender: owner-freebsd-chat@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Maybe my mind if fried from going too long without sleep, but... Just minutes before reading Pete's post about using a database look-alike for system administration, I was thinking that a pure database for all system configuration would be quite interesting. Similar to the Windows registry. Having an extensible SQL/ODBC system would be ideal for both local and network configuration, user management, etc... The only drawback, would be the loss of simple text configurations that could be edited with a simple editor, but by moving slowly and carefully, we could end up with command line, curses, X, and web interfaces that will all work in a very similar way, providing easy access to various databases: - 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 Basically, it comes down to the fact that if we keep doing what UNIX has always done, UNIX will never grow. Today's computing needs require ingenuity and thought. I don't have the resources or the skills to take this idea much further, and I know there's problems with security, accessability, implementation, and compatibility. Even taking this into consideration, I think it could be done. Perhaps something to work towards in FreeBSD 4.0? Maybe even set a new industry standard? -----Original Message----- From: Jordan K. Hubbard To: Peter Korsten Cc: chat@FreeBSD.ORG Date: Wednesday, October 01, 1997 5:56 PM Subject: Re: Browser interface (I changed the subject) >> OK, what did I forget in this magnificent plan? :) > >Your sense of reality. I think none of this stands a chance of >happening unless you truncate your goalset accordingly. ;-) > > Jordan > >