[bootlin/training-materials updates] master: Replace "Unix" by "UNIX" (eab02265)

Michael Opdenacker michael.opdenacker at bootlin.com
Mon May 11 15:33:41 CEST 2020


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

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

commit eab022656ff83d06d5cff9e81fbfbac52a5c206c
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date:   Mon May 11 15:33:41 2020 +0200

    Replace "Unix" by "UNIX"
    
    - To use the trademark name
    - I have the impression that this is more familiar, but you may disagree
    - Wikipedia uses "Unix" though.
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>


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

eab022656ff83d06d5cff9e81fbfbac52a5c206c
 agenda/autotools-agenda.tex                                           | 2 +-
 agenda/boot-time-agenda.tex                                           | 2 +-
 agenda/buildroot-agenda.tex                                           | 2 +-
 agenda/buildroot-fr-agenda.tex                                        | 2 +-
 agenda/buildroot-online-agenda.tex                                    | 2 +-
 agenda/embedded-linux-4d-fr-agenda.tex                                | 2 +-
 agenda/embedded-linux-fr-agenda.tex                                   | 2 +-
 agenda/linux-kernel-agenda.tex                                        | 2 +-
 agenda/linux-kernel-fr-agenda.tex                                     | 4 ++--
 agenda/linux-kernel-online-agenda.tex                                 | 2 +-
 agenda/yocto-agenda.tex                                               | 2 +-
 agenda/yocto-fr-agenda.tex                                            | 2 +-
 agenda/yocto-online-agenda.tex                                        | 2 +-
 lab-data/embedded-linux/realtime/data/rttest.c                        | 2 +-
 lab-data/embedded-linux/tinysystem/data/www/cgi-bin/upload.c          | 4 ++--
 slides/autotools-advanced/autotools-advanced.tex                      | 2 +-
 slides/autotools-usage/autotools-usage.tex                            | 2 +-
 slides/buildroot-rootfs/buildroot-rootfs.tex                          | 4 ++--
 slides/graphics-software/graphics-software.tex                        | 4 ++--
 .../kernel-driver-development-processes.tex                           | 2 +-
 slides/kernel-source-code-drivers/kernel-source-code-drivers.tex      | 4 ++--
 .../sysdev-application-development/sysdev-application-development.tex | 2 +-
 slides/sysdev-block-filesystems/sysdev-block-filesystems.tex          | 2 +-
 slides/sysdev-busybox/sysdev-busybox.tex                              | 4 ++--
 slides/sysdev-device-files/sysdev-device-files.tex                    | 2 +-
 slides/sysdev-embedded-linux/sysdev-embedded-linux.tex                | 4 ++--
 slides/sysdev-intro/sysdev-intro.tex                                  | 2 +-
 slides/sysdev-realtime/sysdev-realtime.tex                            | 4 ++--
 .../sysdev-root-filesystem-contents.tex                               | 2 +-
 .../sysdev-root-filesystem-minimal/sysdev-root-filesystem-minimal.tex | 2 +-
 .../sysdev-root-filesystem-principles.tex                             | 2 +-
 31 files changed, 39 insertions(+), 39 deletions(-)

diff --git a/agenda/autotools-agenda.tex b/agenda/autotools-agenda.tex
index b6238d6b..572ff804 100644
--- a/agenda/autotools-agenda.tex
+++ b/agenda/autotools-agenda.tex
@@ -67,7 +67,7 @@
     {\bf Prerequisites} & {\bf Knowledge of embedded Linux} as covered
     in our embedded Linux course:
     \newline \url{https://bootlin.com/training/embedded-linux/} \vspace{1em}
-    \newline {\bf Knowledge and practice of Unix or GNU/Linux commands}
+    \newline {\bf Knowledge and practice of UNIX or GNU/Linux commands}
     \newline People lacking experience on this topic should get
     trained by themselves, for example with our freely available on-line slides:
     \newline \url{https://bootlin.com/blog/command-line/} \\
diff --git a/agenda/boot-time-agenda.tex b/agenda/boot-time-agenda.tex
index 1a95d53e..6184300a 100644
--- a/agenda/boot-time-agenda.tex
+++ b/agenda/boot-time-agenda.tex
@@ -64,7 +64,7 @@ Boot Time Optimization Training\\
     \newline People supporting embedded Linux system developers. \\
     \hline
 
-    {\bf Prerequisites} & {\bf Knowledge and practice of Unix or
+    {\bf Prerequisites} & {\bf Knowledge and practice of UNIX or
       GNU/Linux commands}
     \newline People lacking experience on this topic should get
     trained by themselves, for example with our freely available
diff --git a/agenda/buildroot-agenda.tex b/agenda/buildroot-agenda.tex
index 8084260c..f3c83ada 100644
--- a/agenda/buildroot-agenda.tex
+++ b/agenda/buildroot-agenda.tex
@@ -73,7 +73,7 @@ Embedded Linux development with Buildroot training\\
     {\bf Prerequisites} & {\bf Knowledge of embedded Linux} as covered
     in our embedded Linux course:
     \newline \url{https://bootlin.com/training/embedded-linux/} \vspace{1em}
-    \newline {\bf Knowledge and practice of Unix or GNU/Linux commands}
+    \newline {\bf Knowledge and practice of UNIX or GNU/Linux commands}
     \newline People lacking experience on this topic should get
     trained by themselves, for example with our freely available
     on-line slides:
diff --git a/agenda/buildroot-fr-agenda.tex b/agenda/buildroot-fr-agenda.tex
index 386cf4ba..cdecc78e 100644
--- a/agenda/buildroot-fr-agenda.tex
+++ b/agenda/buildroot-fr-agenda.tex
@@ -74,7 +74,7 @@ Session de 3 jours
     {\bf Pré-requis} & {\bf Connaissance de Linux embarqué}, sujet couvert par
     notre formation Linux embarqué :
     \newline \url{https://bootlin.com/training/embedded-linux/} \vspace{1em}
-    \newline {\bf Connaissance et pratique des commandes Unix ou
+    \newline {\bf Connaissance et pratique des commandes UNIX ou
     GNU/Linux}
     \newline Les personnes n'ayant pas ces connaissances doivent
     s'autoformer, par exemple en utilisant nos supports de formations
diff --git a/agenda/buildroot-online-agenda.tex b/agenda/buildroot-online-agenda.tex
index bb80d0ae..710c7eee 100644
--- a/agenda/buildroot-online-agenda.tex
+++ b/agenda/buildroot-online-agenda.tex
@@ -73,7 +73,7 @@ On-line seminar
     {\bf Prerequisites} & {\bf Familiarity with embedded Linux} as covered
     in our embedded Linux course:
     \newline \url{https://bootlin.com/training/embedded-linux/} \vspace{1em}
-    \newline {\bf Knowledge and practice of Unix or GNU/Linux commands}
+    \newline {\bf Knowledge and practice of UNIX or GNU/Linux commands}
     \newline People lacking experience on this topic may get
     trained by themselves, for example with our freely available
     on-line slides:
diff --git a/agenda/embedded-linux-4d-fr-agenda.tex b/agenda/embedded-linux-4d-fr-agenda.tex
index e3f25638..fec4270c 100644
--- a/agenda/embedded-linux-4d-fr-agenda.tex
+++ b/agenda/embedded-linux-4d-fr-agenda.tex
@@ -67,7 +67,7 @@ Travaux pratiques sur carte ARM STM32MP157A-DK1 Discovery Board. \\
 
     {\bf Pré-requis} &
 
-    {\bf Connaissance et pratique des commandes Unix ou
+    {\bf Connaissance et pratique des commandes UNIX ou
     GNU/Linux}
     \newline Les personnes n'ayant pas ces connaissances doivent
     s'autoformer, par exemple en utilisant nos supports de formations
diff --git a/agenda/embedded-linux-fr-agenda.tex b/agenda/embedded-linux-fr-agenda.tex
index 2a87bf4d..d1e3c527 100644
--- a/agenda/embedded-linux-fr-agenda.tex
+++ b/agenda/embedded-linux-fr-agenda.tex
@@ -69,7 +69,7 @@ Travaux pratiques avec une carte ARM. \\
 
     {\bf Pré-requis} &
 
-    {\bf Connaissance et pratique des commandes Unix ou
+    {\bf Connaissance et pratique des commandes UNIX ou
     GNU/Linux}
     \newline Les personnes n'ayant pas ces connaissances doivent
     s'autoformer, par exemple en utilisant nos supports de formations
diff --git a/agenda/linux-kernel-agenda.tex b/agenda/linux-kernel-agenda.tex
index dc0a51ba..af6beb8f 100644
--- a/agenda/linux-kernel-agenda.tex
+++ b/agenda/linux-kernel-agenda.tex
@@ -194,7 +194,7 @@ Embedded Linux kernel and driver development training\\
   \item Making searches in the Linux kernel sources: looking for C
     definitions, for definitions of kernel configuration parameters,
     and for other kinds of information.
-  \item Using the Unix command line and then kernel source code
+  \item Using the UNIX command line and then kernel source code
     browsers.
  \end{itemize}
 }
diff --git a/agenda/linux-kernel-fr-agenda.tex b/agenda/linux-kernel-fr-agenda.tex
index 06a99ecc..b6046bcd 100644
--- a/agenda/linux-kernel-fr-agenda.tex
+++ b/agenda/linux-kernel-fr-agenda.tex
@@ -71,7 +71,7 @@ Session de 5 jours
     la création et la gestion de types et de structures de données
     complexes, de pointeurs vers de tels symboles, et de pointeurs de
     fonctions. \vspace{1em}
-    \newline {\bf Connaissance et pratique des commandes Unix ou
+    \newline {\bf Connaissance et pratique des commandes UNIX ou
     GNU/Linux}
     \newline Les personnes n'ayant pas ces connaissances doivent
     s'autoformer, par exemple en utilisant nos supports de formations
@@ -205,7 +205,7 @@ Session de 5 jours
   \item Effectuer des recherches dans les sources du noyau Linux :
     recherche de définitions C, de paramètres de configuration et d'autres
     informations.
-  \item En utilisant la ligne de commande Unix et des outils de
+  \item En utilisant la ligne de commande UNIX et des outils de
     navigation dans le code.
  \end{itemize}
 }
diff --git a/agenda/linux-kernel-online-agenda.tex b/agenda/linux-kernel-online-agenda.tex
index 8b506739..5101bd05 100644
--- a/agenda/linux-kernel-online-agenda.tex
+++ b/agenda/linux-kernel-online-agenda.tex
@@ -180,7 +180,7 @@ On-line seminar
   \item Making searches in the Linux kernel sources: looking for C
     definitions, for definitions of kernel configuration parameters,
     and for other kinds of information.
-  \item Using the Unix command line and then kernel source code
+  \item Using the UNIX command line and then kernel source code
     browsers.
  \end{itemize}
 }
diff --git a/agenda/yocto-agenda.tex b/agenda/yocto-agenda.tex
index 3daca9c8..23d65a40 100644
--- a/agenda/yocto-agenda.tex
+++ b/agenda/yocto-agenda.tex
@@ -63,7 +63,7 @@ Yocto Project and OpenEmbedded training\\
     {\bf Prerequisites} & {\bf Knowledge of embedded Linux} as covered
     in our embedded Linux training
     (\url{https://bootlin.com/training/embedded-linux/}) \vspace{1em}
-    \newline {\bf Knowledge and practice of Unix or GNU/Linux commands}
+    \newline {\bf Knowledge and practice of UNIX or GNU/Linux commands}
     \newline People lacking experience on this topic should get
     trained by themselves, for example with our freely available
     on-line slides:
diff --git a/agenda/yocto-fr-agenda.tex b/agenda/yocto-fr-agenda.tex
index 527e7ecc..5b7f54bd 100644
--- a/agenda/yocto-fr-agenda.tex
+++ b/agenda/yocto-fr-agenda.tex
@@ -63,7 +63,7 @@ Session de 3 jours
 
     {\bf Pré-requis} & {\bf Connaissance de Linux embarqué}, sujet couvert par
     notre formation Linux embarqué (\url{https://bootlin.com/training/embedded-linux/}) \vspace{1em}
-    \newline {\bf Connaissance et pratique des commandes Unix ou
+    \newline {\bf Connaissance et pratique des commandes UNIX ou
     GNU/Linux}
     \newline Les personnes n'ayant pas ces connaissances doivent
     s'autoformer, par exemple en utilisant nos supports de formations
diff --git a/agenda/yocto-online-agenda.tex b/agenda/yocto-online-agenda.tex
index 27fe7b02..7494b7fc 100644
--- a/agenda/yocto-online-agenda.tex
+++ b/agenda/yocto-online-agenda.tex
@@ -63,7 +63,7 @@ On-line seminar
     {\bf Prerequisites} & {\bf Familiarity with embedded Linux} as covered
     in our embedded Linux training
     (\url{https://bootlin.com/training/embedded-linux/}) \vspace{1em}
-    \newline {\bf Familiarity with Unix or GNU/Linux commands}
+    \newline {\bf Familiarity with UNIX or GNU/Linux commands}
     \newline People lacking experience on this topic may get
     trained by themselves, for example with our freely available
     on-line slides:
diff --git a/lab-data/embedded-linux/realtime/data/rttest.c b/lab-data/embedded-linux/realtime/data/rttest.c
index a7741340..d86e69f0 100644
--- a/lab-data/embedded-linux/realtime/data/rttest.c
+++ b/lab-data/embedded-linux/realtime/data/rttest.c
@@ -1,5 +1,5 @@
 /* Small program to test high-resolution timers
- * and scheduling latency in Unix / Linux
+ * and scheduling latency in UNIX / Linux
  *
  * Copyright (c) 2007-2008, Bootlin
  * https://bootlin.com/labs/solutions/cypfig/rttest.c
diff --git a/lab-data/embedded-linux/tinysystem/data/www/cgi-bin/upload.c b/lab-data/embedded-linux/tinysystem/data/www/cgi-bin/upload.c
index 247beff6..65d3f560 100644
--- a/lab-data/embedded-linux/tinysystem/data/www/cgi-bin/upload.c
+++ b/lab-data/embedded-linux/tinysystem/data/www/cgi-bin/upload.c
@@ -144,7 +144,7 @@ int MatchMask(char *String, char *Mask) {
 
 
 /* Translate the URL separator '/' into the directory separator ('/' for
-   Unix, '\\' for DOS), making a proper pathname. */
+   UNIX, '\\' for DOS), making a proper pathname. */
 void Url2Dir(char *Dir, char *Url) {
   char *p1;
   char *p2;
@@ -170,7 +170,7 @@ void Url2Dir(char *Dir, char *Url) {
    character is found from the needle string. The pointer to the found
    character is returned, or NULL if not found. This subroutine is
    designed to find a directory separator in a path, where the directory
-   separator can be '\\' (DOS) or '/' (Unix). */
+   separator can be '\\' (DOS) or '/' (UNIX). */
 char *strrchrs(char *haystack,char *needle) {
   char *h_here;
   char *n_here;
diff --git a/slides/autotools-advanced/autotools-advanced.tex b/slides/autotools-advanced/autotools-advanced.tex
index 358a2031..f91330fd 100644
--- a/slides/autotools-advanced/autotools-advanced.tex
+++ b/slides/autotools-advanced/autotools-advanced.tex
@@ -740,7 +740,7 @@ endif
 
 \begin{frame}{Building shared libraries}
   \begin{itemize}
-  \item Building shared libraries is very different between Unix
+  \item Building shared libraries is very different between UNIX
     variants
   \item A specific tool, called \code{libtool}, was created to
     abstract away the differences between platforms.
diff --git a/slides/autotools-usage/autotools-usage.tex b/slides/autotools-usage/autotools-usage.tex
index 4fd9da3f..c9957bbe 100644
--- a/slides/autotools-usage/autotools-usage.tex
+++ b/slides/autotools-usage/autotools-usage.tex
@@ -2,7 +2,7 @@
 
 \begin{frame}{Why do we need {\em autotools}?}
   \begin{itemize}
-  \item {\bf Portability} accross Unix systems, architectures, Linux
+  \item {\bf Portability} accross UNIX systems, architectures, Linux
     distributions
     \begin{itemize}
     \item Some C functions do not exist everywhere, or have different
diff --git a/slides/buildroot-rootfs/buildroot-rootfs.tex b/slides/buildroot-rootfs/buildroot-rootfs.tex
index 8c9dca64..a7711701 100644
--- a/slides/buildroot-rootfs/buildroot-rootfs.tex
+++ b/slides/buildroot-rootfs/buildroot-rootfs.tex
@@ -10,7 +10,7 @@
 
 \begin{frame}{Root filesystem skeleton}
   \begin{itemize}
-  \item The base of a Linux root filesystem: Unix directory hierarchy,
+  \item The base of a Linux root filesystem: UNIX directory hierarchy,
     a few configuration files and scripts in \code{/etc}. No programs
     or libraries.
   \item All target packages depend on the
@@ -259,7 +259,7 @@ BR2_ROOTFS_POST_BUILD_SCRIPT="board/myproject/post-build.sh"
 
 \begin{frame}[fragile]{Users table}
   \begin{itemize}
-  \item One may need to add specific Unix users and groups in addition
+  \item One may need to add specific UNIX users and groups in addition
     to the ones available in the default skeleton.
   \item \code{BR2_ROOTFS_USERS_TABLES} is a space-separated list of
     user tables.
diff --git a/slides/graphics-software/graphics-software.tex b/slides/graphics-software/graphics-software.tex
index 32d45176..ec521a5e 100644
--- a/slides/graphics-software/graphics-software.tex
+++ b/slides/graphics-software/graphics-software.tex
@@ -302,7 +302,7 @@ ret = ioctl(tty_fd, KDGKBMODE, &kbmode);
   \begin{itemize}
   \item However, the user might still want to switch VTs!
   \item So the display device must be \textbf{released/reacquired} for VT switching
-  \item Unix signals are used to notify the application, configured with:
+  \item UNIX signals are used to notify the application, configured with:
   \begin{minted}[fontsize=\small]{console}
 struct vt_mode vt_mode = { 0 };
 vt_mode.mode = VT_PROCESS;
@@ -395,7 +395,7 @@ ret = ioctl(fb_fd, FBIO_WAITFORVSYNC, &vsync);
 
 \begin{frame}{DRM devices}
   \begin{itemize}
-  \item Unix-style devices are identified with major/minor numbers
+  \item UNIX-style devices are identified with major/minor numbers
     \begin{itemize}
     \item More details in the \code{makedev} manpage, using \code{dev_t} type
     \item Minor/major can be retrieved with \code{stat/fstat}
diff --git a/slides/kernel-driver-development-processes/kernel-driver-development-processes.tex b/slides/kernel-driver-development-processes/kernel-driver-development-processes.tex
index e0d7ee10..44379f08 100644
--- a/slides/kernel-driver-development-processes/kernel-driver-development-processes.tex
+++ b/slides/kernel-driver-development-processes/kernel-driver-development-processes.tex
@@ -7,7 +7,7 @@
   \begin{itemize}
   \item Confusion about the terms \emph{process}, \emph{thread} and
     \emph{task}
-  \item In Unix, a process is created using \code{fork()} and is
+  \item In UNIX, a process is created using \code{fork()} and is
     composed of
     \begin{itemize}
     \item An address space, which contains the program code, data,
diff --git a/slides/kernel-source-code-drivers/kernel-source-code-drivers.tex b/slides/kernel-source-code-drivers/kernel-source-code-drivers.tex
index e0d2fde5..72472533 100644
--- a/slides/kernel-source-code-drivers/kernel-source-code-drivers.tex
+++ b/slides/kernel-source-code-drivers/kernel-source-code-drivers.tex
@@ -3,8 +3,8 @@
 \begin{frame}
   \frametitle{Programming language}
   \begin{itemize}
-  \item Implemented in C like all Unix systems. (C was created to
-    implement the first Unix systems)
+  \item Implemented in C like all UNIX systems. (C was created to
+    implement the first UNIX systems)
   \item A little Assembly is used too:
     \begin{itemize}
     \item CPU and machine initialization, exceptions
diff --git a/slides/sysdev-application-development/sysdev-application-development.tex b/slides/sysdev-application-development/sysdev-application-development.tex
index dfd95bf3..64983e8d 100644
--- a/slides/sysdev-application-development/sysdev-application-development.tex
+++ b/slides/sysdev-application-development/sysdev-application-development.tex
@@ -175,7 +175,7 @@
       Wind River, Zend, Computer Associates...).
     \item Free Software license (Eclipse Public License). Incompatible
       with the GPL.
-    \item Supported platforms: GNU/Linux, Unix, Windows
+    \item Supported platforms: GNU/Linux, UNIX, Windows
     \end{itemize}
     Extremely popular: created a lot of attraction.
     \column{0.2\textwidth}
diff --git a/slides/sysdev-block-filesystems/sysdev-block-filesystems.tex b/slides/sysdev-block-filesystems/sysdev-block-filesystems.tex
index bed174a1..c8018086 100644
--- a/slides/sysdev-block-filesystems/sysdev-block-filesystems.tex
+++ b/slides/sysdev-block-filesystems/sysdev-block-filesystems.tex
@@ -149,7 +149,7 @@ major minor #blocks name
 \end{frame}
 
 \begin{frame}
-  \frametitle{Other journaled Linux/Unix filesystems}
+  \frametitle{Other journaled Linux/UNIX filesystems}
   \begin{itemize}
   \item \code{btrfs}, intended to become the next standard filesystem
     for Linux. Integrates numerous features: data checksuming,
diff --git a/slides/sysdev-busybox/sysdev-busybox.tex b/slides/sysdev-busybox/sysdev-busybox.tex
index ec4c17ab..d093447a 100644
--- a/slides/sysdev-busybox/sysdev-busybox.tex
+++ b/slides/sysdev-busybox/sysdev-busybox.tex
@@ -29,7 +29,7 @@
 \begin{frame}
   \frametitle{General purpose toolbox: BusyBox}
   \begin{itemize}
-  \item Rewrite of many useful Unix command line utilities
+  \item Rewrite of many useful UNIX command line utilities
     \begin{itemize}
     \item Created in 1995 to implement a rescue and installer
      system for Debian, fitting in a single floppy disk.
@@ -186,7 +186,7 @@ yes, zcat, zcip}
     \code{export PATH=$HOME/x-tools/arm-unknown-linux-uclibcgnueabi/bin:$PATH}
   \item Compile BusyBox:\\
     \code{make}
-  \item Install it (this creates a Unix directory structure symbolic
+  \item Install it (this creates a UNIX directory structure symbolic
     links to the \code{busybox} executable):\\
     \code{make install}
   \end{itemize}
diff --git a/slides/sysdev-device-files/sysdev-device-files.tex b/slides/sysdev-device-files/sysdev-device-files.tex
index 9695b61d..f191d00d 100644
--- a/slides/sysdev-device-files/sysdev-device-files.tex
+++ b/slides/sysdev-device-files/sysdev-device-files.tex
@@ -1,7 +1,7 @@
 \begin{frame}
   \frametitle{Devices: everything is a file}
   \begin{itemize}
-  \item A very important Unix design decision was to represent most
+  \item A very important UNIX design decision was to represent most
     {\em system objects} as files
   \item It allows applications to manipulate all {\em system objects} with
     the normal file API (\code{open}, \code{read}, \code{write},
diff --git a/slides/sysdev-embedded-linux/sysdev-embedded-linux.tex b/slides/sysdev-embedded-linux/sysdev-embedded-linux.tex
index 74af2529..c811499a 100644
--- a/slides/sysdev-embedded-linux/sysdev-embedded-linux.tex
+++ b/slides/sysdev-embedded-linux/sysdev-embedded-linux.tex
@@ -845,7 +845,7 @@ met:
       \code{/usr/lib}, \code{/usr/share}, \code{/usr/sbin},
       \code{/var}, \code{/sbin}
     \item A set of basic utilities, providing at least the \code{init}
-      program, a shell and other traditional Unix command line
+      program, a shell and other traditional UNIX command line
       tools. This is usually provided by {\em Busybox}
     \item The C library and the related libraries (thread, math, etc.)
       installed in \code{/lib}
@@ -1287,7 +1287,7 @@ config BR2_PACKAGE_GQVIEW
         bool "gqview"
         depends on BR2_PACKAGE_LIBGTK2
         help
-          GQview is an image viewer for Unix operating systems
+          GQview is an image viewer for UNIX operating systems
 
           http://prdownloads.sourceforge.net/gqview
 \end{verbatim}
diff --git a/slides/sysdev-intro/sysdev-intro.tex b/slides/sysdev-intro/sysdev-intro.tex
index 49dc0b63..dff41f8b 100644
--- a/slides/sysdev-intro/sysdev-intro.tex
+++ b/slides/sysdev-intro/sysdev-intro.tex
@@ -6,7 +6,7 @@
   \item 1983, Richard Stallman, {\bf GNU project} and the {\bf free
       software} concept.  Beginning of the development of {\em gcc},
     {\em gdb}, {\em glibc} and other important tools
-  \item 1991, Linus Torvalds, {\bf Linux kernel project}, a Unix-like
+  \item 1991, Linus Torvalds, {\bf Linux kernel project}, a UNIX-like
     operating system kernel. Together with GNU software and many other
     open-source components: a completely free operating system,
     GNU/Linux
diff --git a/slides/sysdev-realtime/sysdev-realtime.tex b/slides/sysdev-realtime/sysdev-realtime.tex
index c75fc451..1bcd3c12 100644
--- a/slides/sysdev-realtime/sysdev-realtime.tex
+++ b/slides/sysdev-realtime/sysdev-realtime.tex
@@ -23,7 +23,7 @@
 \begin{frame}
   \frametitle{Embedded Linux and real time}
   \begin{itemize}
-  \item Linux is an operating system part of the large Unix family
+  \item Linux is an operating system part of the large UNIX family
   \item It was originally designed as a time-sharing system
     \begin{itemize}
     \item The main goal was to get the best throughput from the
@@ -557,7 +557,7 @@
   \frametitle{Process, thread?}
   \begin{itemize}
   \item Confusion about the terms {\em process}, {\em thread} and {\em task}
-  \item In Unix, a process is created using \code{fork()} and is composed of
+  \item In UNIX, a process is created using \code{fork()} and is composed of
     \begin{itemize}
     \item An address space, which contains the program code, data, stack, shared
       libraries, etc.
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 cf20fbaf..5266beb5 100644
--- a/slides/sysdev-root-filesystem-contents/sysdev-root-filesystem-contents.tex
+++ b/slides/sysdev-root-filesystem-contents/sysdev-root-filesystem-contents.tex
@@ -58,7 +58,7 @@
     and basic libraries in \code{/lib}
   \item All other programs are installed in \code{/usr/bin} and
     \code{/usr/sbin} and all other libraries in \code{/usr/lib}
-  \item In the past, on Unix systems, \code{/usr} was very often
+  \item In the past, on UNIX systems, \code{/usr} was very often
     mounted over the network, through NFS
   \item In order to allow the system to boot when the network was
     down, some binaries and libraries are stored in \code{/bin},
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 8d6e030d..187b12ee 100644
--- a/slides/sysdev-root-filesystem-minimal/sysdev-root-filesystem-minimal.tex
+++ b/slides/sysdev-root-filesystem-minimal/sysdev-root-filesystem-minimal.tex
@@ -21,7 +21,7 @@
     \end{itemize}
   \item A shell, to implement scripts, automate tasks, and allow a user
         to interact with the system
-  \item Basic Unix executables, for use in system scripts or in
+  \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.
   \item These basic components have to be integrated into the root
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 9f28d452..242746b8 100644
--- a/slides/sysdev-root-filesystem-principles/sysdev-root-filesystem-principles.tex
+++ b/slides/sysdev-root-filesystem-principles/sysdev-root-filesystem-principles.tex
@@ -6,7 +6,7 @@
   \item Filesystems are used to organize data in directories and files
     on storage devices or on the network. The directories and files
     are organized as a hierarchy
-  \item In Unix systems, applications and users see a {\bf single
+  \item In UNIX systems, applications and users see a {\bf single
       global hierarchy} of files and directories, which can be
     composed of several filesystems.
   \item Filesystems are {\bf mounted} in a specific location in this




More information about the training-materials-updates mailing list