From owner-freebsd-current@FreeBSD.ORG  Thu Jan 12 07:54:37 2012
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id AA7461065672
	for <current@freebsd.org>; Thu, 12 Jan 2012 07:54:37 +0000 (UTC)
	(envelope-from luigi@onelab2.iet.unipi.it)
Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238])
	by mx1.freebsd.org (Postfix) with ESMTP id 6DC758FC17
	for <current@freebsd.org>; Thu, 12 Jan 2012 07:54:37 +0000 (UTC)
Received: by onelab2.iet.unipi.it (Postfix, from userid 275)
	id 15C677300A; Thu, 12 Jan 2012 09:11:39 +0100 (CET)
Date: Thu, 12 Jan 2012 09:11:39 +0100
From: Luigi Rizzo <rizzo@iet.unipi.it>
To: current@freebsd.org
Message-ID: <20120112081139.GA9921@onelab2.iet.unipi.it>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.3i
Cc: 
Subject: kernel config files outside of sys/${ARCH}/conf ?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
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, 12 Jan 2012 07:54:37 -0000

usr/sbin/config assumes that the kernel config file
lives in ${src_base}/sys/${arch}/conf , which means that
if you need to build a custom kernel one needs RW
access to that directory.

Any idea on how we can enable config to work in a
generic directory ?

I scanned the source code usr.sbin/config and found that
it uses hardwired paths -- specifically, it looks for
the kernel source tree in "../.." and has multiple
hardwired paths such as "../../conf/".
There is also a somewhat undocumented access to a
file called DEFAULTS that extends the configuration you pass.

Any objections to the addition of a "-s" option to config(8)
to specify the location of the source tree ?

cheers
luigi