[BL training-materials-updates] Update static-binaries repo
Michael Opdenacker
michael.opdenacker at bootlin.com
Thu Feb 14 15:35:20 CET 2019
Repository : git://git.bootlin.com/training-materials.git
On branch : master
Link : https://git.bootlin.com/training-materials/commit/?id=ec0430448ee6eb37c2b95c29438a7f56ec374de2
>---------------------------------------------------------------
commit ec0430448ee6eb37c2b95c29438a7f56ec374de2
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date: Thu Feb 14 15:34:40 2019 +0100
Update static-binaries repo
- Moved to GitHub
Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>
>---------------------------------------------------------------
ec0430448ee6eb37c2b95c29438a7f56ec374de2
slides/boottime-application/boottime-application.tex | 2 +-
slides/boottime-init-scripts3/boottime-init-scripts3.tex | 2 +-
.../sysdev-application-development/sysdev-application-development.tex | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/slides/boottime-application/boottime-application.tex b/slides/boottime-application/boottime-application.tex
index 6a04aac..d7a0a32 100644
--- a/slides/boottime-application/boottime-application.tex
+++ b/slides/boottime-application/boottime-application.tex
@@ -29,7 +29,7 @@
\item \code{strace} can be compiled by your build system
\item Even easier: drop a ready-made static binary for your
architecture, just when you need it. See
- \url{https://git.bootlin.com/users/michael-opdenacker/static-binaries/tree/strace}
+ \url{https://github.com/bootlin/static-binaries/tree/master/strace}
\item Recommended usage: \\
\code{strace -f -tt -o strace.log <program> <arguments>}
\begin{itemize}
diff --git a/slides/boottime-init-scripts3/boottime-init-scripts3.tex b/slides/boottime-init-scripts3/boottime-init-scripts3.tex
index 28bd136..fdb2e6e 100644
--- a/slides/boottime-init-scripts3/boottime-init-scripts3.tex
+++ b/slides/boottime-init-scripts3/boottime-init-scripts3.tex
@@ -104,7 +104,7 @@ Often the first sign of life that you are showing!
to display your splashscreen.
\item On \code{armel}, you can just use our statically compiled
binary: {\tiny
-\url{https://git.bootlin.com/users/michael-opdenacker/static-binaries/tree/fbv}}
+\url{https://github.com/bootlin/static-binaries/tree/master/fbv/}}
\item However, this is slow:\\
878 ms on an Microchip AT91SAM9263 system!
\end{itemize}
diff --git a/slides/sysdev-application-development/sysdev-application-development.tex b/slides/sysdev-application-development/sysdev-application-development.tex
index 30e7035..f6ea270 100644
--- a/slides/sysdev-application-development/sysdev-application-development.tex
+++ b/slides/sysdev-application-development/sysdev-application-development.tex
@@ -520,7 +520,7 @@
Can be built by your cross-compiling toolchain generator.
\item Even easier: drop a ready-made static binary for your
architecture, just when you need it. See
- \url{https://git.bootlin.com/users/michael-opdenacker/static-binaries/tree/strace}
+ \url{https://github.com/bootlin/static-binaries/tree/master/strace}
\item Allows to see what any of your processes is doing:\\
accessing files, allocating memory...\\
Often sufficient to find simple bugs.
More information about the training-materials-updates
mailing list