[FE training-materials-updates] buildroot-slides: misc fixes

Thomas Petazzoni thomas.petazzoni at free-electrons.com
Thu May 7 16:19:58 CEST 2015

Repository : git://git.free-electrons.com/training-materials.git

On branch  : master
Link       : http://git.free-electrons.com/training-materials/commit/?id=7383e20057154507f3e5e2fede72d61ed05ea89e


commit 7383e20057154507f3e5e2fede72d61ed05ea89e
Author: Thomas Petazzoni <thomas.petazzoni at free-electrons.com>
Date:   Thu May 7 16:19:13 2015 +0200

    buildroot-slides: misc fixes
    Reported-by: Peter Korsgaard <peter at korsgaard.com>
    Signed-off-by: Thomas Petazzoni <thomas.petazzoni at free-electrons.com>


 .../buildroot-advanced-packages.tex                      | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/slides/buildroot-advanced-packages/buildroot-advanced-packages.tex b/slides/buildroot-advanced-packages/buildroot-advanced-packages.tex
index 16f82dd..72c7631 100644
--- a/slides/buildroot-advanced-packages/buildroot-advanced-packages.tex
+++ b/slides/buildroot-advanced-packages/buildroot-advanced-packages.tex
@@ -234,12 +234,12 @@ endef
-\item Buildroot supports two main init system: {\em sysvinit/Busybox}
-  and {\em systemd}
+\item Buildroot supports several main init systems: {\em sysvinit},
+  {\em Busybox} and {\em systemd}
 \item When packages want to install a program to be started at boot
-  time, they need to install either a startup script ({\em sysvinit})
-  or a {\em systemd service} file.
+  time, they need to install either a startup script ({\em
+    sysvinit}/{\em Busybox}) or a {\em systemd service} file.
 \item They can do so with the \code{<pkg>_INSTALL_INIT_SYSV} and
   \code{<pkg>_INSTALL_INIT_SYSTEMD} variables, which contain a list of
@@ -466,11 +466,11 @@ $(eval $(autotools-package))
     value in the \code{.config} is silently removed.
   \item Due to this, when users upgrade Buildroot, they generally
     don't know that an option they were using has been removed.
-  \item To prevent this, Buildroot keeps in \code{Config.in.legacy}
-    handling all the removed options, and when one of them is enabled
+  \item Buildroot therefore adds the removed config option to
+    \code{Config.in.legacy} with a description of what has
+    happened.
+  \item If any of these legacy options is enabled then Buildroot
     refuses to build.
-  \item When options that have been part of a Buildroot release are
-    removed, they are moved to this file.

More information about the training-materials-updates mailing list