From owner-freebsd-current Wed Oct 1 15:14:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA12643 for current-outgoing; Wed, 1 Oct 1997 15:14:51 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA12633 for ; Wed, 1 Oct 1997 15:14:46 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id PAA04452; Wed, 1 Oct 1997 15:14:44 -0700 (PDT) To: Brandon Gillespie cc: freebsd-current@FreeBSD.ORG Subject: Re: new command: doconfig In-reply-to: Your message of "Wed, 01 Oct 1997 15:39:36 MDT." Date: Wed, 01 Oct 1997 15:14:44 -0700 Message-ID: <4448.875744084@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I would like to add this as a new command to FreeBSD. I mentioned it a > few months back when I originally wrote it, and received positive > responses about it. This command derives from a similar command in > Digital Unix. 'doconfig' is basically a simplifier for kernel compiling, > by wrapping 'vi /sys/i386/conf/MINE; config; cd ../../compile/MINE; make > depend; make; make install; reboot' or whatnot into a simpler, nicer > interface.. For instance, I just recompiled my kernel with (the GLACIER > config file already existed): My only problem with this is that it didn't go far enough. Yes, it front-ends a few steps, but only a few of the ones you'd expect in a configuration front-end tool. It should also build the configuration file through a complete interactive Q&A process if you don't have one. Jordan