[FE training-materials-updates] Rename felabs-<course> to <course-labs>
Michael Opdenacker
michael.opdenacker at free-electrons.com
Mon Sep 1 22:38:43 CEST 2014
Repository : git://git.free-electrons.com/training-materials.git
On branch : master
Link : http://git.free-electrons.com/training-materials/commit/?id=7ea6249146309fd7ea79a352bad1ac36176188c0
>---------------------------------------------------------------
commit 7ea6249146309fd7ea79a352bad1ac36176188c0
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date: Mon Sep 1 22:25:24 2014 +0200
Rename felabs-<course> to <course-labs>
If the archive names is now <course>-labs.tar.xz, so should
the real directory after extraction.
Now, everything should be consistent.
Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com>
>---------------------------------------------------------------
7ea6249146309fd7ea79a352bad1ac36176188c0
.gitignore | 2 +-
Makefile | 2 +-
gen-lab-archive | 4 +-
.../modules/nfsroot/root/debugging/Makefile | 2 +-
.../modules/nfsroot/root/hello/Makefile | 2 +-
.../modules/nfsroot/root/nunchuk/Makefile | 2 +-
.../modules/nfsroot/root/serial/Makefile | 2 +-
labs/android-adb/android-adb.tex | 2 +-
labs/android-application/android-application.tex | 2 +-
labs/android-boot/android-boot.tex | 10 +--
.../android-first-compilation.tex | 4 +-
labs/android-jni-library/android-jni-library.tex | 4 +-
labs/android-native-app/android-native-app.tex | 2 +-
labs/android-new-board/android-new-board.tex | 4 +-
labs/android-source-code/android-source-code.tex | 4 +-
labs/boottime-install/boottime-install.tex | 4 +-
labs/kernel-board-setup/kernel-board-setup.tex | 2 +-
.../host-vs-target.dia | 2 +-
.../kernel-compiling-and-nfs-booting.tex | 6 +-
labs/kernel-debugging/kernel-debugging.tex | 4 +-
labs/kernel-git/kernel-git.tex | 2 +-
.../kernel-i2c-communication.tex | 4 +-
.../kernel-i2c-device-model.tex | 4 +-
labs/kernel-module-simple/kernel-module-simple.tex | 6 +-
labs/kernel-serial-iomem/kernel-serial-iomem.tex | 2 +-
labs/kernel-serial-output/kernel-serial-output.tex | 2 +-
.../kernel-sources-download.tex | 4 +-
.../kernel-sources-exploring.tex | 2 +-
labs/setup/setup.tex | 8 +--
.../sysdev-application-debugging.tex | 2 +-
.../sysdev-application-development.tex | 4 +-
.../sysdev-block-filesystems.tex | 2 +-
labs/sysdev-buildroot/sysdev-buildroot.tex | 4 +-
.../sysdev-flash-filesystems.tex | 2 +-
.../sysdev-kernel-cross-compiling.tex | 2 +-
.../sysdev-kernel-fetch-and-patch.tex | 2 +-
labs/sysdev-real-time/sysdev-real-time.tex | 20 +++---
labs/sysdev-thirdparty/sysdev-thirdparty.tex | 72 +++++++++++-----------
labs/sysdev-tinysystem/host-vs-target.dia | 2 +-
labs/sysdev-tinysystem/sysdev-tinysystem.tex | 8 +--
labs/sysdev-toolchain/sysdev-toolchain.tex | 2 +-
labs/sysdev-u-boot/sysdev-u-boot.tex | 2 +-
labs/yocto-first-build/yocto-first-build.tex | 2 +-
43 files changed, 113 insertions(+), 113 deletions(-)
diff --git a/.gitignore b/.gitignore
index 779ef11..f15b718 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,4 +1,4 @@
out/
*.pdf
-felabs-*/
+*-labs/
*~
diff --git a/Makefile b/Makefile
index 6e54d90..7c3f73e 100644
--- a/Makefile
+++ b/Makefile
@@ -550,7 +550,7 @@ $(VARS): FORCE
/bin/echo "\def \training {$(TRAINING)}" >> $@
clean:
- $(RM) -rf $(OUTDIR) *.pdf felabs-*
+ $(RM) -rf $(OUTDIR) *.pdf *-labs
all: full-sysdev-slides.pdf full-sysdev-labs.pdf full-kernel-slides.pdf full-kernel-labs.pdf full-android-slides.pdf full-android-labs.pdf full-boottime-slides.pdf full-boottime-labs.pdf kernel-agenda.pdf android-agenda.pdf boottime-agenda.pdf
diff --git a/gen-lab-archive b/gen-lab-archive
index 2648b55..f7214c5 100755
--- a/gen-lab-archive
+++ b/gen-lab-archive
@@ -1,7 +1,7 @@
#!/bin/sh
# Produces the lab archive that is published on
-# http://free-electrons.com/labs/felabs-<session>.tar.xz
+# http://free-electrons.com/labs/<session>-labs.tar.xz
ECHO=/bin/echo
GIT=/usr/bin/git
@@ -30,7 +30,7 @@ if ! ls lab-data | grep -q $1; then
exit 1
fi
-FELABS=felabs-$1
+FELABS=$1-labs
# Updating repo
diff --git a/lab-data/linux-kernel/modules/nfsroot/root/debugging/Makefile b/lab-data/linux-kernel/modules/nfsroot/root/debugging/Makefile
index 70c9b24..23c6f0f 100644
--- a/lab-data/linux-kernel/modules/nfsroot/root/debugging/Makefile
+++ b/lab-data/linux-kernel/modules/nfsroot/root/debugging/Makefile
@@ -1,7 +1,7 @@
ifneq ($(KERNELRELEASE),)
obj-m := drvbroken.o
else
-KDIR := $(HOME)/felabs-kernel/src/linux
+KDIR := $(HOME)/linux-kernel-labs/src/linux
all:
$(MAKE) -C $(KDIR) M=$$PWD
endif
diff --git a/lab-data/linux-kernel/modules/nfsroot/root/hello/Makefile b/lab-data/linux-kernel/modules/nfsroot/root/hello/Makefile
index f5ef3e3..4bdb4b6 100644
--- a/lab-data/linux-kernel/modules/nfsroot/root/hello/Makefile
+++ b/lab-data/linux-kernel/modules/nfsroot/root/hello/Makefile
@@ -1,7 +1,7 @@
ifneq ($(KERNELRELEASE),)
obj-m := hello_version.o
else
-KDIR := $(HOME)/felabs-kernel/src/linux
+KDIR := $(HOME)/linux-kernel-labs/src/linux
all:
$(MAKE) -C $(KDIR) M=$$PWD
endif
diff --git a/lab-data/linux-kernel/modules/nfsroot/root/nunchuk/Makefile b/lab-data/linux-kernel/modules/nfsroot/root/nunchuk/Makefile
index b352953..72d2b83 100644
--- a/lab-data/linux-kernel/modules/nfsroot/root/nunchuk/Makefile
+++ b/lab-data/linux-kernel/modules/nfsroot/root/nunchuk/Makefile
@@ -1,7 +1,7 @@
ifneq ($(KERNELRELEASE),)
obj-m := nunchuk.o
else
-KDIR := $(HOME)/felabs-kernel/src/linux
+KDIR := $(HOME)/linux-kernel-labs/src/linux
all:
$(MAKE) -C $(KDIR) M=$$PWD
endif
diff --git a/lab-data/linux-kernel/modules/nfsroot/root/serial/Makefile b/lab-data/linux-kernel/modules/nfsroot/root/serial/Makefile
index 4cacc1e..948956c 100644
--- a/lab-data/linux-kernel/modules/nfsroot/root/serial/Makefile
+++ b/lab-data/linux-kernel/modules/nfsroot/root/serial/Makefile
@@ -1,7 +1,7 @@
ifneq ($(KERNELRELEASE),)
obj-m := feserial.o
else
-KDIR := $(HOME)/felabs-kernel/src/linux
+KDIR := $(HOME)/linux-kernel-labs/src/linux
all:
$(MAKE) -C $(KDIR) M=$$PWD
endif
diff --git a/labs/android-adb/android-adb.tex b/labs/android-adb/android-adb.tex
index 24d28dd..4569bbc 100644
--- a/labs/android-adb/android-adb.tex
+++ b/labs/android-adb/android-adb.tex
@@ -10,7 +10,7 @@ After this lab, you will be able to use ADB to:
\section{Setup}
-Stay in the \code{$HOME/felabs-android/source} directory.
+Stay in the \code{$HOME/android-labs/source} directory.
\section{Get ADB}
diff --git a/labs/android-application/android-application.tex b/labs/android-application/android-application.tex
index 934cefd..acdf7b2 100644
--- a/labs/android-application/android-application.tex
+++ b/labs/android-application/android-application.tex
@@ -9,7 +9,7 @@ After this lab, you will be able to:
\section{Write the application}
-Go to the \code{$HOME/felabs-android/app} directory.
+Go to the \code{$HOME/android-labs/app} directory.
You will find the basics for the \code{MissileControl} app. This app is incomplete,
parts of some activities are missing. However the UI part is
diff --git a/labs/android-boot/android-boot.tex b/labs/android-boot/android-boot.tex
index 25df62b..a8164af 100644
--- a/labs/android-boot/android-boot.tex
+++ b/labs/android-boot/android-boot.tex
@@ -9,7 +9,7 @@ After this lab, you will be able to:
\section{Setup}
-Go to the \code{$HOME/felabs-android/} directory.
+Go to the \code{$HOME/android-labs/} directory.
\section{Compile a kernel for the Android emulator}
@@ -35,7 +35,7 @@ Now that we have kernel sources, we now need a toolchain to compile
the kernel. Fortunately, Android provides one. First, add the
toolchain from the previous lab to your \code{PATH}.
-\code{PATH=$HOME/felabs-android/source/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/bin:$PATH}
+\code{PATH=$HOME/android-labs/source/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/bin:$PATH}
Now, configure the kernel for the target platform
@@ -55,7 +55,7 @@ have to restore the environment that you had after building Android
from sources. This is needed every time you reboot your workstation,
and every time you work with a new terminal.
-Go back to \code{$HOME/felabs-android/source}.
+Go back to \code{$HOME/android-labs/source}.
All you need to do is source the environment and run the \code{lunch}
command to specify which product you're working with
@@ -74,7 +74,7 @@ To run the emulator with your own kernel, you can use the
\code{-kernel} option:
\begin{verbatim}
-emulator -kernel $HOME/felabs-android/kernel/arch/arm/boot/zImage
+emulator -kernel $HOME/android-labs/kernel/arch/arm/boot/zImage
\end{verbatim}
Once again, check the kernel version in the Android settings. Make
@@ -82,7 +82,7 @@ sure that the kernel was built today.
\section{Generate a patchset from the Android Kernel}
-Go back to the \code{$HOME/felabs-android/kernel} directory.
+Go back to the \code{$HOME/android-labs/kernel} directory.
To compare the Android kernel sources with the official kernel ones,
we need to fetch the latter sources too, allowing us to see which
diff --git a/labs/android-first-compilation/android-first-compilation.tex b/labs/android-first-compilation/android-first-compilation.tex
index 1e3c0d5..2315c83 100644
--- a/labs/android-first-compilation/android-first-compilation.tex
+++ b/labs/android-first-compilation/android-first-compilation.tex
@@ -52,7 +52,7 @@ export CCACHE_DIR=/opt/ccache
\end{verbatim}
or, depending on your setup,
\begin{verbatim}
-export CCACHE_DIR=$HOME/felabs-android/ccache
+export CCACHE_DIR=$HOME/android-labs/ccache
\end{verbatim}
And that's it!
@@ -108,7 +108,7 @@ Now, look at the \code{PATH} environment variable again.
You can see that it contains:
\begin{itemize}
\item
- \code{$HOME/felabs-android/source/out/host/linux-x86/bin/}.
+ \code{$HOME/android-labs/source/out/host/linux-x86/bin/}.
That's where new utilities have just been compiled.
\item Prebuilt executables, in particular the ARM cross-compiling
toolchain, which was already present in the repositories fetched by
diff --git a/labs/android-jni-library/android-jni-library.tex b/labs/android-jni-library/android-jni-library.tex
index 1c1c833..3801cb6 100644
--- a/labs/android-jni-library/android-jni-library.tex
+++ b/labs/android-jni-library/android-jni-library.tex
@@ -12,7 +12,7 @@ After this lab, you will be able to
The code should be pretty close to the one you wrote in the native
application lab, so you will find a skeleton of the folder to
integrate into your product definition in the
-\code{$HOME/felabs-android/jni} directory. Copy the \code{frameworks}
+\code{$HOME/android-labs/jni} directory. Copy the \code{frameworks}
folder you will find there into your device folder.
You will mostly have to modify function prototypes from your previous
@@ -42,7 +42,7 @@ We should now have a system with the files
\code{/system/lib/libusb.so}.
Test what you did so far by using the \code{TestJNI.apk} application
-you'll find in the \code{felabs-android} directory.
+you'll find in the \code{android-labs} directory.
Install it using adb, and run it.
diff --git a/labs/android-native-app/android-native-app.tex b/labs/android-native-app/android-native-app.tex
index af992b8..7f0098f 100644
--- a/labs/android-native-app/android-native-app.tex
+++ b/labs/android-native-app/android-native-app.tex
@@ -9,7 +9,7 @@ After this lab, you will be able to:
\section{Add the binary to the compiled image}
Copy the \code{bin} folder from the
-\code{$HOME/felabs-android/native-app} directory and put it into your
+\code{$HOME/android-labs/native-app} directory and put it into your
device folder.
diff --git a/labs/android-new-board/android-new-board.tex b/labs/android-new-board/android-new-board.tex
index 28bfaa9..b51e59e 100644
--- a/labs/android-new-board/android-new-board.tex
+++ b/labs/android-new-board/android-new-board.tex
@@ -11,7 +11,7 @@ After this lab, you will be able to:
\section{Download the source code}
Go to the directory holding the Android source code (either
-\code{/opt/android} or \code{$HOME/felabs-android/source}).
+\code{/opt/android} or \code{$HOME/android-labs/source}).
While still using AOSP, we will use the configuration done in
TI-flavored Android build named \emph{rowboat}. This should make most
@@ -103,7 +103,7 @@ Make sure we are using \code{ccache}:
\begin{verbatim}
export USE_CCACHE=1
-export CCACHE_DIR=$HOME/felabs-android/ccache
+export CCACHE_DIR=$HOME/android-labs/ccache
\end{verbatim}
or, depending on your setup,
\begin{verbatim}
diff --git a/labs/android-source-code/android-source-code.tex b/labs/android-source-code/android-source-code.tex
index a271ed0..75c0453 100644
--- a/labs/android-source-code/android-source-code.tex
+++ b/labs/android-source-code/android-source-code.tex
@@ -22,7 +22,7 @@ cd android
\end{verbatim}
If you don't have that much space available, go to the
-\code{$HOME/felabs-android/source} directory.
+\code{$HOME/android-labs/source} directory.
\section{Install needed packages}
@@ -133,5 +133,5 @@ them once again, you don't have to actually cache them.
Ask your trainer for a pre-filled ccache archive that we will use to
speed up a lot the compilation. Once you have retrieved the archive,
-extract it in either the \code{/opt/} or \code{$HOME/felabs-android/}
+extract it in either the \code{/opt/} or \code{$HOME/android-labs/}
directories.
diff --git a/labs/boottime-install/boottime-install.tex b/labs/boottime-install/boottime-install.tex
index ddc2579..471da9f 100644
--- a/labs/boottime-install/boottime-install.tex
+++ b/labs/boottime-install/boottime-install.tex
@@ -138,8 +138,8 @@ Type the below commands:
\begin{verbatim}
cd /opt
sudo chown -R $USER.$USER .
-wget http://free-electrons.com/doc/training/boot-time/felabs-boottime.tar.xz
-sudo tar xf felabs-boottime.tar.xz
+wget http://free-electrons.com/doc/training/boot-time/boot-time-labs.tar.xz
+sudo tar xf boot-time-labs.tar.xz
sudo chown -R $USER.$USER .
\end{verbatim}
diff --git a/labs/kernel-board-setup/kernel-board-setup.tex b/labs/kernel-board-setup/kernel-board-setup.tex
index caee5ba..00041c4 100644
--- a/labs/kernel-board-setup/kernel-board-setup.tex
+++ b/labs/kernel-board-setup/kernel-board-setup.tex
@@ -119,7 +119,7 @@ Some earlier versions do not support this.}
If you are doing these labs on your own (i.e. without participating to a Free Electrons
course), we ask you to install the U-Boot binary that we compiled and
-tested. See the \code{$HOME/felabs-linux-kernel/bootloader/beaglebone-black/README.txt}
+tested. See the \code{$HOME/linux-kernel-labs/bootloader/beaglebone-black/README.txt}
file for a simple way to do this.
To avoid trouble because of settings applied in previous practical labs,
diff --git a/labs/kernel-compiling-and-nfs-booting/host-vs-target.dia b/labs/kernel-compiling-and-nfs-booting/host-vs-target.dia
index 7194d1a..0772282 100644
--- a/labs/kernel-compiling-and-nfs-booting/host-vs-target.dia
+++ b/labs/kernel-compiling-and-nfs-booting/host-vs-target.dia
@@ -172,7 +172,7 @@ workstation#</dia:string>
<dia:attribute name="text">
<dia:composite type="text">
<dia:attribute name="string">
- <dia:string>#/home/<user>/felabs-linux-kernel/.../nfsroot/root/
+ <dia:string>#/home/<user>/linux-kernel-labs/.../nfsroot/root/
directory#</dia:string>
</dia:attribute>
<dia:attribute name="font">
diff --git a/labs/kernel-compiling-and-nfs-booting/kernel-compiling-and-nfs-booting.tex b/labs/kernel-compiling-and-nfs-booting/kernel-compiling-and-nfs-booting.tex
index c0e472b..1caae7d 100644
--- a/labs/kernel-compiling-and-nfs-booting/kernel-compiling-and-nfs-booting.tex
+++ b/labs/kernel-compiling-and-nfs-booting/kernel-compiling-and-nfs-booting.tex
@@ -38,7 +38,7 @@ accessed through the network by the target, using NFS.
\section{Setup}
-Go to the \code{$HOME/felabs-linux-kernel/src/linux} directory.
+Go to the \code{$HOME/linux-kernel-labs/src/linux} directory.
Install packages needed for configuring, compiling and booting
the kernel for your board:
@@ -116,7 +116,7 @@ of your board will be \code{192.168.0.100}:
\scriptsize
\begin{verbatim}
-/home/<user>/felabs-linux-kernel/modules/nfsroot 192.168.0.100(rw,no_root_squash,no_subtree_check)
+/home/<user>/linux-kernel-labs/modules/nfsroot 192.168.0.100(rw,no_root_squash,no_subtree_check)
\end{verbatim}
\normalsize
@@ -142,7 +142,7 @@ just one line, pay attention to the \code{O} character, like "OMAP", in
\begin{verbatim}
setenv bootargs root=/dev/nfs rw ip=192.168.0.100 console=ttyO0
- nfsroot=192.168.0.1:/home/<user>/felabs-linux-kernel/modules/nfsroot
+ nfsroot=192.168.0.1:/home/<user>/linux-kernel-labs/modules/nfsroot
saveenv
\end{verbatim}
diff --git a/labs/kernel-debugging/kernel-debugging.tex b/labs/kernel-debugging/kernel-debugging.tex
index 9b91814..c3f7758 100644
--- a/labs/kernel-debugging/kernel-debugging.tex
+++ b/labs/kernel-debugging/kernel-debugging.tex
@@ -61,7 +61,7 @@ that have been transmitted by your driver.
\subsection{Setup}
-Go to the \code{~/felabs-linux-kernel/modules/nfsroot/root/debugging/} directory.
+Go to the \code{~/linux-kernel-labs/modules/nfsroot/root/debugging/} directory.
Make sure your kernel is built with the following options:
@@ -101,7 +101,7 @@ If the function source code is not enough, then you can look at the
disassembled version of the function, either using:
\begin{verbatim}
-cd ~/felabs-linux-kernel/src/linux/
+cd ~/linux-kernel-labs/src/linux/
arm-linux-gnueabi-objdump -S vmlinux > vmlinux.disasm
\end{verbatim}
diff --git a/labs/kernel-git/kernel-git.tex b/labs/kernel-git/kernel-git.tex
index bd8c263..209d1d0 100644
--- a/labs/kernel-git/kernel-git.tex
+++ b/labs/kernel-git/kernel-git.tex
@@ -12,7 +12,7 @@ After this lab, you will be able to:
\section{Setup}
-Go to your kernel source tree in \code{~/felabs-linux-kernel/src/linux}
+Go to your kernel source tree in \code{~/linux-kernel-labs/src/linux}
\section{Exploring the history}
diff --git a/labs/kernel-i2c-communication/kernel-i2c-communication.tex b/labs/kernel-i2c-communication/kernel-i2c-communication.tex
index d781470..a9daadf 100644
--- a/labs/kernel-i2c-communication/kernel-i2c-communication.tex
+++ b/labs/kernel-i2c-communication/kernel-i2c-communication.tex
@@ -10,9 +10,9 @@ After this lab, you will be able to:
\section{Setup}
-Stay in the \code{~/felabs-linux-kernel/src/linux} directory for kernel and DTB
+Stay in the \code{~/linux-kernel-labs/src/linux} directory for kernel and DTB
compiling (stay in the \code{nunchuk} branch), and in
-\code{~/felabs-linux-kernel/modules/nfsroot/root/nunchuk} for module compiling
+\code{~/linux-kernel-labs/modules/nfsroot/root/nunchuk} for module compiling
(use two different terminals).
\section{Find pin muxing configuration information for i2c1}
diff --git a/labs/kernel-i2c-device-model/kernel-i2c-device-model.tex b/labs/kernel-i2c-device-model/kernel-i2c-device-model.tex
index 6f574cb..d1b1348 100644
--- a/labs/kernel-i2c-device-model/kernel-i2c-device-model.tex
+++ b/labs/kernel-i2c-device-model/kernel-i2c-device-model.tex
@@ -16,7 +16,7 @@ device/driver match.
\section{Setup}
-Go to the \code{~/felabs-linux-kernel/src/linux} directory. Check out the
+Go to the \code{~/linux-kernel-labs/src/linux} directory. Check out the
\code{3.13.y} branch.
Now create a new \code{nunchuk} branch starting from the
@@ -134,7 +134,7 @@ It is now time to start writing the first building blocks of the I2C
driver for our nunchuk.
In a new terminal, go to
-\code{~/felabs-linux-kernel/modules/nfsroot/root/nunchuk/}. This directory
+\code{~/linux-kernel-labs/modules/nfsroot/root/nunchuk/}. This directory
contains a Makefile and an almost empty \code{nunchuk.c} file.
Now, you can compile your out-of-tree module by running \code{make}. As
diff --git a/labs/kernel-module-simple/kernel-module-simple.tex b/labs/kernel-module-simple/kernel-module-simple.tex
index 66e3c99..485645f 100644
--- a/labs/kernel-module-simple/kernel-module-simple.tex
+++ b/labs/kernel-module-simple/kernel-module-simple.tex
@@ -12,7 +12,7 @@ After this lab, you will be able to:
\section{Setup}
-Go to the \code{~/felabs-linux-kernel/modules/nfsroot/root/hello} directory.
+Go to the \code{~/linux-kernel-labs/modules/nfsroot/root/hello} directory.
Boot your board if needed.
\section{Writing a module}
@@ -87,7 +87,7 @@ Run the \code{scripts/checkpatch.pl -h} command in the kernel sources,
to find which options are available. Now, run:
\begin{verbatim}
-~/felabs-linux-kernel/src/linux/scripts/checkpatch.pl --file --no-tree hello_version.c
+~/linux-kernel-labs/src/linux/scripts/checkpatch.pl --file --no-tree hello_version.c
\end{verbatim}
See how many violations are reported on your code. If there are
@@ -138,7 +138,7 @@ Then, commit your changes in the current branch (try to choose an
appropriate commit message):
\begin{verbatim}
-cd ~/felabs-linux-kernel/src/linux
+cd ~/linux-kernel-labs/src/linux
git add -A
git commit -as
\end{verbatim}
diff --git a/labs/kernel-serial-iomem/kernel-serial-iomem.tex b/labs/kernel-serial-iomem/kernel-serial-iomem.tex
index 4c97386..9681d12 100644
--- a/labs/kernel-serial-iomem/kernel-serial-iomem.tex
+++ b/labs/kernel-serial-iomem/kernel-serial-iomem.tex
@@ -76,7 +76,7 @@ Rebuild and update your DTB.
\section{Operate a platform device driver}
-Go to the \code{~/felabs-linux-kernel/modules/nfsroot/root/serial/} directory.
+Go to the \code{~/linux-kernel-labs/modules/nfsroot/root/serial/} directory.
You will find a \code{feserial.c} file which already provides a platform
driver skeleton.
diff --git a/labs/kernel-serial-output/kernel-serial-output.tex b/labs/kernel-serial-output/kernel-serial-output.tex
index 21175ed..bab9162 100644
--- a/labs/kernel-serial-output/kernel-serial-output.tex
+++ b/labs/kernel-serial-output/kernel-serial-output.tex
@@ -108,7 +108,7 @@ weird assumptions about the {\em misc} framework.}
changes. Commit these if they correspond to useful changes (these
should be your Device Tree edits).
\item Apply the new patch using the following command:
- \code{git am ~/felabs-linux-kernel/src/patches/0001-char-misc*.patch}
+ \code{git am ~/linux-kernel-labs/src/patches/0001-char-misc*.patch}
\item Rebuild and update your kernel image and reboot.
\end{itemize}
diff --git a/labs/kernel-sources-download/kernel-sources-download.tex b/labs/kernel-sources-download/kernel-sources-download.tex
index 93bf14e..251a277 100644
--- a/labs/kernel-sources-download/kernel-sources-download.tex
+++ b/labs/kernel-sources-download/kernel-sources-download.tex
@@ -3,7 +3,7 @@ mainline Linux kernel source tree}
\section{Setup}
-Go to the \code{$HOME/felabs-linux-kernel/src} directory.
+Go to the \code{$HOME/linux-kernel-labs/src} directory.
\section{Installing git packages}
@@ -89,7 +89,7 @@ tree, and fetch only the commits which are specific to that remote tree.
{\footnotesize
\begin{verbatim}
-cd ~/felabs-linux-kernel/src/linux/
+cd ~/linux-kernel-labs/src/linux/
git remote add stable git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
git fetch stable
\end{verbatim}
diff --git a/labs/kernel-sources-exploring/kernel-sources-exploring.tex b/labs/kernel-sources-exploring/kernel-sources-exploring.tex
index 0c83e8c..0bbb998 100644
--- a/labs/kernel-sources-exploring/kernel-sources-exploring.tex
+++ b/labs/kernel-sources-exploring/kernel-sources-exploring.tex
@@ -22,7 +22,7 @@ running.
First, let's get the list of branches on our \code{stable} remote tree:
\begin{verbatim}
-cd ~/felabs-linux-kernel/src/linux
+cd ~/linux-kernel-labs/src/linux
git branch -a
\end{verbatim}
diff --git a/labs/setup/setup.tex b/labs/setup/setup.tex
index d48bac2..0e0698b 100644
--- a/labs/setup/setup.tex
+++ b/labs/setup/setup.tex
@@ -10,9 +10,9 @@ and more). Download and extract its tarball from a terminal:
{\small
{\tt
cd \\
-wget \sessionurl/felabs-\longname.tar.xz \\
-sudo tar Jvxf felabs-\longname.tar.xz \\
-sudo chown -R <user>.<user> felabs-\longname \\
+wget \sessionurl/\longname-labs.tar.xz \\
+sudo tar Jvxf \longname-labs.tar.xz \\
+sudo chown -R <user>.<user> \longname-labs \\
}
}
@@ -22,7 +22,7 @@ an exception. For all the other archives that you will handle during
the practical labs, you will never need \code{root} permissions to
extract them. If there is another exception, we will let you know.
-Lab data are now available in an {\tt felabs-\longname} directory in
+Lab data are now available in an {\tt \longname-labs} directory in
your home directory. For each lab there is a directory containing
various data. This directory will also be used as working space for
each lab, so that the files that you produce during each lab are kept
diff --git a/labs/sysdev-application-debugging/sysdev-application-debugging.tex b/labs/sysdev-application-debugging/sysdev-application-debugging.tex
index eb2c505..82c5081 100644
--- a/labs/sysdev-application-debugging/sysdev-application-debugging.tex
+++ b/labs/sysdev-application-debugging/sysdev-application-debugging.tex
@@ -6,7 +6,7 @@
\section{Setup}
-Go to the \code{$HOME/felabs-embedded-linux/debugging} directory.
+Go to the \code{$HOME/embedded-linux-labs/debugging} directory.
\section{Debugging setup}
diff --git a/labs/sysdev-application-development/sysdev-application-development.tex b/labs/sysdev-application-development/sysdev-application-development.tex
index 63f7ded..ea13612 100644
--- a/labs/sysdev-application-development/sysdev-application-development.tex
+++ b/labs/sysdev-application-development/sysdev-application-development.tex
@@ -3,7 +3,7 @@
\section{Setup}
-Go to the \code{$HOME/felabs-embedded-linux/appdev} directory.
+Go to the \code{$HOME/embedded-linux-labs/appdev} directory.
\section{Compile your own application}
@@ -25,7 +25,7 @@ Let's add this directory to our PATH:
\footnotesize
\begin{verbatim}
-export PATH=$HOME/felabs-embedded-linux/buildroot/buildroot-XXXX.YY/output/host/usr/bin:$PATH
+export PATH=$HOME/embedded-linux-labs/buildroot/buildroot-XXXX.YY/output/host/usr/bin:$PATH
\end{verbatim}
\normalsize
diff --git a/labs/sysdev-block-filesystems/sysdev-block-filesystems.tex b/labs/sysdev-block-filesystems/sysdev-block-filesystems.tex
index bd2f523..64dc35d 100644
--- a/labs/sysdev-block-filesystems/sysdev-block-filesystems.tex
+++ b/labs/sysdev-block-filesystems/sysdev-block-filesystems.tex
@@ -19,7 +19,7 @@ be booted with this MMC card, without using NFS anymore.
\section{Setup}
Throughout this lab, we will continue to use the root filesystem we
-have created in the \code{$HOME/felabs-embedded-linux/tinysystem/nfsroot}
+have created in the \code{$HOME/embedded-linux-labs/tinysystem/nfsroot}
directory, which we will progressively adapt to use block filesystems.
\section{Filesystem support in the kernel}
diff --git a/labs/sysdev-buildroot/sysdev-buildroot.tex b/labs/sysdev-buildroot/sysdev-buildroot.tex
index d7c2622..f8ab9d1 100644
--- a/labs/sysdev-buildroot/sysdev-buildroot.tex
+++ b/labs/sysdev-buildroot/sysdev-buildroot.tex
@@ -5,7 +5,7 @@
\section{Setup}
-Go to the \code{$HOME/felabs-embedded-linux/buildroot/} directory,
+Go to the \code{$HOME/embedded-linux-labs/buildroot/} directory,
which already contains some data needed for this lab.
\section{Get Buildroot and explore the source code}
@@ -165,7 +165,7 @@ explore its contents:
\section{Run the generated system}
-Go back to the \code{$HOME/felabs-embedded-linux/buildroot/} directory. Create
+Go back to the \code{$HOME/embedded-linux-labs/buildroot/} directory. Create
a new directory \code{system} that is going to hold our system,
exported over NFS. Go into this directory, and untar the rootfs using:
diff --git a/labs/sysdev-flash-filesystems/sysdev-flash-filesystems.tex b/labs/sysdev-flash-filesystems/sysdev-flash-filesystems.tex
index ca38994..059bfcd 100644
--- a/labs/sysdev-flash-filesystems/sysdev-flash-filesystems.tex
+++ b/labs/sysdev-flash-filesystems/sysdev-flash-filesystems.tex
@@ -8,7 +8,7 @@ After this lab, you will be able to:
\section{Setup}
-Stay in \code{$HOME/felabs-embedded-linux/tinysystem}. Install the
+Stay in \code{$HOME/embedded-linux-labs/tinysystem}. Install the
\code{mtd-utils} package, which will be useful to create JFFS2
filesystem images.
diff --git a/labs/sysdev-kernel-cross-compiling/sysdev-kernel-cross-compiling.tex b/labs/sysdev-kernel-cross-compiling/sysdev-kernel-cross-compiling.tex
index ed66a93..427c401 100644
--- a/labs/sysdev-kernel-cross-compiling/sysdev-kernel-cross-compiling.tex
+++ b/labs/sysdev-kernel-cross-compiling/sysdev-kernel-cross-compiling.tex
@@ -12,7 +12,7 @@ After this lab, you will be able to:
\section{Setup}
-Go to the \code{$HOME/felabs-embedded-linux/kernel} directory.
+Go to the \code{$HOME/embedded-linux-labs/kernel} directory.
Install the package \code{libqt4-dev} which is needed for the
\code{xconfig} kernel configuration interface.
diff --git a/labs/sysdev-kernel-fetch-and-patch/sysdev-kernel-fetch-and-patch.tex b/labs/sysdev-kernel-fetch-and-patch/sysdev-kernel-fetch-and-patch.tex
index a0f5da7..94d5e5f 100644
--- a/labs/sysdev-kernel-fetch-and-patch/sysdev-kernel-fetch-and-patch.tex
+++ b/labs/sysdev-kernel-fetch-and-patch/sysdev-kernel-fetch-and-patch.tex
@@ -9,7 +9,7 @@ After this lab, you will be able to:
\section{Setup}
-Create the \code{$HOME/felabs-embedded-linux/kernel} directory and go into it.
+Create the \code{$HOME/embedded-linux-labs/kernel} directory and go into it.
\section{Get the sources}
diff --git a/labs/sysdev-real-time/sysdev-real-time.tex b/labs/sysdev-real-time/sysdev-real-time.tex
index 3d6aebb..6ce89ee 100644
--- a/labs/sysdev-real-time/sysdev-real-time.tex
+++ b/labs/sysdev-real-time/sysdev-real-time.tex
@@ -14,7 +14,7 @@ POSIX real-time API, and against Xenomai's POSIX skin.
\section{Setup}
-Go to the \code{$HOME/felabs-embedded-linux/realtime/rttest} directory.
+Go to the \code{$HOME/embedded-linux-labs/realtime/rttest} directory.
If you are using a 64 bit installation of Ubuntu, install support for
executables built with a 32 bit C library, if you didn't do it
@@ -114,7 +114,7 @@ Let's configure our \code{PATH} to use this toolchain:
\scriptsize
\begin{verbatim}
-export PATH=$HOME/felabs-embedded-linux/realtime/rttest/buildroot-2014.05/output/host/usr/bin:$PATH
+export PATH=$HOME/embedded-linux-labs/realtime/rttest/buildroot-2014.05/output/host/usr/bin:$PATH
\end{verbatim}
\normalsize
@@ -176,10 +176,10 @@ patch only apply on this release. Then apply the patch
\code{ipipe-arm-3.14.patch.xz} provided in data:
\begin{verbatim}
-cd $HOME/felabs-embedded-linux/realtime/rttest
-tar xf $HOME/felabs-embedded-linux/kernel/linux-3.13.tar.xz
+cd $HOME/embedded-linux-labs/realtime/rttest
+tar xf $HOME/embedded-linux-labs/kernel/linux-3.13.tar.xz
cd linux-3.13/
-xzcat $HOME/felabs-embedded-linux/kernel/patch-3.14.xz | patch -p1
+xzcat $HOME/embedded-linux-labs/kernel/patch-3.14.xz | patch -p1
xzcat ../data/ipipe-arm-3.14.patch.xz | patch -p1
cd ..
mv linux-3.13/ linux-3.14-ipipe
@@ -189,7 +189,7 @@ Now, download Xenomai's master, in order to apply the extra patches
needed for the interaction with the Xenomai user-space components.
\begin{verbatim}
-cd $HOME/felabs-embedded-linux/realtime/rttest
+cd $HOME/embedded-linux-labs/realtime/rttest
git clone git://git.xenomai.org/xenomai-2.6.git xenomai
cd xenomai
git checkout 589882956280
@@ -197,7 +197,7 @@ git checkout 589882956280
Now, prepare our kernel for Xenomai compilation:
\begin{verbatim}
-cd $HOME/felabs-embedded-linux/realtime/rttest
+cd $HOME/embedded-linux-labs/realtime/rttest
./xenomai/scripts/prepare-kernel.sh --arch=arm --linux=linux-3.14-ipipe/
\end{verbatim}
@@ -217,7 +217,7 @@ source directory, and force Buildroot to build the host variant of
{\em pkg-config}:
\begin{verbatim}
-cd $HOME/felabs-embedded-linux/realtime/rttest/buildroot-2014.05/
+cd $HOME/embedded-linux-labs/realtime/rttest/buildroot-2014.05/
make host-pkgconf
\end{verbatim}
@@ -226,8 +226,8 @@ compile \code{rttest} for the Xenomai POSIX skin:
\scriptsize
\begin{verbatim}
-cd $HOME/felabs-embedded-linux/realtime/rttest/nfsroot/root
-export PATH=$HOME/felabs-embedded-linux/realtime/rttest/buildroot-2014.05/output/host/usr/bin:$PATH
+cd $HOME/embedded-linux-labs/realtime/rttest/nfsroot/root
+export PATH=$HOME/embedded-linux-labs/realtime/rttest/buildroot-2014.05/output/host/usr/bin:$PATH
arm-none-linux-gnueabi-gcc -o rttest rttest.c \
$(pkg-config --libs --cflags libxenomai_posix)
\end{verbatim}
diff --git a/labs/sysdev-thirdparty/sysdev-thirdparty.tex b/labs/sysdev-thirdparty/sysdev-thirdparty.tex
index ff14b46..01c3db0 100644
--- a/labs/sysdev-thirdparty/sysdev-thirdparty.tex
+++ b/labs/sysdev-thirdparty/sysdev-thirdparty.tex
@@ -87,7 +87,7 @@ To sum up, the {\em staging} space will contain everything that's
needed for compilation, while the {\em target} space will contain only
what's needed for execution.
-So, in \code{$HOME/felabs-embedded-linux/thirdparty}, create two
+So, in \code{$HOME/embedded-linux-labs/thirdparty}, create two
directories: \code{staging} and \code{target}.
For the target, we need a basic system with BusyBox, device nodes and
@@ -96,7 +96,7 @@ initialization scripts. We will re-use the system built in the {\em A
directory:
\begin{verbatim}
-sudo cp -a $HOME/felabs-embedded-linux/tinysystem/nfsroot/* target/
+sudo cp -a $HOME/embedded-linux-labs/tinysystem/nfsroot/* target/
\end{verbatim}
The copy must be done as \code{root}, because the root filesystem of
@@ -116,7 +116,7 @@ prompt.
\code{alsa-lib} is a library supposed to handle the interaction with
the ALSA subsystem. It is available at
\url{http://alsa-project.org}. Download version 1.0.28, and extract it
-in \code{$HOME/felabs-embedded-linux/thirdparty/}.
+in \code{$HOME/embedded-linux-labs/thirdparty/}.
By looking at the \code{configure} script, we see that this configure
script has been generated by \code{autoconf} (the header contain a
@@ -294,14 +294,14 @@ application or library will be installed on your host while building
the root filesystem.
For example, libasound will be installed in
-\code{$HOME/felabs-embedded-linux/thirdparty/target/usr/lib/} because this is
+\code{$HOME/embedded-linux-labs/thirdparty/target/usr/lib/} because this is
the directory where we are building the root filesystem, but once our
target system will be running, it will see libasound in
\code{/usr/lib}.
The prefix corresponds to the path in the target system and {\bf
never} on the host. So, one should {\bf never} pass a prefix like
-\code{$HOME/felabs-embedded-linux/thirdparty/target/usr}, otherwise at
+\code{$HOME/embedded-linux-labs/thirdparty/target/usr}, otherwise at
runtime, the application or library may look for files inside this
directory on the target system, which obviously doesn't exist! By
default, most build systems will install the application or library in
@@ -313,7 +313,7 @@ We now only have the installation process left to do.
First, let's make the installation in the {\em staging} space:
\begin{verbatim}
-make DESTDIR=$HOME/felabs-embedded-linux/thirdparty/staging install
+make DESTDIR=$HOME/embedded-linux-labs/thirdparty/staging install
\end{verbatim}
Now look at what has been installed by alsa-lib:
@@ -395,7 +395,7 @@ can be found: there are not in the default directory
Let's use it:
\begin{verbatim}
-CPPFLAGS=-I$HOME/felabs-embedded-linux/thirdparty/staging/usr/include \
+CPPFLAGS=-I$HOME/embedded-linux-labs/thirdparty/staging/usr/include \
CC=arm-linux-gcc \
./configure --host=arm-linux --prefix=/usr
\end{verbatim}
@@ -426,8 +426,8 @@ help text of the configure script:
Let's use this \code{LDFLAGS} variable:
\begin{verbatim}
-LDFLAGS=-L$HOME/felabs-embedded-linux/thirdparty/staging/usr/lib \
-CPPFLAGS=-I$HOME/felabs-embedded-linux/thirdparty/staging/usr/include \
+LDFLAGS=-L$HOME/embedded-linux-labs/thirdparty/staging/usr/lib \
+CPPFLAGS=-I$HOME/embedded-linux-labs/thirdparty/staging/usr/include \
CC=arm-linux-gcc \
./configure --host=arm-linux
\end{verbatim}
@@ -436,8 +436,8 @@ Let's also specify the prefix, so that the library is compiled to be
installed in \code{/usr} and not \code{/usr/local}:
\begin{verbatim}
-LDFLAGS=-L$HOME/felabs-embedded-linux/thirdparty/staging/usr/lib \
-CPPFLAGS=-I$HOME/felabs-embedded-linux/thirdparty/staging/usr/include \
+LDFLAGS=-L$HOME/embedded-linux-labs/thirdparty/staging/usr/lib \
+CPPFLAGS=-I$HOME/embedded-linux-labs/thirdparty/staging/usr/include \
CC=arm-linux-gcc \
./configure --host=arm-linux --prefix=/usr
\end{verbatim}
@@ -454,8 +454,8 @@ just like we built alsa-lib. We will also need to disable the xmlto
support that generates the documentation.
\begin{verbatim}
-LDFLAGS=-L$HOME/felabs-embedded-linux/thirdparty/staging/usr/lib \
-CPPFLAGS=-I$HOME/felabs-embedded-linux/thirdparty/staging/usr/include \
+LDFLAGS=-L$HOME/embedded-linux-labs/thirdparty/staging/usr/lib \
+CPPFLAGS=-I$HOME/embedded-linux-labs/thirdparty/staging/usr/include \
CC=arm-linux-gcc \
./configure --host=arm-linux --prefix=/usr \
--disable-alsamixer --disable-xmlto
@@ -548,7 +548,7 @@ So, we have:
Now, let's make the installation in the {\em staging} space:
\begin{verbatim}
-make DESTDIR=$HOME/felabs-embedded-linux/thirdparty/staging/ install
+make DESTDIR=$HOME/embedded-linux-labs/thirdparty/staging/ install
\end{verbatim}
Then, let's install only the necessary files in the {\em target}
@@ -596,7 +596,7 @@ Installation to the {\em staging} space can be done using the
classical \code{DESTDIR} mechanism:
\begin{verbatim}
-make DESTDIR=$HOME/felabs-embedded-linux/thirdparty/staging/ install
+make DESTDIR=$HOME/embedded-linux-labs/thirdparty/staging/ install
\end{verbatim}
And finally, install manually the only needed files at runtime in the
@@ -637,8 +637,8 @@ Use those:
\begin{verbatim}
CC=arm-linux-gcc ./configure --host=arm-linux --prefix=/usr \
- --with-ogg-includes=$HOME/felabs-embedded-linux/thirdparty/staging/usr/include \
- --with-ogg-libraries=$HOME/felabs-embedded-linux/thirdparty/staging/usr/lib
+ --with-ogg-includes=$HOME/embedded-linux-labs/thirdparty/staging/usr/include \
+ --with-ogg-libraries=$HOME/embedded-linux-labs/thirdparty/staging/usr/lib
\end{verbatim}
Then, compile the library:
@@ -650,7 +650,7 @@ make
Install it in the {\em staging} space:
\begin{verbatim}
-make DESTDIR=$HOME/felabs-embedded-linux/thirdparty/staging/ install
+make DESTDIR=$HOME/embedded-linux-labs/thirdparty/staging/ install
\end{verbatim}
And install only the required files in the {\em target} space:
@@ -674,8 +674,8 @@ Configuring {\em libao} is once again fairly easy, and similar to
every sane autotools based build system:
\begin{verbatim}
-LDFLAGS=-L$HOME/felabs-embedded-linux/thirdparty/staging/usr/lib \
-CPPFLAGS=-I$HOME/felabs-embedded-linux/thirdparty/staging/usr/include \
+LDFLAGS=-L$HOME/embedded-linux-labs/thirdparty/staging/usr/lib \
+CPPFLAGS=-I$HOME/embedded-linux-labs/thirdparty/staging/usr/include \
CC=arm-linux-gcc ./configure --host=arm-linux \
--prefix=/usr
\end{verbatim}
@@ -690,7 +690,7 @@ Installation to the {\em staging} space can be done using the
classical \code{DESTDIR} mechanism:
\begin{verbatim}
-make DESTDIR=$HOME/felabs-embedded-linux/thirdparty/staging/ install
+make DESTDIR=$HOME/embedded-linux-labs/thirdparty/staging/ install
\end{verbatim}
And finally, install manually the only needed files at runtime in the
@@ -735,8 +735,8 @@ configuration options:
So, let's begin with our usual configure line:
\begin{verbatim}
-LDFLAGS=-L$HOME/felabs-embedded-linux/thirdparty/staging/usr/lib \
-CPPFLAGS=-I$HOME/felabs-embedded-linux/thirdparty/staging/usr/include \
+LDFLAGS=-L$HOME/embedded-linux-labs/thirdparty/staging/usr/lib \
+CPPFLAGS=-I$HOME/embedded-linux-labs/thirdparty/staging/usr/include \
CC=arm-linux-gcc \
./configure --host=arm-linux --prefix=/usr
\end{verbatim}
@@ -795,7 +795,7 @@ explained in the manual page of \code{pkg-config}.
Moreover, the \code{.pc} files contain references to paths. For
example, in
-\code{$HOME/felabs-embedded-linux/thirdparty/staging/usr/lib/pkgconfig/ao.pc},
+\code{$HOME/embedded-linux-labs/thirdparty/staging/usr/lib/pkgconfig/ao.pc},
we can see:
\begin{verbatim}
@@ -818,10 +818,10 @@ environment variables:
\small
\begin{verbatim}
-LDFLAGS=-L$HOME/felabs-embedded-linux/thirdparty/staging/usr/lib \
-CPPFLAGS=-I$HOME/felabs-embedded-linux/thirdparty/staging/usr/include \
-PKG_CONFIG_PATH=$HOME/felabs-embedded-linux/thirdparty/staging/usr/lib/pkgconfig \
-PKG_CONFIG_SYSROOT_DIR=$HOME/felabs-embedded-linux/thirdparty/staging \
+LDFLAGS=-L$HOME/embedded-linux-labs/thirdparty/staging/usr/lib \
+CPPFLAGS=-I$HOME/embedded-linux-labs/thirdparty/staging/usr/include \
+PKG_CONFIG_PATH=$HOME/embedded-linux-labs/thirdparty/staging/usr/lib/pkgconfig \
+PKG_CONFIG_SYSROOT_DIR=$HOME/embedded-linux-labs/thirdparty/staging \
CC=arm-linux-gcc \
./configure --host=arm-linux --prefix=/usr
\end{verbatim}
@@ -842,7 +842,7 @@ It may also fail with the following cryptic message:
\begin{verbatim}
if arm-linux-gcc -DSYSCONFDIR=\"/usr/etc\" -DLOCALEDIR=\"/usr/share/locale\"
-DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include -I../include -I../intl
- -I/home/ubuntu/felabs-embedded-linux/thirdparty/staging/usr/include -O2 -Wall
+ -I/home/ubuntu/embedded-linux-labs/thirdparty/staging/usr/include -O2 -Wall
-ffast-math -fsigned-char -g -O2 -MT audio.o -MD -MP -MF ".deps/audio.Tpo"
-c -o audio.o audio.c; \
then mv -f ".deps/audio.Tpo" ".deps/audio.Po"; else rm -f ".deps/audio.Tpo"; exit 1; fi
@@ -853,9 +853,9 @@ In file included from /usr/include/stdio.h:28:0,
^
compilation terminated.
make[2]: *** [audio.o] Error 1
-make[2]: Leaving directory `/home/ubuntu/felabs-embedded-linux/thirdparty/vorbis-tools-1.4.0/ogg123'
+make[2]: Leaving directory `/home/ubuntu/embedded-linux-labs/thirdparty/vorbis-tools-1.4.0/ogg123'
make[1]: *** [all-recursive] Error 1
-make[1]: Leaving directory `/home/ubuntu/felabs-embedded-linux/thirdparty/vorbis-tools-1.4.0'
+make[1]: Leaving directory `/home/ubuntu/embedded-linux-labs/thirdparty/vorbis-tools-1.4.0'
make: *** [all] Error 2
\end{verbatim}
\normalsize
@@ -883,10 +883,10 @@ flags.
Add this to the configure command line to get
\begin{verbatim}
-LDFLAGS=-L$HOME/felabs-embedded-linux/thirdparty/staging/usr/lib \
-CPPFLAGS=-I$HOME/felabs-embedded-linux/thirdparty/staging/usr/include \
-PKG_CONFIG_PATH=$HOME/felabs-embedded-linux/thirdparty/staging/usr/lib/pkgconfig \
-PKG_CONFIG_SYSROOT_DIR=$HOME/felabs-embedded-linux/thirdparty/staging \
+LDFLAGS=-L$HOME/embedded-linux-labs/thirdparty/staging/usr/lib \
+CPPFLAGS=-I$HOME/embedded-linux-labs/thirdparty/staging/usr/include \
+PKG_CONFIG_PATH=$HOME/embedded-linux-labs/thirdparty/staging/usr/lib/pkgconfig \
+PKG_CONFIG_SYSROOT_DIR=$HOME/embedded-linux-labs/thirdparty/staging \
LIBS=-lm \
CC=arm-linux-gcc \
./configure --host=arm-linux --prefix=/usr --without-curl
@@ -897,7 +897,7 @@ Finally, it builds!
Now, install the vorbis-tools to the {\em staging} space using:
\begin{verbatim}
-make DESTDIR=$HOME/felabs-embedded-linux/thirdparty/staging/ install
+make DESTDIR=$HOME/embedded-linux-labs/thirdparty/staging/ install
\end{verbatim}
And then install them in the {\em target} space:
diff --git a/labs/sysdev-tinysystem/host-vs-target.dia b/labs/sysdev-tinysystem/host-vs-target.dia
index 3e99cfa..e80696d 100644
--- a/labs/sysdev-tinysystem/host-vs-target.dia
+++ b/labs/sysdev-tinysystem/host-vs-target.dia
@@ -172,7 +172,7 @@ workstation#</dia:string>
<dia:attribute name="text">
<dia:composite type="text">
<dia:attribute name="string">
- <dia:string>#/home/<user>/felabs-embedded-linux/.../nfsroot/root/
+ <dia:string>#/home/<user>/embedded-linux-labs/.../nfsroot/root/
directory#</dia:string>
</dia:attribute>
<dia:attribute name="font">
diff --git a/labs/sysdev-tinysystem/sysdev-tinysystem.tex b/labs/sysdev-tinysystem/sysdev-tinysystem.tex
index 129575e..28be93e 100644
--- a/labs/sysdev-tinysystem/sysdev-tinysystem.tex
+++ b/labs/sysdev-tinysystem/sysdev-tinysystem.tex
@@ -35,12 +35,12 @@ target to test the impact of script or application updates.
\section{Setup}
-Go to the \code{$HOME/felabs-embedded-linux/tinysystem/} directory.
+Go to the \code{$HOME/embedded-linux-labs/tinysystem/} directory.
\section{Kernel configuration}
We will re-use the kernel sources from our previous lab, in
-\code{$HOME/felabs-embedded-linux/kernel/}.
+\code{$HOME/embedded-linux-labs/kernel/}.
In the kernel configuration built in the previous lab, verify that you
have all options needed for booting the system using a root filesystem
@@ -60,7 +60,7 @@ IP address of your board will be \code{192.168.0.100}:
\footnotesize
\begin{verbatim}
-/home/<user>/felabs-embedded-linux/tinysystem/nfsroot 192.168.0.100(rw,no_root_squash,no_subtree_check)
+/home/<user>/embedded-linux-labs/tinysystem/nfsroot 192.168.0.100(rw,no_root_squash,no_subtree_check)
\end{verbatim}
\normalsize
@@ -85,7 +85,7 @@ Use the following U-Boot command to do so, {\bf in just 1 line}
\begin{verbatim}
setenv bootargs console=ttyS0,115200 root=/dev/nfs ip=192.168.0.100:::::eth0
- nfsroot=192.168.0.1:/home/<user>/felabs-embedded-linux/tinysystem/nfsroot rw
+ nfsroot=192.168.0.1:/home/<user>/embedded-linux-labs/tinysystem/nfsroot rw
\end{verbatim}
Of course, you need to adapt the IP addresses to your exact network
diff --git a/labs/sysdev-toolchain/sysdev-toolchain.tex b/labs/sysdev-toolchain/sysdev-toolchain.tex
index 261f517..d9aa386 100644
--- a/labs/sysdev-toolchain/sysdev-toolchain.tex
+++ b/labs/sysdev-toolchain/sysdev-toolchain.tex
@@ -11,7 +11,7 @@ After this lab, you will be able to:
\section{Setup}
-Go to the \code{$HOME/felabs-embedded-linux/toolchain} directory.
+Go to the \code{$HOME/embedded-linux-labs/toolchain} directory.
\section{Install needed packages}
diff --git a/labs/sysdev-u-boot/sysdev-u-boot.tex b/labs/sysdev-u-boot/sysdev-u-boot.tex
index 49dc321..135db71 100644
--- a/labs/sysdev-u-boot/sysdev-u-boot.tex
+++ b/labs/sysdev-u-boot/sysdev-u-boot.tex
@@ -31,7 +31,7 @@ without having anything installed on it.
\section{Setup}
-Go to the \code{~/felabs-embedded-linux/bootloader} directory.
+Go to the \code{~/embedded-linux-labs/bootloader} directory.
If you are using a 64 bit installation of Ubuntu, install support for
executables built with a 32 bit C library:
diff --git a/labs/yocto-first-build/yocto-first-build.tex b/labs/yocto-first-build/yocto-first-build.tex
index 45ef8b0..66495c4 100644
--- a/labs/yocto-first-build/yocto-first-build.tex
+++ b/labs/yocto-first-build/yocto-first-build.tex
@@ -14,7 +14,7 @@ Before starting this lab, make sure your home directory is not encrypted. Yocto
cannot be used on top of an eCryptFS file system due to limitations on file name
lengths.
-Go to the \code{\$HOME/felabs-yocto/} directory.
+Go to the \code{\$HOME/yocto-labs/} directory.
Install the required packages:
\begin{verbatim}
More information about the training-materials-updates
mailing list