[bootlin/training-materials updates] master: Use "ip" instead of "ifconfig" (deprecated) (9fae4d0e)

Michael Opdenacker michael.opdenacker at bootlin.com
Wed Sep 2 11:11:01 CEST 2020


Repository : https://github.com/bootlin/training-materials
On branch  : master
Link       : https://github.com/bootlin/training-materials/commit/9fae4d0e5d7dc7137c3d08483f50468bbea315a9

>---------------------------------------------------------------

commit 9fae4d0e5d7dc7137c3d08483f50468bbea315a9
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date:   Wed Sep 2 11:11:01 2020 +0200

    Use "ip" instead of "ifconfig" (deprecated)
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>


>---------------------------------------------------------------

9fae4d0e5d7dc7137c3d08483f50468bbea315a9
 labs/buildroot-rootfs/buildroot-rootfs.tex                           | 2 +-
 labs/sysdev-u-boot-qemu/sysdev-u-boot-qemu.tex                       | 4 ++--
 labs/sysdev-u-boot-stm32/sysdev-u-boot-stm32.tex                     | 5 ++---
 labs/sysdev-u-boot/sysdev-u-boot.tex                                 | 4 ++--
 .../yocto-advanced-configuration-stm32.tex                           | 4 ++--
 slides/kernel-frameworks/kernel-frameworks.tex                       | 2 +-
 .../sysdev-root-filesystem-contents.tex                              | 2 +-
 .../sysdev-root-filesystem-minimal.tex                               | 2 +-
 8 files changed, 12 insertions(+), 13 deletions(-)

diff --git a/labs/buildroot-rootfs/buildroot-rootfs.tex b/labs/buildroot-rootfs/buildroot-rootfs.tex
index 5747cff1..3f82d775 100644
--- a/labs/buildroot-rootfs/buildroot-rootfs.tex
+++ b/labs/buildroot-rootfs/buildroot-rootfs.tex
@@ -130,7 +130,7 @@ we'll use NetworkManager and its command line interface:
 nmcli con add type ethernet ifname enxf8dc7a000001 ip4 192.168.0.1/24
 \end{verbatim}
 
-{\em Note: using \code{ifconfig} in the command line is not
+{\em Note: using \code{ip} in the command line is not
 recommended, because Network Manager will unconfigure and
 reconfigure the network interface each time the board is rebooted.}
 
diff --git a/labs/sysdev-u-boot-qemu/sysdev-u-boot-qemu.tex b/labs/sysdev-u-boot-qemu/sysdev-u-boot-qemu.tex
index 1eefe062..9375fa81 100644
--- a/labs/sysdev-u-boot-qemu/sysdev-u-boot-qemu.tex
+++ b/labs/sysdev-u-boot-qemu/sysdev-u-boot-qemu.tex
@@ -211,7 +211,7 @@ script that will bring up a network interface between QEMU and the host. Here ar
 
 \begin{verbatim}
 #!/bin/bash
-exec /sbin/ifconfig $1 192.168.0.1
+exec /sbin/ip a add 192.168.0.1/24 dev $1
 \end{verbatim}
 
 Of course, make this script executable:
@@ -240,7 +240,7 @@ Note the new net options:
 \item \code{-net nic}: adds a network device to the emulated machine
 \end{itemize}
 
-On the host machine, using the \code{ifconfig} command, check that
+On the host machine, using the \code{ip a} command, check that
 there is now a \code{tap0} network interface with the expected IP
 address.
 
diff --git a/labs/sysdev-u-boot-stm32/sysdev-u-boot-stm32.tex b/labs/sysdev-u-boot-stm32/sysdev-u-boot-stm32.tex
index ac7341c9..c1925dce 100644
--- a/labs/sysdev-u-boot-stm32/sysdev-u-boot-stm32.tex
+++ b/labs/sysdev-u-boot-stm32/sysdev-u-boot-stm32.tex
@@ -309,10 +309,9 @@ wired connection to the network, your instructor will provide you with
 a USB Ethernet adapter. A new network interface should appear on your
 Linux system.
 
-Install the \code{net-tools} package and find the name of this interface
-by typing:
+Find the name of this interface by typing:
 \begin{verbatim}
-ifconfig -a
+ip a
 \end{verbatim}
 
 The network interface name is likely to be
diff --git a/labs/sysdev-u-boot/sysdev-u-boot.tex b/labs/sysdev-u-boot/sysdev-u-boot.tex
index ffffa83e..3ca4f10e 100644
--- a/labs/sysdev-u-boot/sysdev-u-boot.tex
+++ b/labs/sysdev-u-boot/sysdev-u-boot.tex
@@ -287,9 +287,9 @@ wired connection to the network, your instructor will provide you with
 a USB Ethernet adapter. A new network interface should appear on your
 Linux system.
 
-Install the \code{net-tools} package and find the name of this interface by typing:
+Find the name of this interface by typing:
 \begin{verbatim}
-ifconfig -a
+ip a
 \end{verbatim}
 
 The network interface name is likely to be
diff --git a/labs/yocto-advanced-configuration-stm32/yocto-advanced-configuration-stm32.tex b/labs/yocto-advanced-configuration-stm32/yocto-advanced-configuration-stm32.tex
index 2eb77af0..5129902a 100644
--- a/labs/yocto-advanced-configuration-stm32/yocto-advanced-configuration-stm32.tex
+++ b/labs/yocto-advanced-configuration-stm32/yocto-advanced-configuration-stm32.tex
@@ -33,9 +33,9 @@ one of your computer. If your computer already has a wired connection
 to the network, your instructor will provide you with a USB Ethernet
 adapter. A new network interface should appear on your Linux system.
 
-Install the \code{net-tools} package and find the name of this interface by typing:
+Find the name of this interface by typing:
 \begin{verbatim}
-ifconfig -a
+ip a
 \end{verbatim}
 
 The network interface name is likely to be
diff --git a/slides/kernel-frameworks/kernel-frameworks.tex b/slides/kernel-frameworks/kernel-frameworks.tex
index c3f12f27..ca3c336a 100644
--- a/slides/kernel-frameworks/kernel-frameworks.tex
+++ b/slides/kernel-frameworks/kernel-frameworks.tex
@@ -25,7 +25,7 @@
   three types of devices:
   \begin{itemize}
   \item {\bf Network devices}. They are represented as network
-    interfaces, visible in user space using \code{ifconfig}.
+    interfaces, visible in user space using \code{ip a}
   \item {\bf Block devices}. They are used to provide user space
     applications access to raw storage devices (hard disks, USB
     keys). They are visible to the applications as {\em device files}
diff --git a/slides/sysdev-root-filesystem-contents/sysdev-root-filesystem-contents.tex b/slides/sysdev-root-filesystem-contents/sysdev-root-filesystem-contents.tex
index 36bb7a6f..aedd30dc 100644
--- a/slides/sysdev-root-filesystem-contents/sysdev-root-filesystem-contents.tex
+++ b/slides/sysdev-root-filesystem-contents/sysdev-root-filesystem-contents.tex
@@ -64,7 +64,7 @@
     down, some binaries and libraries are stored in \code{/bin},
     \code{/sbin} and \code{/lib}
   \item \code{/bin} and \code{/sbin} contain programs like \code{ls},
-    \code{ifconfig}, \code{cp}, \code{bash}, etc.
+    \code{ip}, \code{cp}, \code{bash}, etc.
   \item \code{/lib} contains the C library and sometimes a few other
     basic libraries
   \item All other programs and libraries are in \code{/usr}
diff --git a/slides/sysdev-root-filesystem-minimal/sysdev-root-filesystem-minimal.tex b/slides/sysdev-root-filesystem-minimal/sysdev-root-filesystem-minimal.tex
index 4b6c0127..c762b914 100644
--- a/slides/sysdev-root-filesystem-minimal/sysdev-root-filesystem-minimal.tex
+++ b/slides/sysdev-root-filesystem-minimal/sysdev-root-filesystem-minimal.tex
@@ -25,7 +25,7 @@
         to interact with the system
   \item Basic UNIX executables, for use in system scripts or in
         interactive shells: \code{mv}, \code{cp}, \code{mkdir}, \code{cat},
-        \code{modprobe}, \code{mount}, \code{ifconfig}, etc.
+        \code{modprobe}, \code{mount}, \code{ip}, etc.
   \item These basic components have to be integrated into the root
     filesystem to make it usable
   \end{itemize}




More information about the training-materials-updates mailing list