From owner-freebsd-current  Wed Oct  1 15:19:42 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id PAA12877
          for current-outgoing; Wed, 1 Oct 1997 15:19:42 -0700 (PDT)
Received: from roguetrader.com (brandon@cold.org [206.81.134.103])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA12866
          for <freebsd-current@FreeBSD.ORG>; Wed, 1 Oct 1997 15:19:37 -0700 (PDT)
Received: from localhost (brandon@localhost)
	by roguetrader.com (8.8.5/8.8.5) with SMTP id QAA28670;
	Wed, 1 Oct 1997 16:21:46 -0600 (MDT)
Date: Wed, 1 Oct 1997 16:21:45 -0600 (MDT)
From: Brandon Gillespie <brandon@roguetrader.com>
To: "Jordan K. Hubbard" <jkh@time.cdrom.com>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: new command: doconfig 
In-Reply-To: <4448.875744084@time.cdrom.com>
Message-ID: <Pine.BSF.3.96.971001161834.28587B-100000@roguetrader.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Wed, 1 Oct 1997, Jordan K. Hubbard wrote:
> > 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.

I agree :)

The only reason I didn't do it, was because I've never been able to find
out if anybody is working on this already...  If not, then perhaps we can
make one.  I have a few ideas on various modular ways this could be
implemented.

As it is right now, 'doconfig' actually runs an external program to
'auto-generate' the initial file.  The external program does nothing other
than sed the GENERIC kernel, but only because of the above reasons.

So I guess the question is, what is there right now for auto generating a
kernel config file?
 
-Brandon