From owner-freebsd-hackers  Wed Feb 28 07:53:13 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id HAA17086
          for hackers-outgoing; Wed, 28 Feb 1996 07:53:13 -0800 (PST)
Received: from koala.scott.net (root@koala.scott.net [204.181.147.2])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id HAA17079
          for <hackers@FreeBSD.ORG>; Wed, 28 Feb 1996 07:53:07 -0800 (PST)
Received: from jason.scott.net (dialup84.scott.net [205.241.3.84]) by koala.scott.net (8.7.3/8.7.3) with SMTP id JAA19147 for <hackers@FreeBSD.ORG>; Wed, 28 Feb 1996 09:52:56 -0600
Message-ID: <31347A5A.41C67EA6@scott.net>
Date: Wed, 28 Feb 1996 09:52:58 -0600
From: Jason Gilbert <jason@scott.net>
X-Mailer: Mozilla 2.0 (X11; I; FreeBSD 2.1-STABLE i386)
MIME-Version: 1.0
To: hackers@FreeBSD.ORG
Subject: Re: xforms maintenance tools (was Re: Tcl/Tk sysinstall)
References: <9602281427.AA18009@sys8.wfc.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
Precedence: bulk

Mike Eggleston wrote:

> >> Why not have a html/cgi based manager.  That would run under lynx,
> >> chimera, mosaic, etc., for local and remote administration.
> >>
> >> Mike
> >>
> 
> > How about security? I don't feel I would like that kind of
> > management tool...
> 
> >       Sander
> 
> Security can be handled by the server's internal authentication
> protocols.  For httpd just set up authentication on the single
> person(s) that is allowed to modify the security configurations.
> 
> To me, for a company (an ISP maybe?) that had a central mis group, but
> all their computers/servers were distributed around the country/world,
> a distributed configuration/management system would be ideal.
> 
> I wouldn't want to run X through a 14.4 remote dialup from around the
> world (I have little enough hair as it is (8)
> 
> Mike

Isn's this how Netscape does management for there servers??

Jason