[bootlin/training-materials updates] master: Replace "Busybox" by "BusyBox" (a6b00d61)

Michael Opdenacker michael.opdenacker at bootlin.com
Mon Jul 19 11:53:22 CEST 2021

Repository : https://github.com/bootlin/training-materials
On branch  : master
Link       : https://github.com/bootlin/training-materials/commit/a6b00d61183f1986007c198cf27aced0bc89dd55


commit a6b00d61183f1986007c198cf27aced0bc89dd55
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date:   Mon Jul 19 11:53:22 2021 +0200

    Replace "Busybox" by "BusyBox"
    That's how the project names itself
    Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>


 labs/boot-time-application/boot-time-application.tex   |  4 ++--
 .../boot-time-filesystem-optimizations.tex             |  2 +-
 labs/boot-time-init-scripts/boot-time-init-scripts.tex |  6 +++---
 labs/buildroot-basic/buildroot-basic.tex               |  2 +-
 labs/buildroot-rootfs/buildroot-rootfs.tex             |  2 +-
 labs/sysdev-buildroot/sysdev-buildroot.tex             |  4 ++--
 labs/sysdev-tinysystem/sysdev-tinysystem.tex           | 18 +++++++++---------
 .../buildroot-advanced-packages.tex                    |  4 ++--
 slides/buildroot-internals/buildroot-internals.tex     |  2 +-
 slides/buildroot-rootfs/buildroot-rootfs.tex           |  6 +++---
 slides/sysdev-busybox/sysdev-busybox.tex               | 14 +++++++-------
 slides/sysdev-embedded-linux/sysdev-embedded-linux.tex | 10 +++++-----
 12 files changed, 37 insertions(+), 37 deletions(-)

diff --git a/labs/boot-time-application/boot-time-application.tex b/labs/boot-time-application/boot-time-application.tex
index caee8a8d..39ccb1f3 100644
--- a/labs/boot-time-application/boot-time-application.tex
+++ b/labs/boot-time-application/boot-time-application.tex
@@ -133,7 +133,7 @@ tree
 The \code{tree} command really makes this task easier.
-For the moment, don't bother about Busybox and system files. They will
+For the moment, don't bother about BusyBox and system files. They will
 be addressed later. Better focus on files and libraries related to
@@ -253,7 +253,7 @@ fi
-\item It seems you can not run an empty \code{while} loop with Busybox
+\item It seems you can not run an empty \code{while} loop with BusyBox
       \code{sh}. That's why I had to put a real command (not a comment)
       inside the loop.
 \item Fortunately, the \code{sleep} command supports subsecond waiting.
diff --git a/labs/boot-time-filesystem-optimizations/boot-time-filesystem-optimizations.tex b/labs/boot-time-filesystem-optimizations/boot-time-filesystem-optimizations.tex
index 27d87d60..5217ae93 100644
--- a/labs/boot-time-filesystem-optimizations/boot-time-filesystem-optimizations.tex
+++ b/labs/boot-time-filesystem-optimizations/boot-time-filesystem-optimizations.tex
@@ -87,7 +87,7 @@ devtmpfs} filesystem mounted automatically on \code{/dev}. We'll mount
 it from our \code{playvideo} script.
-   \item Modify the Busybox configuration to add support for the
+   \item Modify the BusyBox configuration to add support for the
    \code{mount} command (found in \code{Linux System Utilities}), without
     any additional option.
    \item Add the following line to the \code{/playvideo} file:\\
diff --git a/labs/boot-time-init-scripts/boot-time-init-scripts.tex b/labs/boot-time-init-scripts/boot-time-init-scripts.tex
index 44209715..0959286b 100644
--- a/labs/boot-time-init-scripts/boot-time-init-scripts.tex
+++ b/labs/boot-time-init-scripts/boot-time-init-scripts.tex
@@ -33,7 +33,7 @@ Update your root filesystem on the SD card.
 The next thing to do is to use the \code{init} argument on the
 kernel command line (in \code{u-boot}, this is the \code{bootargs}
 environment variable) to boot using \code{bootchart} instead of using
-the \code{init} program provided by Busybox.
+the \code{init} program provided by BusyBox.
 So, boot your board but stay in the U-Boot shell, by pressing the
 \code{Space} key before the timer expires.
@@ -313,7 +313,7 @@ Check and write down the new size of the root filesystem archive.
 \subsection{Reducing BusyBox to the minimum}
 While we're simplifying the root filesystem, it's time to reduce the
-configuration of Busybox, to only contain the features we need in our
+configuration of BusyBox, to only contain the features we need in our
 Before we do this, check the size of the \code{busybox} executable in
@@ -363,7 +363,7 @@ cp output/build/busybox-1.31.1/.config board/beaglecam/busybox.config
 Then, run \code{make menuconfig} and set
 \code{BR2_PACKAGE_BUSYBOX_CONFIG} to this new file. In \code{System
 configuration}, also set \code{Init system} to \code{None}. Otherwise
-Buildroot will enable Busybox \code{init} into your configuration.
+Buildroot will enable BusyBox \code{init} into your configuration.
 Run \code{make}, and update your SD card.
 Check the new size of \code{/bin/busybox}!
diff --git a/labs/buildroot-basic/buildroot-basic.tex b/labs/buildroot-basic/buildroot-basic.tex
index 592c4dd9..542eee5e 100644
--- a/labs/buildroot-basic/buildroot-basic.tex
+++ b/labs/buildroot-basic/buildroot-basic.tex
@@ -207,7 +207,7 @@ Now, let's do the configuration:
   menu, as this is the one where you can select amongst the 2800+
   available Buildroot packages which ones should be built and
   installed in your system. For our basic system, enabling
-  \code{Busybox} is sufficient and is already enabled by default, but
+  \code{BusyBox} is sufficient and is already enabled by default, but
   feel free to explore the available packages. We'll have the
   opportunity to enable some more packages in the next labs.
diff --git a/labs/buildroot-rootfs/buildroot-rootfs.tex b/labs/buildroot-rootfs/buildroot-rootfs.tex
index 2163ca14..d7a45693 100644
--- a/labs/buildroot-rootfs/buildroot-rootfs.tex
+++ b/labs/buildroot-rootfs/buildroot-rootfs.tex
@@ -83,7 +83,7 @@ scripts named \code{SXX*} in \code{/etc/init.d}.
 \subsection{IP address configuration}
-By default, Buildroot uses the \code{ifup} program from Busybox, which
+By default, Buildroot uses the \code{ifup} program from BusyBox, which
 reads the \code{/etc/network/interfaces} file to configure network
 interfaces. So, in \code{board/felabs/beagleboneblack/rootfs-overlay},
 create a file named \code{etc/network/interfaces} with the following
diff --git a/labs/sysdev-buildroot/sysdev-buildroot.tex b/labs/sysdev-buildroot/sysdev-buildroot.tex
index b87b4b25..1ae81bea 100644
--- a/labs/sysdev-buildroot/sysdev-buildroot.tex
+++ b/labs/sysdev-buildroot/sysdev-buildroot.tex
@@ -51,7 +51,7 @@ In our case, we would like to:
 \item Generate an embedded Linux system for ARM;
 \item Use an already existing external toolchain instead of having
   Buildroot generating one for us;
-\item Integrate {\em Busybox}, {\em alsa-utils} and {\em vorbis-tools}
+\item Integrate {\em BusyBox}, {\em alsa-utils} and {\em vorbis-tools}
   in our embedded Linux system;
 \item Integrate the target filesystem into a tarball
@@ -107,7 +107,7 @@ button whenever you need more details about a given option:
 \item \code{Target packages}
-  \item Keep \code{BusyBox} (default version) and keep the Busybox
+  \item Keep \code{BusyBox} (default version) and keep the BusyBox
     configuration proposed by Buildroot;
   \item \code{Audio and video applications}
diff --git a/labs/sysdev-tinysystem/sysdev-tinysystem.tex b/labs/sysdev-tinysystem/sysdev-tinysystem.tex
index fc6e4dc7..3fb24e4b 100644
--- a/labs/sysdev-tinysystem/sysdev-tinysystem.tex
+++ b/labs/sysdev-tinysystem/sysdev-tinysystem.tex
@@ -126,10 +126,10 @@ kernel. See Linux Documentation/admin-guide/init.rst for guidance.
 Obviously, our root filesystem being mostly empty, there isn't such an
-application yet. In the next paragraph, you will add Busybox to your root
+application yet. In the next paragraph, you will add BusyBox to your root
 filesystem and finally make it usable.
-\section{Root filesystem with Busybox}
+\section{Root filesystem with BusyBox}
 Download the sources of the latest BusyBox 1.33.x release.
@@ -140,14 +140,14 @@ because it requires an old version of the Qt library.
 So, let's use \inlinebash{$ make menuconfig}.
 Now, configure BusyBox with the configuration file provided in the
-\code{data/} directory (remember that the Busybox configuration file
-is \code{.config} in the Busybox sources).
+\code{data/} directory (remember that the BusyBox configuration file
+is \code{.config} in the BusyBox sources).
 If you don't use the BusyBox configuration file that we provide, at least,
-make sure you build BusyBox statically! Compiling Busybox
+make sure you build BusyBox statically! Compiling BusyBox
 statically in the first place makes it easy to set up the system,
 because there are no dependencies on libraries. Later on, we will set
-up shared libraries and recompile Busybox.
+up shared libraries and recompile BusyBox.
 Build BusyBox using the toolchain that you used to build the kernel.
@@ -257,13 +257,13 @@ seeing the changes made on the NFS server.
 Similarly, find the missing libraries in the toolchain and copy
 them to \code{lib/} on the target.
-Once the small test program works, we are going to recompile Busybox
-without the static compilation option, so that Busybox takes
+Once the small test program works, we are going to recompile BusyBox
+without the static compilation option, so that BusyBox takes
 advantages of the shared libraries that are now present on the target.
 Before doing that, measure the size of the \code{busybox} executable.
-Then, build Busybox with shared libraries, and install it again on the
+Then, build BusyBox with shared libraries, and install it again on the
 target filesystem. Make sure that the system still boots and see how
 much smaller the \code{busybox} executable got.
diff --git a/slides/buildroot-advanced-packages/buildroot-advanced-packages.tex b/slides/buildroot-advanced-packages/buildroot-advanced-packages.tex
index f20497b9..dae526e4 100644
--- a/slides/buildroot-advanced-packages/buildroot-advanced-packages.tex
+++ b/slides/buildroot-advanced-packages/buildroot-advanced-packages.tex
@@ -538,11 +538,11 @@ endef
 \item Buildroot supports several main init systems: {\em sysvinit},
-  {\em Busybox}, {\em systemd}, {\em OpenRC}
+  {\em BusyBox}, {\em systemd}, {\em OpenRC}
 \item When packages want to install a program to be started at boot
   time, they need to install a startup script ({\em
-    sysvinit}/{\em Busybox}), a {\em systemd service} file, etc.
+    sysvinit}/{\em BusyBox}), a {\em systemd service} file, etc.
 \item They can do so using the following variables, which contain a
   list of shell commands.
diff --git a/slides/buildroot-internals/buildroot-internals.tex b/slides/buildroot-internals/buildroot-internals.tex
index b21ea5e0..2a8bdd0f 100644
--- a/slides/buildroot-internals/buildroot-internals.tex
+++ b/slides/buildroot-internals/buildroot-internals.tex
@@ -168,7 +168,7 @@ $(BUILD_DIR)/%/.stamp_downloaded:
 \item Step handled by the package infrastructure
 \item In all {\em stamp file targets}, \code{PKG} is the upper case
-  name of the package. So when used for Busybox,
+  name of the package. So when used for BusyBox,
   \code{$($(PKG)_SOURCE)} is the value of \code{BUSYBOX_SOURCE}.
 \item {\em Hooks}: make macros called before and after each step.
 \item \code{<pkg>_ALL_DOWNLOADS} lists all the files to be downloaded,
diff --git a/slides/buildroot-rootfs/buildroot-rootfs.tex b/slides/buildroot-rootfs/buildroot-rootfs.tex
index 15f90e0e..40f00a45 100644
--- a/slides/buildroot-rootfs/buildroot-rootfs.tex
+++ b/slides/buildroot-rootfs/buildroot-rootfs.tex
@@ -61,7 +61,7 @@
 \begin{frame}{Installation of packages}
   \item All the selected target packages will be built (can be
-    Busybox, Qt, OpenSSH, lighttpd, and many more)
+    BusyBox, Qt, OpenSSH, lighttpd, and many more)
   \item Most of them will install files in \code{$(TARGET_DIR)}:
     programs, libraries, fonts, data files, configuration files, etc.
   \item This is really the step that will bring the vast majority of
@@ -307,7 +307,7 @@ test         8000  wheel   -1    =          -         /bin/sh -           Test u
   \item Buildroot supports multiple {\em init} implementations:
-    \item {\bf Busybox init}, the default. Simplest solution.
+    \item {\bf BusyBox init}, the default. Simplest solution.
     \item {\bf sysvinit}, the old style featureful {\em init}
     \item {\bf systemd}, the modern init system
@@ -334,7 +334,7 @@ test         8000  wheel   -1    =          -         /bin/sh -           Test u
       Default option.
     \item Using {\bf static /dev}. This is the old way of doing
       \code{/dev}, not very practical.
-    \item Using {\bf mdev}. \code{mdev} is part of Busybox and can run
+    \item Using {\bf mdev}. \code{mdev} is part of BusyBox and can run
       custom actions when devices are added/removed. Requires {\em
         devtmpfs} kernel support.
     \item Using {\bf eudev}. Forked from \code{systemd}, allows to run
diff --git a/slides/sysdev-busybox/sysdev-busybox.tex b/slides/sysdev-busybox/sysdev-busybox.tex
index cb153f8c..aa81df37 100644
--- a/slides/sysdev-busybox/sysdev-busybox.tex
+++ b/slides/sysdev-busybox/sysdev-busybox.tex
@@ -1,7 +1,7 @@
-  \frametitle{Why Busybox?}
+  \frametitle{Why BusyBox?}
   \item A Linux system needs a basic set of programs to work
@@ -21,7 +21,7 @@
       mind: they are not very configurable and have a wide range of
-  \item Busybox is an alternative solution, extremely common on
+  \item BusyBox is an alternative solution, extremely common on
     embedded systems
@@ -59,7 +59,7 @@
         \item Symbolic links to \code{/bin/busybox} are created for each
-          application integrated into Busybox
+          application integrated into BusyBox
       \item For a fairly featureful configuration, less than 500 KB
         (statically compiled with uClibc) or less than 1 MB (statically
@@ -182,9 +182,9 @@ yes, zcat, zcip}
-  \frametitle{Applet highlight: Busybox init}
+  \frametitle{Applet highlight: BusyBox init}
-  \item Busybox provides an implementation of an \code{init} program
+  \item BusyBox provides an implementation of an \code{init} program
   \item Simpler than the init implementation found on desktop/server
     systems ({\em SysV init} or {\em systemd})
   \item A single configuration file: \code{/etc/inittab}
@@ -193,7 +193,7 @@ yes, zcat, zcip}
   \item Allows to run services at startup, and to make sure that
     certain services are always running on the system
-  \item See \projfile{busybox}{examples/inittab} in Busybox for details on the
+  \item See \projfile{busybox}{examples/inittab} in BusyBox for details on the
diff --git a/slides/sysdev-embedded-linux/sysdev-embedded-linux.tex b/slides/sysdev-embedded-linux/sysdev-embedded-linux.tex
index 66dbcf92..5a8b9654 100644
--- a/slides/sysdev-embedded-linux/sysdev-embedded-linux.tex
+++ b/slides/sysdev-embedded-linux/sysdev-embedded-linux.tex
@@ -141,7 +141,7 @@
     \hfill \includegraphics[width=6em]{slides/sysdev-embedded-linux/gpl-v3.pdf}
   \item Covers around 55\% of the free software projects
-    \item Including the Linux kernel, Busybox and many applications
+    \item Including the Linux kernel, BusyBox and many applications
   \item Is a copyleft license
@@ -150,7 +150,7 @@
     \item Programs linked with a library released under the GPL must
       also be released under the GPL
-  \item Some programs covered by version 2 (Linux kernel, Busybox, U-Boot...)
+  \item Some programs covered by version 2 (Linux kernel, BusyBox, U-Boot...)
   \item A number of programs are covered by version 3, released in 2007:
 	gcc, bash, grub, samba, Qt...
@@ -223,7 +223,7 @@
       source code to your customers.
   \item You make modifications to the Linux kernel (to add drivers or
-    adapt to your board), to Busybox, U-Boot or other GPL software
+    adapt to your board), to BusyBox, U-Boot or other GPL software
     \item You must release the modified versions under the same
@@ -890,7 +890,7 @@ met:
       \code{/var}, \code{/sbin}
     \item A set of basic utilities, providing at least the \code{init}
       program, a shell and other traditional UNIX command line
-      tools. This is usually provided by {\em Busybox}
+      tools. This is usually provided by {\em BusyBox}
     \item The C library and the related libraries (thread, math, etc.)
       installed in \code{/lib}
     \item A few configuration files, such as \code{/etc/inittab}, and
@@ -904,7 +904,7 @@ met:
   \frametitle{Target and build spaces}
-  \item The system foundation, Busybox and C library, are the core of
+  \item The system foundation, BusyBox and C library, are the core of
     the target root filesystem
   \item However, when building other components, one must distinguish
     two directories

More information about the training-materials-updates mailing list