From owner-freebsd-questions@FreeBSD.ORG  Mon Jan 30 18:56:50 2012
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 5A3931065673
	for <freebsd-questions@freebsd.org>;
	Mon, 30 Jan 2012 18:56:50 +0000 (UTC)
	(envelope-from freebsd-questions-local@be-well.ilk.org)
Received: from asbnvacz-mailrelay01.megapath.net
	(asbnvacz-mailrelay01.megapath.net [207.145.128.243])
	by mx1.freebsd.org (Postfix) with ESMTP id 26A748FC18
	for <freebsd-questions@freebsd.org>;
	Mon, 30 Jan 2012 18:56:49 +0000 (UTC)
Received: from mail6.sea5.speakeasy.net (mail6.sea5.speakeasy.net
	[69.17.117.50])
	by asbnvacz-mailrelay01.megapath.net (Postfix) with ESMTP id
	3E3B4A707DE for <freebsd-questions@freebsd.org>;
	Mon, 30 Jan 2012 13:56:48 -0500 (EST)
Received: (qmail 11032 invoked from network); 30 Jan 2012 18:56:48 -0000
Received: by simscan 1.4.0 ppid: 11434, pid: 29821, t: 0.1600s
	scanners: clamav: 0.88.2/m:52/d:10739
Received: from unknown (HELO be-well.ilk.org) ([66.92.78.145])
	(envelope-sender <freebsd-questions-local@be-well.ilk.org>)
	by mail6.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP
	for <freebsd-questions@freebsd.org>; 30 Jan 2012 18:56:48 -0000
Received: by be-well.ilk.org (Postfix, from userid 1147)
	id 28BAD56460; Mon, 30 Jan 2012 13:56:46 -0500 (EST)
From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org>
To: Rick Miller <vmiller@hostileadmin.com>
References: <CAHzLAVG1+x+A7+zo1+80kKBvrQgKFxzo9RbCXBRQWfQ2tDZCTA@mail.gmail.com>
	<CANT_JfwMj60vndg=cvNjOBUOLg5rxX16X0gHP3iV91Wahi_7cQ@mail.gmail.com>
	<CAHzLAVFc4U4QjXw0pk10XUg4jZt6WrSExg7ANu_CjgA_tW-_kA@mail.gmail.com>
Date: Mon, 30 Jan 2012 13:56:46 -0500
In-Reply-To: <CAHzLAVFc4U4QjXw0pk10XUg4jZt6WrSExg7ANu_CjgA_tW-_kA@mail.gmail.com>
	(Rick Miller's message of "Mon, 30 Jan 2012 13:39:11 -0500")
Message-ID: <44liopqas1.fsf@be-well.ilk.org>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (berkeley-unix)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Rob Farmer <rfarmer@predatorlabs.net>, freebsd-questions@freebsd.org
Subject: Re: make release custom kernel conf not found
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, 
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Jan 2012 18:56:50 -0000

Rick Miller <vmiller@hostileadmin.com> writes:

> Thanks Rob...
>
> I put the kernel conf file in the source tree as opposed to linking to
> it and it certainly did compile the custom kernel.
>
> What confuses me (not that I expect you to have the answer) is that
> Chapter 9 of the handbook has a tip that recommends keeping the kernel
> config in /root/kernels and symlinking to it from the source tree.  If
> it doesn't work, why is there a tip recommending this practice?

It works fine; sounds like you just don't understand what a chroot is. 

Once a process is chroot'd to /app/release/, its idea of /root/kernels
is what non-chroot'd processes see as /app/release/kernels. It can't see
*any* files that aren't under /app/release. I would tend to recommend
adding to your build script a command that copies the kernel file into
the chroot before starting the chroot, but I'm sure others have other
preferred approaches.

 - Lowell