From owner-freebsd-config  Wed Apr 30 03:02:49 1997
Return-Path: <owner-freebsd-config>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id DAA19374
          for config-outgoing; Wed, 30 Apr 1997 03:02:49 -0700 (PDT)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA19369
          for <config@freebsd.org>; Wed, 30 Apr 1997 03:02:45 -0700 (PDT)
Received: from time.cdrom.com (localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id DAA26031; Wed, 30 Apr 1997 03:02:36 -0700 (PDT)
To: Bruce Evans <bde@zeta.org.au>
cc: msmith@atrad.adelaide.edu.au, config@freebsd.org
Subject: Re: Startup userconfig parsing 
In-reply-to: Your message of "Wed, 30 Apr 1997 18:37:30 +1000."
             <199704300837.SAA13095@godzilla.zeta.org.au> 
Date: Wed, 30 Apr 1997 03:02:36 -0700
Message-ID: <26029.862394556@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-freebsd-config@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> No, it's desired to have no user-specified configuration data then.
> Userconfig etc. are "temporary" kludges to get around h/w and BIOS
> braindamage.

Feh.  Why don't we just put a TCL interpreter into the kernel and have
done with this?  /boot.tcl.  Problem solved at a stroke.  You're
entirely welcome, thanks.

					Jordan