<br><br><div class="gmail_quote">On Wed, Dec 9, 2009 at 5:10 PM, Phill Wiggin <span dir="ltr"><<a href="mailto:alamar@gmail.com">alamar@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im"><br><br><div class="gmail_quote">On Wed, Dec 9, 2009 at 4:26 PM, Phil Bridges <span dir="ltr"><<a href="mailto:gravityhammer@gmail.com" target="_blank">gravityhammer@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
When setting up a netbooting directory, is it common to go ahead and<br>
CHROOT and totally build a new kernel and new bin files for all of<br>
your software? I'm using Gentoo, if that matters.<br></blockquote></div><br></div>That's just what I do. Works like a charm. Let the hosting machine do all the heavy lifting, then the netbooting frontend doesn't have to.<br>
</blockquote></div><br>Forgot to mention, I'm using Gentoo too.<br><br>Also, I'm using the same architecture to do the compiles (no cross-compiling and what-not). I just<br><br>* Shut down the frontend (Zotac ION .. amd64)<br>
* Log in to the hosting machine (amd64)<br>* chroot<br>* emerge updates<br>* Exit chroot environment<br>* Net-Boot frontend.<br>