source: clfs-embedded/BOOK/final-system/x86/busybox.xml@ 9642843

<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
  "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
  <!ENTITY % general-entities SYSTEM "../../general.ent">
  %general-entities;
]>

<sect1 id="ch-system-busybox" role="wrap">
  <?dbhtml filename="busybox.html"?>

  <title>Busybox-&busybox-version;</title>

  <indexterm zone="ch-system-busybox">
    <primary sortas="a-Busybox">Busybox</primary>
  </indexterm>

  <sect2 role="package">
    <title/>

    <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</title>

    <para os="p1">Before you build BusyBox, you may want to check the following URL for
    patches that the upstream maintainer of BusyBox has released to fix issues.
    <ulink url="http://busybox.net/downloads/fixes-&busybox-version;"/></para>

    <para os="p2">Here's an example of how to apply the patches from Busybox's website
    replace {patch_name} with the name of the patch:</para>

<screen os="p3" role="nodump"><userinput>patch -Np1 -i ../busybox-&busybox-version;{patch_name}</userinput></screen>

    <para os="p4">The following patch fixes some issues that are related to the
    headers we are using:</para>

<screen os="p5"><userinput>patch -Np1 -i ../&busybox-fixes-patch;</userinput></screen>

    <para os="a">Create the default configuration:</para>

<screen os="b"><userinput>make defconfig</userinput></screen>

    <note os="c">
      <para>Below we are just telling Busybox to use the default configuration of
      uClibc. For those for more adventureous, you can use make menuconfig, and
      do a more custom build of your Busybox.</para>
    </note>

   <para os="d">We will need to edit the configuration file, to make sure everything gets
   compiled:</para>

<screen os="e"><userinput>BUSYBOX_OPTIONS="CONFIG_DMALLOC CONFIG_BUILD_AT_ONCE CONFIG_BUILD_LIBBUSYBOX
    CONFIG_FEATURE_SH_IS_NONE CONFIG_LOCALE_SUPPORT CONFIG_TFTP CONFIG_FTPGET
    CONFIG_FTPPUT CONFIG_IPCALC CONFIG_TFTP CONFIG_HUSH CONFIG_LASH
    CONFIG_MSH CONFIG_INETD CONFIG_DPKG CONFIG_RPM2CPIO CONFIG_RPM
    CONFIG_FOLD CONFIG_LOGNAME CONFIG_OD CONFIG_CRONTAB CONFIG_UUDECODE
    CONFIG_UUENCODE CONFIG_SULOGIN CONFIG_DC CONFIG_DEBUG_YANK_SUSv2
    CONFIG_DEBUG_INIT CONFIG_DEBUG_CROND_OPTION CONFIG_FEATURE_UDHCP_DEBUG
    CONFIG_TASKSET CONFIG_CHATTR CONFIG_FSCK CONFIG_LSATTR CONFIG_CHPST
    CONFIG_SETUIDGID CONFIG_ENVUIDGID CONFIG_ENVDIR CONFIG_SOFTLIMIT
    CONFIG_FEATURE_2_4_MODULES"
for config in $BUSYBOX_OPTIONS; do
    cp .config{,.orig}
    sed -e "s:${config}=y:${config}=n:" .config.orig &gt; .config
done
BUSYBOX_OPTIONS="CONFIG_FEATURE_SH_IS_ASH CONFIG_FEATURE_TRACEROUTE_VERBOSE
    CONFIG_FEATURE_TRACEROUTE_SOURCE_ROUTE"
for config in $BUSYBOX_OPTIONS; do
    cp .config{,.orig}
    sed -e "s:# ${config} is not set:${config}=y:" .config.orig &gt; .config
done</userinput></screen>

    <para os="f">Compile the package:</para>

<screen os="g"><userinput>make ARCH=i386 CROSS_COMPILE="${CLFS_TARGET}-" CFLAGS="${BUILD}"</userinput></screen>

    <para os="h">Install the package:</para>

<screen os="i"><userinput>make ARCH=i386 CROSS_COMPILE="${CLFS_TARGET}-" CFLAGS="${BUILD}" \
    CONFIG_PREFIX="${CLFS}" install</userinput></screen>

    <para os="j">If your going to build your kernel with modules, you will need to make
    sure <command>depmod.pl</command> is available:</para>

<screen os="k"><userinput>cp examples/depmod.pl ${CLFS}/cross-tools/bin
chmod 755 ${CLFS}/cross-tools/bin/depmod.pl</userinput></screen>

  </sect2>

  <sect2 id="contents-busybox" role="content">
    <title>Contents of Busybox</title>

    <segmentedlist>
      <segtitle>Installed programs</segtitle>

      <seglistitem>
        <seg>To be Written</seg>
      </seglistitem>
    </segmentedlist>

<!--
    <variablelist>
      <bridgehead renderas="sect3">Short Descriptions</bridgehead>
      <?dbfo list-presentation="list"?>
      <?dbhtml list-presentation="table"?>

      <varlistentry id="bash">
        <term><command>bash</command></term>
        <listitem>
          <para>A widely-used command interpreter; it performs many types of
          expansions and substitutions on a given command line before executing
          it, thus making this interpreter a powerful tool</para>
          <indexterm zone="ch-system-bash bash">
            <primary sortas="b-bash">bash</primary>
          </indexterm>
        </listitem>
      </varlistentry>

      <varlistentry id="bashbug">
        <term><command>bashbug</command></term>
        <listitem>
          <para>A shell script to help the user compose and mail standard
          formatted bug reports concerning <command>bash</command></para>
          <indexterm zone="ch-system-bash bashbug">
            <primary sortas="b-bashbug">bashbug</primary>
          </indexterm>
        </listitem>
      </varlistentry>

      <varlistentry id="sh">
        <term><command>sh</command></term>
        <listitem>
          <para>A symlink to the <command>bash</command> program; when invoked
          as <command>sh</command>, <command>bash</command> tries to mimic the
          startup behavior of historical versions of <command>sh</command> as
          closely as possible, while conforming to the POSIX standard as
          well</para>
          <indexterm zone="ch-system-bash sh">
            <primary sortas="b-sh">sh</primary>
          </indexterm>
        </listitem>
      </varlistentry>

    </variablelist>
-->
  </sect2>

</sect1>