Boot time: libraries update

Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>

slides/boot-time-init-scripts/boot-time-init-scripts.tex

@@ -177,7 +177,7 @@ \section{Optimizing init scripts and system startup}
 
 \begin{frame}
 \frametitle{Reduce size (2)}
-You may try \code{mklibs}, available at \url{http://packages.debian.org/sid/mklibs}.
+You may try \code{mklibs}, available at \url{https://packages.debian.org/sid/mklibs}.
 \begin{itemize}
 	\item \code{mklibs} produces cut-down shared libraries that contain
 	only the routines required by a particular set of executables.
@@ -194,7 +194,7 @@ \section{Optimizing init scripts and system startup}
 Often the first sign of life that you are showing!
 \begin{itemize}
 \item You could use the \code{fbv} program
-      (\url{http://freecode.com/projects/fbv})\\
+      (\url{http://freshmeat.sourceforge.net/projects/fbv})\\
       to display your splashscreen.
 \item On \code{armel}, you can just use our statically compiled
       binary:\\

slides/boot-time-init-scripts3/boot-time-init-scripts3.tex

@@ -19,8 +19,8 @@
 \begin{itemize}
 \item Statically linked executables are very useful to reduce size
       (especially in small initramfs), and require less work to start.
-\item However, the LGPL license in libraries (uClibc, glibc), require
-      to leave the user the ability to relink the executable
+\item However, the LGPL license in the uClibc and glibc libraries
+      require to leave the user the ability to relink the executable
       with a modified version of the library.
 \item Solution to keep static binaries:
       \begin{itemize}
@@ -31,6 +31,8 @@
       \item Or also provide a dynamically linked version of the
 	    executable (in a separate way), allowing to use another
             library version.
+      \item Easiest solution: build your static executables with the
+	    \code{musl} library (MIT license: no trouble)
       \end{itemize}
 \item References: \\
       {\footnotesize