[bootlin/training-materials updates] master: Embedded Linux: simplify BusyBox instructions (464483f0)

[Michael Opdenacker]

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

>---------------------------------------------------------------

commit 464483f0b30f49c9ee8d1a11923a321bc6076002
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date:   Wed Nov 10 11:46:44 2021 +0100

    Embedded Linux: simplify BusyBox instructions
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>


>---------------------------------------------------------------

464483f0b30f49c9ee8d1a11923a321bc6076002
 labs/sysdev-tinysystem/sysdev-tinysystem.tex | 22 ++++++++--------------
 1 file changed, 8 insertions(+), 14 deletions(-)

diff --git a/labs/sysdev-tinysystem/sysdev-tinysystem.tex b/labs/sysdev-tinysystem/sysdev-tinysystem.tex
index c729f5bd..2ee625c5 100644
--- a/labs/sysdev-tinysystem/sysdev-tinysystem.tex
+++ b/labs/sysdev-tinysystem/sysdev-tinysystem.tex
@@ -133,28 +133,22 @@ filesystem and finally make it usable.
 
 Download the sources of the latest BusyBox 1.34.x release.
 
-To configure BusyBox, we won't be able to use \code{make xconfig},
-which is currently broken for BusyBox in Ubuntu 20.04,
-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).
 
-If you don't use the BusyBox configuration file that we provide, at least,
-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.
+Then, you can use \inlinebash{$ make menuconfig} to further customize
+the BusyBox configuration. At least, keep the setting that
+builds a static BusyBox. 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.
 
 Build BusyBox using the toolchain that you used to build the kernel.
 
-Going back to the BusyBox configuration interface
-specify the installation directory for BusyBox\footnote{You will find
+Going back to the BusyBox configuration interface,
+check the installation directory for BusyBox\footnote{You will find
 this setting in \code{Settings -> Install Options -> BusyBox installation prefix}.}.
-It should be the path to your \code{nfsroot} directory.
+Set it to the path to your \code{nfsroot} directory.
 
 Now run \inlinebash{$ make install} to install BusyBox in this directory.