From owner-freebsd-advocacy Sat May 2 07:58:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA04490 for freebsd-advocacy-outgoing; Sat, 2 May 1998 07:58:07 -0700 (PDT) (envelope-from owner-freebsd-advocacy@FreeBSD.ORG) Received: from violet.csi.cam.ac.uk (exim@violet.csi.cam.ac.uk [131.111.8.58]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA04482 for ; Sat, 2 May 1998 07:58:01 -0700 (PDT) (envelope-from bjc23@hermes.cam.ac.uk) Received: from bjc23.trin.cam.ac.uk ([131.111.212.250]) by violet.csi.cam.ac.uk with smtp (Exim 1.92 #1) id 0yVdjf-0001VV-00; Sat, 2 May 1998 15:57:55 +0100 Date: Sat, 2 May 1998 15:57:56 +0100 (BST) From: Ben Cohen X-Sender: bjc23@bjc23.trin.cam.ac.uk Reply-To: bjc23@hermes.cam.ac.uk To: Don Wilde cc: advocacy@FreeBSD.ORG Subject: Re: A GUI greyscale interface by default In-Reply-To: <354B2984.CC161BAB@ibm.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-advocacy@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! > I just want to keep > the GUI-to-script separation absolute, because I don't want to lose any > of the command-line text-file configuration interface. I'm afraid that > GUI will eventually lead to binary config files, and then we've lost the > access to mass config changes. I'm speaking specifically of user changes > in passwd, but there are other places where I want to use scripts to > make config changes. Before I get flamed, I realize that GUI doesn't > imply lack of access, I just want to keep it on the sane path from the > start. I agree---I'm sure there are plenty of places where things are bound to be easier editing a config file rather than using a config program (both in terms of writing a the program and using it). And it would be simpler having text config files because then they can be inspected by hand easily (e.g. if the GUI fails or is suspected broken) and the sources for programs which use the configs wouldn't have to be re-written. > I'm starting to dig through the ports install scripts and such with some > tips from Jordan. I think our problem needs to be addressed at a deeper > level first, before we even begin to talk GUI. Yes. The config program could be split up into several different programs each of which could be worked on separately. e.g. Ports manager, X config manager, system admin, ... > I will say right up front that I am still a UN*X newbie, but I've bought > _lots_ of O'Reilly books and I'm slowly working my way through them. The > more I read, the more I see that FreeBSD is a rough-cut gem that just > needs a little TLC because it's really a perfect blue-white. It just > takes a few judicious taps and we'll have a brilliant-cut diamond > flashing in the Sun! I'm a newbie too. I first used SCO UNIX V a year or so ago, which I prefer in a few ways, partly because I used SCO first. (e.g. sysadmsh) Ben. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message