%general-entities; ]> Busybox-&busybox-version; Busybox <para>BusyBox combines tiny versions of many common UNIX utilities into a single small executable. It provides replacements for most of the utilities you usually find in GNU fileutils, shellutils, etc. The utilities in BusyBox generally have fewer options than their full-featured GNU cousins; however, the options that are included provide the expected functionality and behave very much like their GNU counterparts. BusyBox provides a fairly complete environment for any small or embedded system.</para> </sect2> <sect2 role="installation"> <title>Installation of Busybox The following patch contains a number of fixes to version &busybox-version; by the Busybox developers: patch -Np1 -i ../&busybox-fixes-patch; The following patch contains a default configuration for busybox: patch -Np1 -i ../&busybox-config-patch; cp -v clfs/config .config Currently we are just telling Busybox to use a generic configuration. For those for more adventureous, you can use make menuconfig, and create a custom or modified configuration for your build. The following tells BusyBox to validate the configuration, and makes sure all required options are defined: make oldconfig Compile the package: make CROSS_COMPILE="${CLFS_TARGET}-" Install the package: make CROSS_COMPILE="${CLFS_TARGET}-" \ CONFIG_PREFIX="${CLFS}" install If your going to build your kernel with modules, you will need to make sure depmod.pl is available: cp examples/depmod.pl /cross-tools/bin chmod 755 /cross-tools/bin/depmod.pl Contents of Busybox Installed programs To be Written