From owner-freebsd-current@FreeBSD.ORG  Wed Sep  3 21:14:53 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 1DFD216A4BF
	for <current@freebsd.org>; Wed,  3 Sep 2003 21:14:53 -0700 (PDT)
Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3B83443FF5
	for <current@freebsd.org>; Wed,  3 Sep 2003 21:14:50 -0700 (PDT)
	(envelope-from jb@cimlogic.com.au)
Received: from freebsd1.cimlogic.com.au (localhost [127.0.0.1])
	by cimlogic.com.au (8.12.9/8.12.9) with ESMTP id h844GWbZ014941
	for <current@freebsd.org>; Thu, 4 Sep 2003 14:16:33 +1000 (EST)
	(envelope-from jb@cimlogic.com.au)
Received: (from jb@localhost)
	by freebsd1.cimlogic.com.au (8.12.9/8.12.9/Submit) id h844GWtd014940
	for current@freebsd.org; Thu, 4 Sep 2003 14:16:32 +1000 (EST)
Date: Thu, 4 Sep 2003 14:16:32 +1000
From: John Birrell <jb@cimlogic.com.au>
To: current@freebsd.org
Message-ID: <20030904041632.GA14639@freebsd1.cimlogic.com.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.1i
Subject: config(8) KERNEL setting
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Sep 2003 04:14:53 -0000

In a RELENG_4 kernel build, I'm accustomed to setting 'config foo' in
a kernel configuration file and ending up with a kernel called 'foo'.

In current, kern.pre.mk contains:

KERNEL_KO?=	kernel
KERNEL?=	kernel
KODIR?=		/boot/${KERNEL}

however kern.post.mk only uses KERNEL_KO, so even though config(8) has
set KERNEL for me, that name only gets used for the boot directory.
There doesn't seem to be any way of getting KERNEL_KO set from the
kernel config file.

It would make more sense to me if kern.pre.mk contained this:

KERNEL?=	kernel
KERNEL_KO?=	${KERNEL}
KODIR?=		/boot/${KERNEL}

Comments?

-- 
John Birrell