[e666df1] | 1 | <?xml version="1.0" encoding="ISO-8859-1"?>
|
---|
| 2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
|
---|
| 3 | "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
|
---|
| 4 | <!ENTITY % general-entities SYSTEM "../../general.ent">
|
---|
| 5 | %general-entities;
|
---|
| 6 | ]>
|
---|
| 7 |
|
---|
| 8 | <sect1 id="ch-system-busybox" role="wrap">
|
---|
| 9 | <?dbhtml filename="busybox.html"?>
|
---|
| 10 |
|
---|
| 11 | <title>Busybox-&busybox-version;</title>
|
---|
| 12 |
|
---|
| 13 | <indexterm zone="ch-system-busybox">
|
---|
| 14 | <primary sortas="a-Busybox">Busybox</primary>
|
---|
| 15 | </indexterm>
|
---|
| 16 |
|
---|
| 17 | <sect2 role="package">
|
---|
| 18 | <title/>
|
---|
| 19 |
|
---|
| 20 | <para>BusyBox combines tiny versions of many common UNIX utilities into a single small
|
---|
| 21 | executable. It provides replacements for most of the utilities you usually find in GNU
|
---|
| 22 | fileutils, shellutils, etc. The utilities in BusyBox generally have fewer options than
|
---|
| 23 | their full-featured GNU cousins; however, the options that are included provide the
|
---|
| 24 | expected functionality and behave very much like their GNU counterparts. BusyBox provides
|
---|
| 25 | a fairly complete environment for any small or embedded system.</para>
|
---|
| 26 |
|
---|
| 27 | </sect2>
|
---|
| 28 |
|
---|
| 29 | <sect2 role="installation">
|
---|
| 30 | <title>Installation of Busybox</title>
|
---|
| 31 |
|
---|
| 32 | <para os="p1">The follow patches fixes some issues that are related to the
|
---|
| 33 | headers we are using. To correct this issues apply the following patch:</para>
|
---|
| 34 |
|
---|
| 35 | <screen os="p2"><userinput>patch -Np1 -i ../&busybox-fixes-patch;</userinput></screen>
|
---|
| 36 |
|
---|
| 37 | <para os="a">Create default configuration:</para>
|
---|
| 38 |
|
---|
| 39 | <screen os="b"><userinput>make defconfig</userinput></screen>
|
---|
| 40 |
|
---|
[3800899] | 41 | <note os="c">
|
---|
| 42 | <para>Below we are just telling Busybox to use the default configuration of
|
---|
| 43 | uClibc. For those for more adventureous, you can use make menuconfig, and
|
---|
| 44 | do a more custom build of your Busybox.</para>
|
---|
| 45 | </note>
|
---|
| 46 |
|
---|
| 47 | <para os="d">We will need to edit the configuration file, to make sure everything gets
|
---|
[e666df1] | 48 | compiled and put into it's proper locations:</para>
|
---|
| 49 |
|
---|
[3800899] | 50 | <screen os="e"><userinput>cp .config .config.orig
|
---|
[e666df1] | 51 | sed -e "s:# USING_CROSS_COMPILER.*:USING_CROSS_COMPILER=y:" \
|
---|
| 52 | -e "/^CROSS_COMPILER_PREFIX/s:=.*:=\"${CLFS_TARGET}-\":" \
|
---|
| 53 | .config.orig > .config</userinput></screen>
|
---|
| 54 |
|
---|
[3800899] | 55 | <para os="f">Compile the package:</para>
|
---|
[e666df1] | 56 |
|
---|
[3800899] | 57 | <screen os="g"><userinput>make CROSS="${CLFS_TARGET}-" PREFIX="${CLFS}" busybox</userinput></screen>
|
---|
[e666df1] | 58 |
|
---|
[3800899] | 59 | <para os="h">Install the package:</para>
|
---|
[e666df1] | 60 |
|
---|
[3800899] | 61 | <screen os="i"><userinput>make PREFIX="${CLFS}" install</userinput></screen>
|
---|
[e666df1] | 62 |
|
---|
| 63 | </sect2>
|
---|
| 64 |
|
---|
| 65 | <sect2 id="contents-busybox" role="content">
|
---|
| 66 | <title>Contents of Busybox</title>
|
---|
| 67 |
|
---|
| 68 | <segmentedlist>
|
---|
| 69 | <segtitle>Installed programs</segtitle>
|
---|
| 70 |
|
---|
| 71 | <seglistitem>
|
---|
| 72 | <seg>To be Written</seg>
|
---|
| 73 | </seglistitem>
|
---|
| 74 | </segmentedlist>
|
---|
| 75 |
|
---|
| 76 | <!--
|
---|
| 77 | <variablelist>
|
---|
| 78 | <bridgehead renderas="sect3">Short Descriptions</bridgehead>
|
---|
| 79 | <?dbfo list-presentation="list"?>
|
---|
| 80 | <?dbhtml list-presentation="table"?>
|
---|
| 81 |
|
---|
| 82 | <varlistentry id="bash">
|
---|
| 83 | <term><command>bash</command></term>
|
---|
| 84 | <listitem>
|
---|
| 85 | <para>A widely-used command interpreter; it performs many types of
|
---|
| 86 | expansions and substitutions on a given command line before executing
|
---|
| 87 | it, thus making this interpreter a powerful tool</para>
|
---|
| 88 | <indexterm zone="ch-system-bash bash">
|
---|
| 89 | <primary sortas="b-bash">bash</primary>
|
---|
| 90 | </indexterm>
|
---|
| 91 | </listitem>
|
---|
| 92 | </varlistentry>
|
---|
| 93 |
|
---|
| 94 | <varlistentry id="bashbug">
|
---|
| 95 | <term><command>bashbug</command></term>
|
---|
| 96 | <listitem>
|
---|
| 97 | <para>A shell script to help the user compose and mail standard
|
---|
| 98 | formatted bug reports concerning <command>bash</command></para>
|
---|
| 99 | <indexterm zone="ch-system-bash bashbug">
|
---|
| 100 | <primary sortas="b-bashbug">bashbug</primary>
|
---|
| 101 | </indexterm>
|
---|
| 102 | </listitem>
|
---|
| 103 | </varlistentry>
|
---|
| 104 |
|
---|
| 105 | <varlistentry id="sh">
|
---|
| 106 | <term><command>sh</command></term>
|
---|
| 107 | <listitem>
|
---|
| 108 | <para>A symlink to the <command>bash</command> program; when invoked
|
---|
| 109 | as <command>sh</command>, <command>bash</command> tries to mimic the
|
---|
| 110 | startup behavior of historical versions of <command>sh</command> as
|
---|
| 111 | closely as possible, while conforming to the POSIX standard as
|
---|
| 112 | well</para>
|
---|
| 113 | <indexterm zone="ch-system-bash sh">
|
---|
| 114 | <primary sortas="b-sh">sh</primary>
|
---|
| 115 | </indexterm>
|
---|
| 116 | </listitem>
|
---|
| 117 | </varlistentry>
|
---|
| 118 |
|
---|
| 119 | </variablelist>
|
---|
| 120 | -->
|
---|
| 121 | </sect2>
|
---|
| 122 |
|
---|
| 123 | </sect1>
|
---|