1 | <?xml version="1.0" encoding="ISO-8859-1"?> |
---|
2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" |
---|
3 | "http://www.oasis-open.org/docbook/xml/4.5/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 following patch contains a number of updates to the |
---|
33 | &busybox-version; branch by the Busybox developers:</para> |
---|
34 | |
---|
35 | <screen os="p2"><userinput>patch -Np1 -i ../&busybox-branch_update-patch;</userinput></screen> |
---|
36 | |
---|
37 | <para os="a">Copy the Busybox config file from where you downloaded it::</para> |
---|
38 | |
---|
39 | <screen os="b"><userinput>cp ${CLFS}/sources/busybox-&busybox-version;.config .config</userinput></screen> |
---|
40 | |
---|
41 | <note os="c"> |
---|
42 | <para>Below we are just telling Busybox to use the default configuration of |
---|
43 | Busybox. 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">Now we will take our configuration we just created, and make Busybox use it:</para> |
---|
48 | |
---|
49 | <screen os="e"><userinput>make oldconfig</userinput></screen> |
---|
50 | |
---|
51 | <para os="f">Compile the package:</para> |
---|
52 | |
---|
53 | <screen os="g"><userinput>make ARCH=${CLFS_ARCH} CC="${CC} ${BUILD}" CROSS_COMPILE="${CLFS_TARGET}-"</userinput></screen> |
---|
54 | |
---|
55 | <para os="h">Install the package:</para> |
---|
56 | |
---|
57 | <screen os="i"><userinput>make ARCH=${CLFS_ARCH} CC="${CC} ${BUILD}" CROSS_COMPILE="${CLFS_TARGET}-" \ |
---|
58 | CONFIG_PREFIX=${IMAGE_DIR} install</userinput></screen> |
---|
59 | |
---|
60 | <para os="j">If your going to build your kernel with modules, you will need to make |
---|
61 | sure <command>depmod.pl</command> is available:</para> |
---|
62 | |
---|
63 | <screen os="k"><userinput>cp examples/depmod.pl /cross-tools/bin |
---|
64 | chmod 755 /cross-tools/bin/depmod.pl</userinput></screen> |
---|
65 | |
---|
66 | </sect2> |
---|
67 | |
---|
68 | <sect2 id="contents-busybox" role="content"> |
---|
69 | <title>Contents of Busybox</title> |
---|
70 | |
---|
71 | <segmentedlist> |
---|
72 | <segtitle>Installed programs</segtitle> |
---|
73 | |
---|
74 | <seglistitem> |
---|
75 | <seg>To be Written</seg> |
---|
76 | </seglistitem> |
---|
77 | </segmentedlist> |
---|
78 | |
---|
79 | <!-- |
---|
80 | <variablelist> |
---|
81 | <bridgehead renderas="sect3">Short Descriptions</bridgehead> |
---|
82 | <?dbfo list-presentation="list"?> |
---|
83 | <?dbhtml list-presentation="table"?> |
---|
84 | |
---|
85 | <varlistentry id="bash"> |
---|
86 | <term><command>bash</command></term> |
---|
87 | <listitem> |
---|
88 | <para>A widely-used command interpreter; it performs many types of |
---|
89 | expansions and substitutions on a given command line before executing |
---|
90 | it, thus making this interpreter a powerful tool</para> |
---|
91 | <indexterm zone="ch-system-bash bash"> |
---|
92 | <primary sortas="b-bash">bash</primary> |
---|
93 | </indexterm> |
---|
94 | </listitem> |
---|
95 | </varlistentry> |
---|
96 | |
---|
97 | <varlistentry id="bashbug"> |
---|
98 | <term><command>bashbug</command></term> |
---|
99 | <listitem> |
---|
100 | <para>A shell script to help the user compose and mail standard |
---|
101 | formatted bug reports concerning <command>bash</command></para> |
---|
102 | <indexterm zone="ch-system-bash bashbug"> |
---|
103 | <primary sortas="b-bashbug">bashbug</primary> |
---|
104 | </indexterm> |
---|
105 | </listitem> |
---|
106 | </varlistentry> |
---|
107 | |
---|
108 | <varlistentry id="sh"> |
---|
109 | <term><command>sh</command></term> |
---|
110 | <listitem> |
---|
111 | <para>A symlink to the <command>bash</command> program; when invoked |
---|
112 | as <command>sh</command>, <command>bash</command> tries to mimic the |
---|
113 | startup behavior of historical versions of <command>sh</command> as |
---|
114 | closely as possible, while conforming to the POSIX standard as |
---|
115 | well</para> |
---|
116 | <indexterm zone="ch-system-bash sh"> |
---|
117 | <primary sortas="b-sh">sh</primary> |
---|
118 | </indexterm> |
---|
119 | </listitem> |
---|
120 | </varlistentry> |
---|
121 | |
---|
122 | </variablelist> |
---|
123 | --> |
---|
124 | </sect2> |
---|
125 | |
---|
126 | </sect1> |
---|