From owner-freebsd-current  Wed Oct  1 16:52:44 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id QAA17178
          for current-outgoing; Wed, 1 Oct 1997 16:52:44 -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 QAA17170
          for <freebsd-current@FreeBSD.ORG>; Wed, 1 Oct 1997 16:52:41 -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 QAA18525; Wed, 1 Oct 1997 16:52:40 -0700 (PDT)
To: Brandon Gillespie <brandon@roguetrader.com>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: new command: doconfig 
In-reply-to: Your message of "Wed, 01 Oct 1997 16:21:45 MDT."
             <Pine.BSF.3.96.971001161834.28587B-100000@roguetrader.com> 
Date: Wed, 01 Oct 1997 16:52:40 -0700
Message-ID: <18521.875749960@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> 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.

I don't think that anyone is really working on it - they keep
waiting for a miracle to happen and config(1) to simply go away. ;-)

Since that's not likely anytime soon, I say go for it with
doconfig.

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

Nothing. :(

					Jordan