Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 31 Jan 2012 06:32:29 -0500
From:      Rick Miller <vmiller@hostileadmin.com>
To:        Rob Farmer <rfarmer@predatorlabs.net>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: make release custom kernel conf not found
Message-ID:  <CAHzLAVGtQ3%2BKrXU3aGXYWVBd7SuRwdwowCpSmn7hzb1G%2B3zvQA@mail.gmail.com>
In-Reply-To: <CANT_Jfw=B7QaKfk1Xzv0SRuDe6n=udMR64Y0N_qPFTYx3QAVbg@mail.gmail.com>
References:  <CAHzLAVG1%2Bx%2BA7%2Bzo1%2B80kKBvrQgKFxzo9RbCXBRQWfQ2tDZCTA@mail.gmail.com> <CANT_JfwMj60vndg=cvNjOBUOLg5rxX16X0gHP3iV91Wahi_7cQ@mail.gmail.com> <CAHzLAVFc4U4QjXw0pk10XUg4jZt6WrSExg7ANu_CjgA_tW-_kA@mail.gmail.com> <CANT_Jfw=B7QaKfk1Xzv0SRuDe6n=udMR64Y0N_qPFTYx3QAVbg@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Thanks Rob and Lowell,

I will keep this information handy.  It was helpful.

On Tue, Jan 31, 2012 at 4:22 AM, Rob Farmer <rfarmer@predatorlabs.net> wrot=
e:
> On Mon, Jan 30, 2012 at 10:39 AM, Rick Miller <vmiller@hostileadmin.com> =
wrote:
>> 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.
>
> --
> Rob Farmer



--=20
Take care
Rick Miller



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHzLAVGtQ3%2BKrXU3aGXYWVBd7SuRwdwowCpSmn7hzb1G%2B3zvQA>