From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 14 17:56:23 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 125EB1065695; Sun, 14 Nov 2010 17:56:23 +0000 (UTC) (envelope-from jhein@gossamer.timing.com) Received: from mout.perfora.net (mout.perfora.net [74.208.4.195]) by mx1.freebsd.org (Postfix) with ESMTP id CF0B58FC08; Sun, 14 Nov 2010 17:56:22 +0000 (UTC) Received: from gossamer.timing.com ([206.168.13.144]) by mrelay.perfora.net (node=mrus1) with ESMTP (Nemesis) id 0MSciy-1OsUEZ1nm8-00RrxR; Sun, 14 Nov 2010 12:43:45 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <19680.8138.582316.245120@gossamer.timing.com> Date: Sun, 14 Nov 2010 10:43:38 -0700 From: John Hein To: Adrian Chadd In-Reply-To: References: X-Mailer: VM 8.0.12 under 22.3.1 (i386-redhat-linux-gnu) X-Provags-ID: V02:K0:KWdt4qXSYYaHeYMvN0pjr3m7dKXDF7vueTe2JPHG6W3 EJnY+InP3N0smu+BSQodDMYgY1QqwdgWUzAkjwaMfe6d8WFtEA //IOig+XQfK3T81SOP990JDOZkDBEmT2vmJcJbD9BH8u6ImeQC 0G1ZVTgwyNvDLcnQrk3F2JrDShnMFMTGwFabHW0v0RIV5tG/yq lr+Bj4IC5yX0SWrlPNf4g== Cc: freebsd-hackers@freebsd.org, freebsd-current , freebsd-embedded@freebsd.org Subject: Re: The path is now set for "busybox", FreeBSD style X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Nov 2010 17:56:23 -0000 Adrian Chadd wrote at 11:40 +0800 on Nov 14, 2010: > I've committed the below changes to -HEAD. You can now create and build your > own busybox style binary system, completely cross-compiled within the > existing Make framework. It isn't as impressive as it sounds though - a lot > of the framework is already there from just building crunchgen'ed > rescue/sysinstall binaries. > > There's a few things which should be done. Specifically, being able to build > an alternative set of libraries before building the crunchgen target. The > base crosscompile system may include support for PAM, Kerberos, ATM/IPX, etc > but you may not want your crunch'ed image to have them. To do this right > now, you have to disable these features in the main build. That may be OK > for some. > > But just to stress it - I've got a couple of access point images at home > running a crunchgen'ed environment under MIPS and besides the obvious binary > bloat, it works perfectly well. Besides a cut-down startup framework, the > image cross-builds entirely from the base FreeBSD source tree. > > Let me know if you'd like to give it a shot and I'll put my "bsdbox" > Makefile scripts online to try. That's great. I assume it be not be hard for someone to take your scripts as a starting point and create a sysutils/bsdbox akin to sysutils/busybox?