From owner-freebsd-stable@FreeBSD.ORG Mon Mar 13 15:32:35 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AA89516A429 for ; Mon, 13 Mar 2006 15:32:26 +0000 (UTC) (envelope-from amesbury@umn.edu) Received: from mtaout-m.tc.umn.edu (mtaout-m.tc.umn.edu [160.94.23.21]) by mx1.FreeBSD.org (Postfix) with SMTP id 3168543D62 for ; Mon, 13 Mar 2006 15:32:26 +0000 (GMT) (envelope-from amesbury@umn.edu) Received: from [160.94.247.212] (paulaner.oitsec.umn.edu [160.94.247.212]) by mtaout-m.tc.umn.edu with ESMTP; Mon, 13 Mar 2006 09:32:25 -0600 (CST) X-Umn-Remote-Mta: [N] paulaner.oitsec.umn.edu [160.94.247.212] #+LO+TS+AU+HN Message-ID: <44159088.9000505@umn.edu> Date: Mon, 13 Mar 2006 09:32:24 -0600 From: Alan Amesbury User-Agent: Thunderbird 1.5 (X11/20060119) MIME-Version: 1.0 To: Jorge Aldana References: <440DFEC5.3070501@umn.edu> In-Reply-To: X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Kernel INCLUDE_CONFIG_FILE workaround? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Mar 2006 15:32:35 -0000 Jorge Aldana wrote: > I'm on 6.1PreRelease and this works: > > strings -n 3 /boot/kernel/kernel | grep -v ____ | sed -n 's/^___//p' > > There was a minor tweek in this line back in 5.X transition form 4.X but > my script works fine for 6.X since then. Note that the problem isn't in the line you provided above that extracts the built-in configuration file. It's in the build procedure that's supposed to put the config file into the kernel in the first place. In other words, "options INCLUDE_CONFIG_FILE" doesn't include *all* the configuration data, because it doesn't include included configuration files. It's only including the very first level of nested configuration files, which is not an accurate representation of what's in the kernel. In my example, the configuration file for GENERIC should've been in there somewhere, as well as anything included by GENERIC (such as the stuff in DEFAULTS). Again, this used to work great, but appears to have been broken in favor of... usability? -- Alan Amesbury University of Minnesota