[bootlin/training-materials updates] master: Boot time slides: mention "CONFIG_FEATURE_PREFER_APPLETS" in BusyBox (52ad69fa)
Michael Opdenacker
michael.opdenacker at bootlin.com
Mon May 2 14:58:50 CEST 2022
Repository : https://github.com/bootlin/training-materials
On branch : master
Link : https://github.com/bootlin/training-materials/commit/52ad69fa746c6b23c14175b0c532d62f10406110
>---------------------------------------------------------------
commit 52ad69fa746c6b23c14175b0c532d62f10406110
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date: Mon May 2 14:58:50 2022 +0200
Boot time slides: mention "CONFIG_FEATURE_PREFER_APPLETS" in BusyBox
Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>
>---------------------------------------------------------------
52ad69fa746c6b23c14175b0c532d62f10406110
.../boot-time-init-scripts.tex | 36 +++++++++++++---------
1 file changed, 22 insertions(+), 14 deletions(-)
diff --git a/slides/boot-time-init-scripts/boot-time-init-scripts.tex b/slides/boot-time-init-scripts/boot-time-init-scripts.tex
index ad47a7c8..3d65e962 100644
--- a/slides/boot-time-init-scripts/boot-time-init-scripts.tex
+++ b/slides/boot-time-init-scripts/boot-time-init-scripts.tex
@@ -142,27 +142,35 @@ int main (void)
BusyBox, you can use \code{echo}, \code{test}, \code{printf}
and others as shell built-ins. At run time, use the \code{type}
command to check whether a command is a built-in. Example:
- \code{type echo}
-\item Pipes and back-quotes are also implemented by
- \code{fork}/\code{exec}. You can reduce their usage in
- scripts. Example:
- \begin{block}{}
- \begin{verbatim}
+ \code{type echo}.
+\item BusyBox also has a {\em exec prefer applets} setting
+ (\code{CONFIG_FEATURE_PREFER_APPLETS}) trying to run the corresponding
+ applet (instead of making an \code{exec} call), typically in shells
+ or in commands such as \code{find -exec}.
+\end{itemize}
+\end{frame}
+
+\begin{frame}[fragile]
+\frametitle{Reduce forking (2)}
+Pipes and back-quotes are also implemented by
+\code{fork}/\code{exec}. You can reduce their usage in
+scripts. Example:
+\begin{block}{}
+\begin{verbatim}
cat /proc/cpuinfo | grep model
- \end{verbatim}
- \end{block}
+\end{verbatim}
+\end{block}
Replace it with:
- \begin{block}{}
- \begin{verbatim}
+\begin{block}{}
+\begin{verbatim}
grep model /proc/cpuinfo
- \end{verbatim}
- \end{block}
-\end{itemize}
+\end{verbatim}
+\end{block}
See \url{https://elinux.org/Optimize_RC_Scripts}
\end{frame}
\begin{frame}[fragile]
-\frametitle{Reduce forking (2)}
+\frametitle{Reduce forking (3)}
Replaced:
\begin{block}{}
\begin{verbatim}
More information about the training-materials-updates
mailing list