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 |
---|
21 | single small executable. It provides replacements for most of the utilities |
---|
22 | you usually find in GNU fileutils, shellutils, etc. The utilities in |
---|
23 | BusyBox generally have fewer options than their full-featured GNU cousins; |
---|
24 | however, the options that are included provide the expected functionality |
---|
25 | and behave very much like their GNU counterparts. BusyBox provides |
---|
26 | a fairly complete environment for any small or embedded system.</para> |
---|
27 | |
---|
28 | </sect2> |
---|
29 | |
---|
30 | <sect2 role="installation"> |
---|
31 | <title>Installation of Busybox</title> |
---|
32 | |
---|
33 | <para os="p1">The following patch contains a number of fixes to version |
---|
34 | &busybox-version; by the Busybox developers:</para> |
---|
35 | |
---|
36 | <screen os="p2"><userinput>patch -Np1 -i ../&busybox-fixes-patch;</userinput></screen> |
---|
37 | |
---|
38 | <para os="a">The following patch contains a default configuration for busybox:</para> |
---|
39 | |
---|
40 | <screen os="b"><userinput>patch -Np1 -i ../&busybox-config-patch; |
---|
41 | cp -v clfs/config .config</userinput></screen> |
---|
42 | |
---|
43 | <note os="c"> |
---|
44 | <para>Currently we are just telling Busybox to use a generic |
---|
45 | configuration. For those for more adventureous, you can use |
---|
46 | <command>make menuconfig</command>, and create a custom or modified |
---|
47 | configuration for your build.</para> |
---|
48 | </note> |
---|
49 | |
---|
50 | <para os="d">The following tells BusyBox to validate the configuration, |
---|
51 | and makes sure all required options are defined:</para> |
---|
52 | |
---|
53 | <screen os="e"><userinput>make oldconfig</userinput></screen> |
---|
54 | |
---|
55 | <para os="f">Compile the package:</para> |
---|
56 | |
---|
57 | <screen os="g"><userinput>make CROSS_COMPILE="${CLFS_TARGET}-"</userinput></screen> |
---|
58 | |
---|
59 | <para os="h">Install the package:</para> |
---|
60 | |
---|
61 | <screen os="i"><userinput>make CROSS_COMPILE="${CLFS_TARGET}-" \ |
---|
62 | CONFIG_PREFIX="${CLFS}" install</userinput></screen> |
---|
63 | |
---|
64 | <para os="j">If your going to build your kernel with modules, you will need |
---|
65 | to make sure <command>depmod.pl</command> is available:</para> |
---|
66 | |
---|
67 | <screen os="k"><userinput>cp examples/depmod.pl ${CLFS}/cross-tools/bin |
---|
68 | chmod 755 ${CLFS}/cross-tools/bin/depmod.pl</userinput></screen> |
---|
69 | |
---|
70 | </sect2> |
---|
71 | |
---|
72 | <sect2 id="contents-busybox" role="content"> |
---|
73 | <title>Contents of Busybox</title> |
---|
74 | |
---|
75 | <segmentedlist> |
---|
76 | <segtitle>Installed programs</segtitle> |
---|
77 | |
---|
78 | <seglistitem> |
---|
79 | <seg>To be Written</seg> |
---|
80 | </seglistitem> |
---|
81 | </segmentedlist> |
---|
82 | |
---|
83 | <!-- |
---|
84 | <variablelist> |
---|
85 | <bridgehead renderas="sect3">Short Descriptions</bridgehead> |
---|
86 | <?dbfo list-presentation="list"?> |
---|
87 | <?dbhtml list-presentation="table"?> |
---|
88 | |
---|
89 | <varlistentry id="bash"> |
---|
90 | <term><command>bash</command></term> |
---|
91 | <listitem> |
---|
92 | <para>A widely-used command interpreter; it performs many types of |
---|
93 | expansions and substitutions on a given command line before executing |
---|
94 | it, thus making this interpreter a powerful tool</para> |
---|
95 | <indexterm zone="ch-system-bash bash"> |
---|
96 | <primary sortas="b-bash">bash</primary> |
---|
97 | </indexterm> |
---|
98 | </listitem> |
---|
99 | </varlistentry> |
---|
100 | |
---|
101 | <varlistentry id="bashbug"> |
---|
102 | <term><command>bashbug</command></term> |
---|
103 | <listitem> |
---|
104 | <para>A shell script to help the user compose and mail standard |
---|
105 | formatted bug reports concerning <command>bash</command></para> |
---|
106 | <indexterm zone="ch-system-bash bashbug"> |
---|
107 | <primary sortas="b-bashbug">bashbug</primary> |
---|
108 | </indexterm> |
---|
109 | </listitem> |
---|
110 | </varlistentry> |
---|
111 | |
---|
112 | <varlistentry id="sh"> |
---|
113 | <term><command>sh</command></term> |
---|
114 | <listitem> |
---|
115 | <para>A symlink to the <command>bash</command> program; when invoked |
---|
116 | as <command>sh</command>, <command>bash</command> tries to mimic the |
---|
117 | startup behavior of historical versions of <command>sh</command> as |
---|
118 | closely as possible, while conforming to the POSIX standard as |
---|
119 | well</para> |
---|
120 | <indexterm zone="ch-system-bash sh"> |
---|
121 | <primary sortas="b-sh">sh</primary> |
---|
122 | </indexterm> |
---|
123 | </listitem> |
---|
124 | </varlistentry> |
---|
125 | |
---|
126 | </variablelist> |
---|
127 | --> |
---|
128 | </sect2> |
---|
129 | |
---|
130 | </sect1> |
---|