From owner-freebsd-questions@FreeBSD.ORG Tue Jan 31 09:22:55 2012 Return-Path: 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 A2E50106564A for ; Tue, 31 Jan 2012 09:22:55 +0000 (UTC) (envelope-from rfarmer@predatorlabs.net) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 532038FC14 for ; Tue, 31 Jan 2012 09:22:55 +0000 (UTC) Received: by vcmm1 with SMTP id m1so312025vcm.13 for ; Tue, 31 Jan 2012 01:22:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=predatorlabs.net; s=google; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=irAuWE0Itd1jXRYHug1gpxIYQ8fG2VaRXDg1pN8dvUE=; b=jwPgsnAxmKTjFFlLIIh0DuXaLxZONTR5tLNIpbdmZPWkl/KFG50dpuFLyAln9TqxJd s7ItNyruaDOqBsaBHBXUSPBvdLKvBoLJ2+Wf62aK9Iib1VwUsCBozObJx9sXHUEu9rxt U42+j90YT/lABl6ph5Evys1tO8awQJsQOoxxQ= MIME-Version: 1.0 Received: by 10.220.38.10 with SMTP id z10mr12348677vcd.48.1328001774572; Tue, 31 Jan 2012 01:22:54 -0800 (PST) Received: by 10.220.199.77 with HTTP; Tue, 31 Jan 2012 01:22:54 -0800 (PST) X-Originating-IP: [128.95.134.93] In-Reply-To: References: Date: Tue, 31 Jan 2012 01:22:54 -0800 Message-ID: From: Rob Farmer To: Rick Miller Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jan 2012 09:22:55 -0000 On Mon, Jan 30, 2012 at 10:39 AM, Rick Miller wr= ote: > 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. =A0If > it doesn't work, why is there a tip recommending this practice? > I think the idea is to avoid accidentally deleting it - sometimes people who get weird build errors are told to delete /usr/src and /usr/obj, to make sure everything is in a consistent state. The symlink will work fine for normal builds, which is what the handbook covers, but the release building process installs a new copy of the base system and then runs within it, to try and ensure a completely stock environment. Any changes you made to the main system (make.conf, custom kernels, etc.) are intentionally ignored. As Lowell points out, the "right" way to do this is make either a patch or a script to add your changes and have the release framework apply it. Copying it in is the quick and dirty fix. --=20 Rob Farmer