%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 updates to the &busybox-version; branch by the Busybox developers: patch -Np1 -i ../&busybox-branch_update-patch; Copy the Busybox config file from where you downloaded it:: cp ${CLFS}/sources/busybox-&busybox-version;.config .config Below we are just telling Busybox to use the default configuration of Busybox. For those for more adventureous, you can use make menuconfig, and do a more custom build of your Busybox. Now we will take our configuration we just created, and make Busybox use it: make oldconfig Compile the package: make ARCH=${CLFS_ARCH} CC="${CC} ${BUILD}" CROSS_COMPILE="${CLFS_TARGET}-" Install the package: make make ARCH=${CLFS_ARCH} CC="${CC} ${BUILD}" CROSS_COMPILE="${CLFS_TARGET}-" \ CONFIG_PREFIX=${IMAGE_DIR} 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