From owner-freebsd-hackers  Thu Jan 23 17:52:13 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id RAA29118
          for hackers-outgoing; Thu, 23 Jan 1997 17:52:13 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA29110
          for <freebsd-hackers@freefall.freebsd.org>; Thu, 23 Jan 1997 17:52:11 -0800 (PST)
Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id RAA06457; Thu, 23 Jan 1997 17:51:56 -0800 (PST)
To: Don Yuniskis <dgy@rtd.com>
cc: freebsd-hackers@freefall.freebsd.org (FreeBSD hackers)
Subject: Re: suggestion for kernel printk() ? 
In-reply-to: Your message of "Thu, 23 Jan 1997 10:46:39 MST."
             <199701231746.KAA04519@seagull.rtd.com> 
Date: Thu, 23 Jan 1997 17:51:56 -0800
Message-ID: <6454.854070716@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>      But, apparently the kernel image no longer contains the complete
> text of the kernel configuration file!  :-(  This sure had made it easier
> to backtrack in the past.   Presumably, this has been removed to make the
> kernel's footprint smaller?

You need to explicitly select this feature now.  From LINT:

# This allows you to actually store this configuration file into
# the kernel binary itself, where it may be later read by saying:
#    strings /kernel | grep ^___ | sed -e 's/^___//' > MYKERNEL
#
options         INCLUDE_CONFIG_FILE     # Include this file in kernel

					Jordan