summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDenys Vlasenko <vda.linux@googlemail.com>2011-03-08 11:04:09 (GMT)
committer Denys Vlasenko <vda.linux@googlemail.com>2011-03-08 11:04:09 (GMT)
commit89bb5510f435bd18ebedae2f7150eecdf99abd65 (patch)
treeb08eb380d2b1331acf5f47051d365148429d2993
parentc2ba9734566ad10982866c398961ebbf19dff4a7 (diff)
downloadbusybox-website-89bb5510f435bd18ebedae2f7150eecdf99abd65.tar.gz
busybox-website-89bb5510f435bd18ebedae2f7150eecdf99abd65.tar.bz2
FAQ.html: fix capitalization again.
Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
-rw-r--r--FAQ.html28
1 files changed, 14 insertions, 14 deletions
diff --git a/FAQ.html b/FAQ.html
index 007f55a..7b738dd 100644
--- a/FAQ.html
+++ b/FAQ.html
@@ -151,9 +151,9 @@ have additions to this FAQ document, we would love to add them,
most generic arm version (for smartphones), so those are probably good
starting points.
</p>
-<p> This is a statically linked version of the busybox "multiplexer", a
+<p> This is a statically linked version of the Busybox "multiplexer", a
single command that can perform multiple actions, the way a swiss army
- knife has multiple blades. To try it out, give busybox the command line
+ knife has multiple blades. To try it out, give Busybox the command line
you'd like it to execute:
</p>
<pre>
@@ -161,7 +161,7 @@ have additions to this FAQ document, we would love to add them,
./busybox ps
./busybox seq 1 5
</pre>
-<p> To get a list of the commands supported by this instance of busybox, run
+<p> To get a list of the commands supported by this instance of Busybox, run
it without any arguments, or use the "--list" or :
</p>
<pre>
@@ -176,7 +176,7 @@ have additions to this FAQ document, we would love to add them,
<h3>Installing Busybox</h3>
-<p> If the busybox executable is renamed to one of the commands it supports,
+<p> If the Busybox executable is renamed to one of the commands it supports,
it will act as that command automatically:
</p>
<pre>
@@ -184,11 +184,11 @@ have additions to this FAQ document, we would love to add them,
./pwd
</pre>
<p> This allows you to create a bunch of symlinks or hardlinks to the
- busybox executable, add them to your $PATH, and let a single busybox
+ Busybox executable, add them to your $PATH, and let a single Busybox
provide a standard set of command line tools. The --list option to
busybox gives the list of supported commands in an easily scriptable
form. (The --list-full option gives full paths, such as usr/sbin/test,
- to help create a busybox-based root filesystem.)
+ to help create a Busybox-based root filesystem.)
</p>
<pre>
mkdir bbdir
@@ -197,8 +197,8 @@ have additions to this FAQ document, we would love to add them,
ln -s busybox bbdir/$i
done
</pre>
-<p> To launch busybox's built in command shell with the $PATH giving access
- to just busybox's built-in commands:
+<p> To launch Busybox's built in command shell with the $PATH giving access
+ to just Busybox's built-in commands:
</p>
<pre>
PATH=$(pwd)/bbdir bbdir/sh
@@ -206,12 +206,12 @@ have additions to this FAQ document, we would love to add them,
<h3>Building Busybox from source</h3>
-<p> The prebuilt binaries are based on the default configuration of busybox,
+<p> The prebuilt binaries are based on the default configuration of Busybox,
which enables all functionality except special purpose things like
selinux or debugging support which would reduce the portability of the
resulting binary.
</p>
-<p> To build a defconfig busybox from source, download the source code from
+<p> To build a defconfig Busybox from source, download the source code from
<a href="http://busybox.net/downloads">http://busybox.net/downloads</a>
</p>
@@ -231,7 +231,7 @@ have additions to this FAQ document, we would love to add them,
name).
</p>
-<h3>Cross compiling busybox</h3>
+<h3>Cross compiling Busybox</h3>
<p> Obtain and install a cross compiler for your target. (A few prebuilt
ones are available from
@@ -244,20 +244,20 @@ have additions to this FAQ document, we would love to add them,
probably named things like "armv4tl-cc", "armv4tl-ld", and
"armv4tl-strip". In this case, "armv4tl-" would be the prefix.
</p>
-<p> So to build busybox with that cross compiler, go:
+<p> So to build Busybox with that cross compiler, go:
</p>
<pre>
make CROSS_COMPILE=armv4tl-
</pre>
<p> (Note the trailing dash, if that's part of the prefix. This is a make
- variable override preventing busybox from using its default value, which
+ variable override preventing Busybox from using its default value, which
is why it has to come on the make command line instead of as an
environment variable.)
</p>
<p> To build a static version, set the environment variable
"LDFLAGS=--static". And of course you can do a parallel SMP build with
make's -j options. So to build a static cross compiled version of
- busybox using a parallel build:
+ Busybox using a parallel build:
</p>
<pre>
LDFLAGS="--static" make -j 4 CROSS_COMPILE="armv4tl-"