[BL training-materials-updates] Replace "apt-get" by "apt"
Michael Opdenacker
michael.opdenacker at bootlin.com
Thu Apr 12 17:32:50 CEST 2018
Repository : git://git.free-electrons.com/training-materials.git
On branch : master
Link : http://git.free-electrons.com/training-materials/commit/?id=0e4d1582f2e055acac598a73f0697a72bb277736
>---------------------------------------------------------------
commit 0e4d1582f2e055acac598a73f0697a72bb277736
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date: Thu Apr 12 17:32:50 2018 +0200
Replace "apt-get" by "apt"
- More friendly and simpler interface
Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com>
>---------------------------------------------------------------
0e4d1582f2e055acac598a73f0697a72bb277736
README | 6 +++---
lab-data/boot-time/setup/install-packages | 2 +-
lab-data/common/bootloader/beaglebone-black/README.txt | 2 +-
lab-data/get_packages | 14 +++++++-------
labs/android-new-board/android-new-board.tex | 2 +-
labs/android-source-code/android-source-code.tex | 10 +++++-----
labs/autotools-advanced/autotools-advanced.tex | 2 +-
labs/autotools-usage/autotools-usage.tex | 8 ++++----
labs/boottime-getting-started/boottime-getting-started.tex | 6 +++---
labs/boottime-init-scripts/boottime-init-scripts.tex | 2 +-
labs/boottime-install/boottime-install.tex | 4 ++--
labs/boottime-kernel/boottime-kernel.tex | 2 +-
labs/boottime-measuring/boottime-measuring.tex | 6 +++---
labs/buildroot-basic/buildroot-basic.tex | 4 ++--
labs/kernel-board-setup/kernel-board-setup.tex | 4 ++--
.../kernel-compiling-and-nfs-booting.tex | 4 ++--
labs/kernel-debugging/kernel-debugging.tex | 2 +-
labs/kernel-git/kernel-git.tex | 2 +-
labs/kernel-sources-download/kernel-sources-download.tex | 2 +-
labs/sysdev-real-time/sysdev-real-time.tex | 2 +-
labs/sysdev-tinysystem/sysdev-tinysystem.tex | 2 +-
labs/sysdev-toolchain/sysdev-toolchain.tex | 2 +-
labs/sysdev-u-boot/sysdev-u-boot.tex | 4 ++--
.../yocto-advanced-configuration.tex | 2 +-
labs/yocto-first-build/yocto-first-build.tex | 4 ++--
slides/kernel-git-content/kernel-git-content.tex | 4 ++--
.../sysdev-bootloaders-u-boot.tex | 2 +-
slides/sysdev-dev-environment/sysdev-dev-environment.tex | 10 +++++-----
.../sysdev-root-filesystem-principles.tex | 2 +-
.../sysdev-toolchains-obtaining.tex | 2 +-
slides/yocto-recipe-extra/yocto-recipe-extra.tex | 4 ++--
31 files changed, 62 insertions(+), 62 deletions(-)
diff --git a/README b/README
index 04aa3e3..44c55b7 100644
--- a/README
+++ b/README
@@ -3,7 +3,7 @@ How to compile these materials
First, you may install the packages needed to compile the materials:
-sudo apt-get install --no-install-recommends git-core inkscape \
+sudo apt install --no-install-recommends git-core inkscape \
texlive-latex-base texlive-latex-extra texlive-font-utils dia \
python-pygments texlive-fonts-recommended texlive-fonts-extra make \
texlive-xetex fonts-inconsolata fonts-liberation ttf-ubuntu-font-family \
@@ -129,7 +129,7 @@ Emacs usage in LaTeX
Install the AUCTex package which contains an improved Emacs
environment for editing LaTeX documents:
-sudo apt-get install auctex
+sudo apt install auctex
In your ~/.emacs.el file, add the following lines:
@@ -157,7 +157,7 @@ Diagrams
The recommended program to do diagrams is Dia:
- apt-get install dia
+ apt install dia
When saving a file, please make sure to unselect the "Compressed saved
files" option, so that the .dia files are raw XML files, and not
diff --git a/lab-data/boot-time/setup/install-packages b/lab-data/boot-time/setup/install-packages
index ef82843..98090b7 100755
--- a/lab-data/boot-time/setup/install-packages
+++ b/lab-data/boot-time/setup/install-packages
@@ -1,4 +1,4 @@
#!/bin/sh
# Packages to install for the boot time workshop
-sudo apt-get install picocom libxss1 git libncurses5-dev libqt4-dev u-boot-tools g++ bison flex gettext texinfo lzop ant openjdk-6-jdk meld inkscape
+sudo apt install picocom libxss1 git libncurses5-dev libqt4-dev u-boot-tools g++ bison flex gettext texinfo lzop ant openjdk-6-jdk meld inkscape
diff --git a/lab-data/common/bootloader/beaglebone-black/README.txt b/lab-data/common/bootloader/beaglebone-black/README.txt
index c4458b8..220310d 100644
--- a/lab-data/common/bootloader/beaglebone-black/README.txt
+++ b/lab-data/common/bootloader/beaglebone-black/README.txt
@@ -122,7 +122,7 @@ Toolchain
Tested on Ubuntu 13.10
Install the Linaro toolchain:
-sudo apt-get install gcc-arm-linux-gnueabi
+sudo apt install gcc-arm-linux-gnueabi
(the version at the time of our testing was 4:4.7.2-1)
Compiling U-Boot
diff --git a/lab-data/get_packages b/lab-data/get_packages
index 7ab2a47..7850172 100755
--- a/lab-data/get_packages
+++ b/lab-data/get_packages
@@ -4,22 +4,22 @@
# Caution: very partial, news updating!
# Lab setup
-apt-get install vim-full emacs nedit lzma
+apt install vim-full emacs nedit lzma
# Linux/Lab1
-apt-get install patch cscope cbrowser ketchup
+apt install patch cscope cbrowser ketchup
# Linux/Lab2
-apt-get install qemu libqt3-mt-dev g++ libncurses-dev libglade2-dev
+apt install qemu libqt3-mt-dev g++ libncurses-dev libglade2-dev
# Linux/Lab4
-apt-get install nfs-kernel-server
+apt install nfs-kernel-server
# Linux/debugging (lab 6)
-apt-get install gdb libftdi-dev
+apt install gdb libftdi-dev
# Linux/PCI
-apt-get install pciutils
+apt install pciutils
# Sysdev / buildroot
-apt-get install bison flex gettext texinfo
+apt install bison flex gettext texinfo
diff --git a/labs/android-new-board/android-new-board.tex b/labs/android-new-board/android-new-board.tex
index ec66d2f..6828a08 100644
--- a/labs/android-new-board/android-new-board.tex
+++ b/labs/android-new-board/android-new-board.tex
@@ -151,7 +151,7 @@ serial communication program, such as \code{picocom}\footnote
more complex to configure.}:
\begin{verbatim}
-sudo apt-get install picocom
+sudo apt install picocom
\end{verbatim}
You also need to make your user belong to the \code{dialout} group to be
diff --git a/labs/android-source-code/android-source-code.tex b/labs/android-source-code/android-source-code.tex
index a11eeab..fa359c9 100644
--- a/labs/android-source-code/android-source-code.tex
+++ b/labs/android-source-code/android-source-code.tex
@@ -29,7 +29,7 @@ If you don't have that much space available, go to the
Install the packages needed to fetch Android's source code:
\begin{verbatim}
-sudo apt-get install git curl
+sudo apt install git curl
\end{verbatim}
\section{Fetch the source code}
@@ -91,12 +91,12 @@ While \code{repo sync} runs, download the packages that you will need
to compile Android and its components from source:
\begin{verbatim}
-sudo apt-get install xsltproc gnupg flex bison gperf build-essential \
+sudo apt install xsltproc gnupg flex bison gperf build-essential \
zlib1g-dev libc6-dev lib32ncurses5-dev ccache unzip zip\
x11proto-core-dev libx11-dev lib32readline6-dev lib32z1-dev \
libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown \
libxml2-utils
-sudo apt-get clean
+sudo apt clean
\end{verbatim}
Again, if you have a slow connection to the Internet, installing these
@@ -114,12 +114,12 @@ nowadays.
\begin{verbatim}
sudo add-apt-repository ppa:webupd8team/java
-sudo apt-get update
+sudo apt update
\end{verbatim}
Now, we can install the latest JDK version with the command:
\begin{verbatim}
-sudo apt-get install oracle-java6-installer
+sudo apt install oracle-java6-installer
\end{verbatim}
Follow the steps asked, and you should be all set!
diff --git a/labs/autotools-advanced/autotools-advanced.tex b/labs/autotools-advanced/autotools-advanced.tex
index 2d7a3c1..66fc15a 100644
--- a/labs/autotools-advanced/autotools-advanced.tex
+++ b/labs/autotools-advanced/autotools-advanced.tex
@@ -131,7 +131,7 @@ can install this library on your system, and its development files by
running:
\begin{verbatim}
-apt-get install libconfig-dev
+apt install libconfig-dev
\end{verbatim}
Now, change \code{src/hello.c} to do the following:
diff --git a/labs/autotools-usage/autotools-usage.tex b/labs/autotools-usage/autotools-usage.tex
index 0f0951f..c9b26de 100644
--- a/labs/autotools-usage/autotools-usage.tex
+++ b/labs/autotools-usage/autotools-usage.tex
@@ -76,7 +76,7 @@ To cross-compile {\em ethtool}, we'll first have to install a
cross-compiler:
\begin{verbatim}
-apt-get install gcc-arm-linux-gnueabihf
+apt install gcc-arm-linux-gnueabihf
\end{verbatim}
Then you can do:
@@ -138,7 +138,7 @@ source code of a library called {\em libconfuse}:
git clone https://github.com/martinh/libconfuse
\end{verbatim}
-Note: you may need to install {\em Git}, using \code{apt-get install
+Note: you may need to install {\em Git}, using \code{apt install
git}.
Look at the {\em libconfuse} source code, and see that you only have
@@ -154,7 +154,7 @@ because your system doesn't have the {\em autotools} installed. In
this case, run:
\begin{verbatim}
-apt-get install autoconf automake libtool autopoint gettext
+apt install autoconf automake libtool autopoint gettext
\end{verbatim}
(Note: \code{autopoint} and \code{gettext} are needed because this
@@ -176,7 +176,7 @@ wasn't available, but did not error out. As you can see not all
Install {\em flex}:
\begin{verbatim}
-apt-get install flex
+apt install flex
\end{verbatim}
Re-run \code{./configure}, and restart the build.
diff --git a/labs/boottime-getting-started/boottime-getting-started.tex b/labs/boottime-getting-started/boottime-getting-started.tex
index 633e919..772b550 100644
--- a/labs/boottime-getting-started/boottime-getting-started.tex
+++ b/labs/boottime-getting-started/boottime-getting-started.tex
@@ -48,7 +48,7 @@ serial console. It works in a simple terminal. \code{minicom} has more
features, but is also more complex to configure.}:
\begin{verbatim}
-sudo apt-get install picocom
+sudo apt install picocom
\end{verbatim}
Now, run the below command, to start serial communication on
@@ -125,14 +125,14 @@ tar xf sama5d3xek-demo.tar.xz
SAM-BA requires an extra Ubuntu package:
\begin{verbatim}
-sudo apt-get install libxss1
+sudo apt install libxss1
\end{verbatim}
If you have a 64 bit system (if the \code{arch} command returns
\code{x86_64}, SAM-BA also needs the 32-bit libraries:
\begin{verbatim}
-sudo apt-get install ia32-libs
+sudo apt install ia32-libs
\end{verbatim}
Make sure that \code{JP9} is open to enable booting from the
diff --git a/labs/boottime-init-scripts/boottime-init-scripts.tex b/labs/boottime-init-scripts/boottime-init-scripts.tex
index 0515adc..1deb07c 100644
--- a/labs/boottime-init-scripts/boottime-init-scripts.tex
+++ b/labs/boottime-init-scripts/boottime-init-scripts.tex
@@ -72,7 +72,7 @@ To use \code{bootchart} on your workstation, you first need to
install a few Java packages:
\begin{verbatim}
-sudo apt-get install ant openjdk-6-jdk
+sudo apt install ant openjdk-6-jdk
\end{verbatim}
Now, get the \code{bootchart} source code\footnote{The source
diff --git a/labs/boottime-install/boottime-install.tex b/labs/boottime-install/boottime-install.tex
index 176ff16..d01a052 100644
--- a/labs/boottime-install/boottime-install.tex
+++ b/labs/boottime-install/boottime-install.tex
@@ -55,8 +55,8 @@ space, you can of course have a dedicated partition for \code{/opt}.
At the end of installation, we recommend to install the latest updates:
\begin{verbatim}
-sudo apt-get update
-sudo apt-get dist-upgrade
+sudo apt update
+sudo apt dist-upgrade
\end{verbatim}
\section{Preparing a USB disk for the workshop}
diff --git a/labs/boottime-kernel/boottime-kernel.tex b/labs/boottime-kernel/boottime-kernel.tex
index 7c66cb1..25ec250 100644
--- a/labs/boottime-kernel/boottime-kernel.tex
+++ b/labs/boottime-kernel/boottime-kernel.tex
@@ -96,7 +96,7 @@ You can view the boot graph with the \code{inkscape} vector graphics
editor:
\begin{verbatim}
-sudo apt-get install inkscape
+sudo apt install inkscape
inkscape boot.svg
\end{verbatim}
diff --git a/labs/boottime-measuring/boottime-measuring.tex b/labs/boottime-measuring/boottime-measuring.tex
index 7e12806..18340dd 100644
--- a/labs/boottime-measuring/boottime-measuring.tex
+++ b/labs/boottime-measuring/boottime-measuring.tex
@@ -158,8 +158,8 @@ components like the Linux kernel, you will need to install several
software development packages:
\begin{verbatim}
-sudo apt-get install git libncurses5-dev u-boot-tools g++ bison
-sudo apt-get install flex gettext texinfo libqt4-dev lzop
+sudo apt install git libncurses5-dev u-boot-tools g++ bison
+sudo apt install flex gettext texinfo libqt4-dev lzop
\end{verbatim}
Also install the \code{meld} package. It is a very
@@ -167,7 +167,7 @@ convenient utility to compare different versions of a file, which
is often useful in an optimization project.
\begin{verbatim}
-sudo apt-get install meld
+sudo apt install meld
\end{verbatim}
Now, to be able to update the root filesystem, you need to reconstitute
diff --git a/labs/buildroot-basic/buildroot-basic.tex b/labs/buildroot-basic/buildroot-basic.tex
index 9367410..763ae34 100644
--- a/labs/buildroot-basic/buildroot-basic.tex
+++ b/labs/buildroot-basic/buildroot-basic.tex
@@ -21,7 +21,7 @@ Buildroot requires a few packages to be installed on your
machine. Let's install them using Ubuntu's package manager:
\begin{verbatim}
-sudo apt-get install sed make binutils gcc g++ bash patch \
+sudo apt install sed make binutils gcc g++ bash patch \
gzip bzip2 perl tar cpio python unzip rsync wget libncurses-dev
\end{verbatim}
@@ -288,7 +288,7 @@ To communicate with the board through the serial port, install a
serial communication program, such as \code{picocom}:
\begin{verbatim}
-sudo apt-get install picocom
+sudo apt install picocom
\end{verbatim}
If you run \code{ls -l /dev/ttyUSB0}, you can also see that only
diff --git a/labs/kernel-board-setup/kernel-board-setup.tex b/labs/kernel-board-setup/kernel-board-setup.tex
index 17b0aba..10c6fac 100644
--- a/labs/kernel-board-setup/kernel-board-setup.tex
+++ b/labs/kernel-board-setup/kernel-board-setup.tex
@@ -71,7 +71,7 @@ To communicate with the board through the serial port, install a
serial communication program, such as \code{picocom}:
\begin{verbatim}
-sudo apt-get install picocom
+sudo apt install picocom
\end{verbatim}
If you run \code{ls -l /dev/ttyUSB0}, you can also see that only
@@ -140,7 +140,7 @@ board download files, such as the kernel image and Device Tree Binary
To start with, install a TFTP server on your development workstation:
\begin{verbatim}
-sudo apt-get install tftpd-hpa
+sudo apt install tftpd-hpa
\end{verbatim}
With a network cable, connect the Ethernet port of your board to the
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 f69aa05..b496868 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
@@ -44,7 +44,7 @@ Install packages needed for configuring, compiling and booting
the kernel for your board:
\begin{verbatim}
-sudo apt-get install qt5-default g++ pkg-config
+sudo apt install qt5-default g++ pkg-config
\end{verbatim}
\code{qt5-default} and \code{g++} are needed for \code{make xconfig}.
@@ -56,7 +56,7 @@ very popular source for ARM toolchains (amongst other useful resources
for Linux on ARM).
\begin{verbatim}
-sudo apt-get install gcc-arm-linux-gnueabi
+sudo apt install gcc-arm-linux-gnueabi
\end{verbatim}
Now find out the path and name of the cross-compiler executable by looking at the contents of the package:
diff --git a/labs/kernel-debugging/kernel-debugging.tex b/labs/kernel-debugging/kernel-debugging.tex
index d246c50..27a459d 100644
--- a/labs/kernel-debugging/kernel-debugging.tex
+++ b/labs/kernel-debugging/kernel-debugging.tex
@@ -110,7 +110,7 @@ supporting multiple architectures at once. If you have a cross
toolchain including gdb, you can also run arm-linux-gdb directly.}:
\begin{verbatim}
-sudo apt-get install gdb-multiarch
+sudo apt install gdb-multiarch
gdb-multiarch vmlinux
(gdb) set arch arm
(gdb) set gnutarget elf32-littlearm
diff --git a/labs/kernel-git/kernel-git.tex b/labs/kernel-git/kernel-git.tex
index 7b4b459..4a0bd47 100644
--- a/labs/kernel-git/kernel-git.tex
+++ b/labs/kernel-git/kernel-git.tex
@@ -52,7 +52,7 @@ Find something to modify in the Linux kernel sources. Here are ideas:
(simpler because you don't have to repeat the location in the tree).
Make sure that the new DT is equivalent by decompiling and comparing the old DTB
and the new DTB (\code{dtc -I dtb}).
-\item Run \code{apt-get install coccinelle} and \code{make coccicheck}
+\item Run \code{apt install coccinelle} and \code{make coccicheck}
and try to propose fixes for the reported bugs (\code{coccinelle}
can propose patches too, but they need to be reviewed by humans
before submission.
diff --git a/labs/kernel-sources-download/kernel-sources-download.tex b/labs/kernel-sources-download/kernel-sources-download.tex
index 4b8f810..0713e6f 100644
--- a/labs/kernel-sources-download/kernel-sources-download.tex
+++ b/labs/kernel-sources-download/kernel-sources-download.tex
@@ -11,7 +11,7 @@ First, let's install software packages that we will need
throughout the practical labs:
\begin{verbatim}
-sudo apt-get install git gitk git-email
+sudo apt install git gitk git-email
\end{verbatim}
\section{Git configuration}
diff --git a/labs/sysdev-real-time/sysdev-real-time.tex b/labs/sysdev-real-time/sysdev-real-time.tex
index 64864b2..5f31d62 100644
--- a/labs/sysdev-real-time/sysdev-real-time.tex
+++ b/labs/sysdev-real-time/sysdev-real-time.tex
@@ -78,7 +78,7 @@ you to install 32 bit compatibility packages to be able to execute the
Sourcery CodeBench external toolchain:
\begin{verbatim}
-sudo apt-get install libc6-i386 lib32stdc++6 lib32z1
+sudo apt install libc6-i386 lib32stdc++6 lib32z1
\end{verbatim}
At the end of the build job, extract the
diff --git a/labs/sysdev-tinysystem/sysdev-tinysystem.tex b/labs/sysdev-tinysystem/sysdev-tinysystem.tex
index 0d360d7..4c0fa2f 100644
--- a/labs/sysdev-tinysystem/sysdev-tinysystem.tex
+++ b/labs/sysdev-tinysystem/sysdev-tinysystem.tex
@@ -141,7 +141,7 @@ We are going to use \code{make gconfig} this time. Before doing this,
install the required packages:
\begin{verbatim}
-sudo apt-get install libglade2-dev
+sudo apt install libglade2-dev
\end{verbatim}
Now, configure BusyBox with the configuration file provided in the
diff --git a/labs/sysdev-toolchain/sysdev-toolchain.tex b/labs/sysdev-toolchain/sysdev-toolchain.tex
index 377c5cd..251e7f3 100644
--- a/labs/sysdev-toolchain/sysdev-toolchain.tex
+++ b/labs/sysdev-toolchain/sysdev-toolchain.tex
@@ -18,7 +18,7 @@ Go to the \code{$HOME/embedded-linux-labs/toolchain} directory.
Install the packages needed for this lab:
\begin{verbatim}
-sudo apt-get install autoconf automake libtool-bin libexpat1-dev \
+sudo apt install autoconf automake libtool-bin libexpat1-dev \
libncurses5-dev bison flex patch curl cvs texinfo git bc \
build-essential subversion gawk python-dev gperf unzip \
pkg-config help2man wget
diff --git a/labs/sysdev-u-boot/sysdev-u-boot.tex b/labs/sysdev-u-boot/sysdev-u-boot.tex
index 0b8a89f..aaab1b6 100644
--- a/labs/sysdev-u-boot/sysdev-u-boot.tex
+++ b/labs/sysdev-u-boot/sysdev-u-boot.tex
@@ -63,7 +63,7 @@ To communicate with the board through the serial port, install a
serial communication program, such as \code{picocom}:
\begin{verbatim}
-sudo apt-get install picocom
+sudo apt install picocom
\end{verbatim}
You also need to make your user belong to the \code{dialout} group to be
@@ -222,7 +222,7 @@ Basically, you need to:
need to have the Device Tree compiler:
\begin{verbatim}
-sudo apt-get install device-tree-compiler
+sudo apt install device-tree-compiler
\end{verbatim}
\item Finally, run \code{make}, which should build U-Boot.
diff --git a/labs/yocto-advanced-configuration/yocto-advanced-configuration.tex b/labs/yocto-advanced-configuration/yocto-advanced-configuration.tex
index d2c180b..8ed6c78 100644
--- a/labs/yocto-advanced-configuration/yocto-advanced-configuration.tex
+++ b/labs/yocto-advanced-configuration/yocto-advanced-configuration.tex
@@ -53,7 +53,7 @@ click on the \code{Apply} button).
First install the NFS server on the training computer and create the root NFS
directory:
\begin{verbatim}
-sudo apt-get install nfs-kernel-server
+sudo apt install nfs-kernel-server
sudo mkdir -m 777 /nfs
\end{verbatim}
diff --git a/labs/yocto-first-build/yocto-first-build.tex b/labs/yocto-first-build/yocto-first-build.tex
index be65228..ada50f7 100644
--- a/labs/yocto-first-build/yocto-first-build.tex
+++ b/labs/yocto-first-build/yocto-first-build.tex
@@ -18,7 +18,7 @@ Go to the \code{$HOME/yocto-labs/} directory.
Install the required packages:
\begin{verbatim}
-sudo apt-get install bc build-essential chrpath cpio diffstat gawk git python texinfo wget
+sudo apt install bc build-essential chrpath cpio diffstat gawk git python texinfo wget
\end{verbatim}
\section{Download Yocto}
@@ -138,7 +138,7 @@ To communicate with the board through the serial port, install a
serial communication program, such as \code{picocom}:
\begin{verbatim}
-sudo apt-get install picocom
+sudo apt install picocom
\end{verbatim}
If you run \code{ls -l /dev/ttyUSB0}, you can also see that only
diff --git a/slides/kernel-git-content/kernel-git-content.tex b/slides/kernel-git-content/kernel-git-content.tex
index 42ca34f..e55f565 100644
--- a/slides/kernel-git-content/kernel-git-content.tex
+++ b/slides/kernel-git-content/kernel-git-content.tex
@@ -23,7 +23,7 @@
\begin{itemize}
\item Git is available as a package in your distribution
\begin{itemize}
- \item \code{sudo apt-get install git}
+ \item \code{sudo apt install git}
\end{itemize}
\item Everything is available through the git command
\begin{itemize}
@@ -351,7 +351,7 @@ Signed-off-by: David S. Miller <davem at davemloft.net>
\includegraphics[height=0.45\textheight]{slides/kernel-git-content/git-gui.png}
\end{center}
\item Example usage on Ubuntu/Debian:\\
- \code{sudo apt-get install git-gui}\\
+ \code{sudo apt install git-gui}\\
\code{git gui blame Makefile}
\end{itemize}
\end{frame}
diff --git a/slides/sysdev-bootloaders-u-boot/sysdev-bootloaders-u-boot.tex b/slides/sysdev-bootloaders-u-boot/sysdev-bootloaders-u-boot.tex
index 0ee94a2..d5fcb59 100644
--- a/slides/sysdev-bootloaders-u-boot/sysdev-bootloaders-u-boot.tex
+++ b/slides/sysdev-bootloaders-u-boot/sysdev-bootloaders-u-boot.tex
@@ -361,7 +361,7 @@ u-boot # saveenv
\end{itemize}
\item A TFTP server is needed on the development workstation
\begin{itemize}
- \item \code{sudo apt-get install tftpd-hpa}
+ \item \code{sudo apt install tftpd-hpa}
\item All files in \code{/var/lib/tftpboot} are then visible
through TFTP
\item A TFTP client is available in the \code{tftp-hpa} package,
diff --git a/slides/sysdev-dev-environment/sysdev-dev-environment.tex b/slides/sysdev-dev-environment/sysdev-dev-environment.tex
index 307c55c..0b29d01 100644
--- a/slides/sysdev-dev-environment/sysdev-dev-environment.tex
+++ b/slides/sysdev-dev-environment/sysdev-dev-environment.tex
@@ -114,7 +114,7 @@
\begin{itemize}
\item Package repositories are specified in \code{/etc/apt/sources.list}
\item To update package repository lists:\\
- \code{sudo apt-get update}
+ \code{sudo apt update}
\item To find the name of a package to install, the best is to use
the search engine on \url{http://packages.debian.org} or on
\url{http://packages.ubuntu.com}. You may
@@ -127,11 +127,11 @@
\frametitle{Managing software packages (2)}
\begin{itemize}
\item To install a given package:\\
- \code{sudo apt-get install <package>}
+ \code{sudo apt install <package>}
\item To remove a given package:\\
- \code{sudo apt-get remove <package>}
+ \code{sudo apt remove <package>}
\item To install all available package updates:\\
- \code{sudo apt-get dist-upgrade}
+ \code{sudo apt dist-upgrade}
\item Get information about a package:\\
\code{apt-cache show <package>}
\item Graphical interfaces
@@ -173,7 +173,7 @@
\item In this training session, we recommend using the simplest of
them: \code{picocom}
\begin{itemize}
- \item Installation with \code{sudo apt-get install picocom}
+ \item Installation with \code{sudo apt install picocom}
\item Run with \code{picocom -b BAUD_RATE /dev/SERIAL_DEVICE}
\item Exit with \code{Control-A Control-X}
\end{itemize}
diff --git a/slides/sysdev-root-filesystem-principles/sysdev-root-filesystem-principles.tex b/slides/sysdev-root-filesystem-principles/sysdev-root-filesystem-principles.tex
index 364b058..a6c8ac7 100644
--- a/slides/sysdev-root-filesystem-principles/sysdev-root-filesystem-principles.tex
+++ b/slides/sysdev-root-filesystem-principles/sysdev-root-filesystem-principles.tex
@@ -168,7 +168,7 @@ Kernel panic - not syncing: VFS: Unable to mount root fs on unknown block(0,0)
\begin{itemize}
\item Install an NFS server (example: Debian, Ubuntu)\\
- \code{sudo apt-get install nfs-kernel-server}
+ \code{sudo apt install nfs-kernel-server}
\item Add the exported directory to your \code{/etc/exports} file:\\
\code{/home/tux/rootfs 192.168.1.111(rw,no_root_squash,no_subtree_check)}
\begin{itemize}
diff --git a/slides/sysdev-toolchains-obtaining/sysdev-toolchains-obtaining.tex b/slides/sysdev-toolchains-obtaining/sysdev-toolchains-obtaining.tex
index 37f2372..8769800 100644
--- a/slides/sysdev-toolchains-obtaining/sysdev-toolchains-obtaining.tex
+++ b/slides/sysdev-toolchains-obtaining/sysdev-toolchains-obtaining.tex
@@ -34,7 +34,7 @@
\begin{itemize}
\item Toolchains packaged by your distribution\\
Ubuntu example:\\
- \code{sudo apt-get install gcc-arm-linux-gnueabihf}
+ \code{sudo apt install gcc-arm-linux-gnueabihf}
\item Sourcery CodeBench toolchains, now only supporting MIPS,
NIOS-II, AMD64, Hexagon. Old versions with ARM support still
available through build systems (Buildroot...)
diff --git a/slides/yocto-recipe-extra/yocto-recipe-extra.tex b/slides/yocto-recipe-extra/yocto-recipe-extra.tex
index 9c6ca09..52abff0 100644
--- a/slides/yocto-recipe-extra/yocto-recipe-extra.tex
+++ b/slides/yocto-recipe-extra/yocto-recipe-extra.tex
@@ -220,8 +220,8 @@ rootfs_deb_do_rootfs () {
[...]
- apt-get update
- apt-get ${APT_ARGS} install ${package_to_install} \
+ apt update
+ apt ${APT_ARGS} install ${package_to_install} \
--force-yes --allow-unauthenticated
[...]
More information about the training-materials-updates
mailing list