On 9/12/06, Ken Moffat <[EMAIL PROTECTED]> wrote:
Agreed. The temp system should be adequate for finishing the build, for most people that doesn't mean nfs or ssh. The temp system needs to be "(only) just good enough" ;) Ken
Well, I tend to disagree with this a little :) For my purposes, I think the env the book leaves you with in /tools is not sufficient - especially when you use the boot method. We really do need some form of editor built there, both to be able to read the book and follow it while you build, as well as for modifying config files as the final builds progress. Plus, building over a serial console is painful, so for headless machines, a method of SSH'ing in is useful as well - hence why I wrote my SSH Hint to put dropbear into /tools. However, I myself cross-compile iproute2, inetutils, dhcpcd, and dropbear - iproute2 and inetutils come with their own little quirks when cross-built as an un-priviledged user (some of their binaries end up without execute permissions). I've been meaning to Wiki-fy my ssh hint - and I think making the "/tools Add-Ons" part of the wiki is a great idea. Jeremy _______________________________________________ Clfs-dev mailing list [email protected] http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-dev
