Commit 0be303ca authored by Simon Dawson's avatar Simon Dawson Committed by Peter Korsgaard
Browse files

replace references to Busybox with BusyBox 



The correct capitalised form appears to be "BusyBox" rather than "Busybox";
fix all references to the latter form. (Most such references occur in the
manual and in commentary in package makefiles.)

Signed-off-by: default avatarSimon Dawson <spdawson@gmail.com>
Signed-off-by: default avatarPeter Korsgaard <peter@korsgaard.com>
parent 65b47530

Makefile

+1 −1
Original line number Diff line number Diff line
@@ -89,7 +89,7 @@ CONFIG_DIR := $(TOPDIR) 
NEED_WRAPPER =

else

# other packages might also support Linux-style out of tree builds

# with the O=<dir> syntax (E.G. Busybox does). As make automatically

# with the O=<dir> syntax (E.G. BusyBox does). As make automatically

# forwards command line variable definitions those packages get very

# confused. Fix this by telling make to not do so

MAKEOVERRIDES =

docs/manual/common-usage.txt

+2 −2
Original line number Diff line number Diff line
@@ -76,9 +76,9 @@ to +make+ or set in the environment: 
  is the recommended way of setting it.

  +

* +BUSYBOX_CONFIG_FILE=<path/to/.config>+, path to

  the Busybox configuration file.

  the BusyBox configuration file.

  +

  Note that the Busybox configuration file can also be set from the

  Note that the BusyBox configuration file can also be set from the

  configuration interface, so through the Buildroot +.config+ file; this

  is the recommended way of setting it.

  +

docs/manual/configure.txt

+8 −8
Original line number Diff line number Diff line
@@ -272,7 +272,7 @@ different solutions to handle the +/dev+ directory : 
   requirement to have +CONFIG_DEVTMPFS+ and +CONFIG_DEVTMPFS_MOUNT+

   enabled in the kernel configuration still apply), but adds the

   +mdev+ userspace utility on top of it. +mdev+ is a program part of

   Busybox that the kernel will call every time a device is added or

   BusyBox that the kernel will call every time a device is added or

   removed. Thanks to the +/etc/mdev.conf+ configuration file, +mdev+

   can be configured to for example, set specific permissions or

   ownership on a device file, call a script or application whenever a
@@ -314,16 +314,16 @@ graphical applications, other network servers, etc.). 
Buildroot allows to use three different types of init systems, which

can be chosen from +System configuration+, +Init system+:



 * The first solution is *Busybox*. Amongst many programs, Busybox has

 * The first solution is *BusyBox*. Amongst many programs, BusyBox has

   an implementation of a basic +init+ program, which is sufficient

   for most embedded systems. Enabling the +BR2_INIT_BUSYBOX+ will

   ensure Busybox will build and install its +init+ program. This is

   the default solution in Buildroot. The Busybox +init+ program will

   ensure BusyBox will build and install its +init+ program. This is

   the default solution in Buildroot. The BusyBox +init+ program will

   read the +/etc/inittab+ file at boot to know what to do. The syntax

   of this file can be found in

   http://git.busybox.net/busybox/tree/examples/inittab (note that

   Busybox +inittab+ syntax is special: do not use a random +inittab+

   documentation from the Internet to learn about Busybox

   BusyBox +inittab+ syntax is special: do not use a random +inittab+

   documentation from the Internet to learn about BusyBox

   +inittab+). The default +inittab+ in Buildroot is stored in

   +system/skeleton/etc/inittab+. Apart from mounting a few important

   filesystems, the main job the default inittab does is to start the
@@ -336,7 +336,7 @@ can be chosen from +System configuration+, +Init system+: 
   Linux distributions, until they switched to more recent

   alternatives such as Upstart or Systemd. +sysvinit+ also works with

   an +inittab+ file (which has a slightly different syntax than the

   one from Busybox). The default +inittab+ installed with this init

   one from BusyBox). The default +inittab+ installed with this init

   solution is located in +package/sysvinit/inittab+.



 * The third solution is *systemd*. +systemd+ is the new generation
@@ -353,5 +353,5 @@ can be chosen from +System configuration+, +Init system+: 
   http://www.freedesktop.org/wiki/Software/systemd.



The solution recommended by Buildroot developers is to use the

*Busybox init* as it is sufficient for most embedded

*BusyBox init* as it is sufficient for most embedded

systems. *systemd* can be used for more complex situations.

docs/manual/customize-busybox-config.txt

+2 −2
Original line number Diff line number Diff line
@@ -2,9 +2,9 @@ 
// vim: set syntax=asciidoc:



[[busybox-custom]]

=== Customizing the Busybox configuration

=== Customizing the BusyBox configuration



http://www.busybox.net/[Busybox] is very configurable, and you may

http://www.busybox.net/[BusyBox] is very configurable, and you may

want to customize it. You can follow these simple steps to do so. This

method isn't optimal, but it's simple, and it works:

docs/manual/customize-store.txt

+2 −2
Original line number Diff line number Diff line
@@ -80,9 +80,9 @@ work. 


To do so, you need to create a normal Buildroot configuration that

builds a basic system for the hardware: toolchain, kernel, bootloader,

filesystem and a simple Busybox-only userspace. No specific package

filesystem and a simple BusyBox-only userspace. No specific package

should be selected: the configuration should be as minimal as

possible, and should only build a working basic Busybox system for the

possible, and should only build a working basic BusyBox system for the

target platform. You can of course use more complicated configurations

for your internal projects, but the Buildroot project will only

integrate basic board configurations. This is because package