Date: Mon, 30 Jan 2012 13:56:46 -0500 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: Rick Miller <vmiller@hostileadmin.com> Cc: Rob Farmer <rfarmer@predatorlabs.net>, freebsd-questions@freebsd.org Subject: Re: make release custom kernel conf not found Message-ID: <44liopqas1.fsf@be-well.ilk.org> In-Reply-To: <CAHzLAVFc4U4QjXw0pk10XUg4jZt6WrSExg7ANu_CjgA_tW-_kA@mail.gmail.com> (Rick Miller's message of "Mon, 30 Jan 2012 13:39:11 -0500") References: <CAHzLAVG1%2Bx%2BA7%2Bzo1%2B80kKBvrQgKFxzo9RbCXBRQWfQ2tDZCTA@mail.gmail.com> <CANT_JfwMj60vndg=cvNjOBUOLg5rxX16X0gHP3iV91Wahi_7cQ@mail.gmail.com> <CAHzLAVFc4U4QjXw0pk10XUg4jZt6WrSExg7ANu_CjgA_tW-_kA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44liopqas1.fsf>