[bootlin/training-materials updates] master: Correct/clarify block fs explanations (13c09e13)

[Michael Opdenacker]

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

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

commit 13c09e1375071c44db0bb00e3ce518926dd320fe
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date:   Mon Mar 1 11:15:08 2021 +0100

    Correct/clarify block fs explanations
    
    - Not true to say that without journaling, a block filesystem
      will be corrupted after a crash (thanks to Thomas)
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>


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

13c09e1375071c44db0bb00e3ce518926dd320fe
 slides/sysdev-block-filesystems/sysdev-block-filesystems.tex | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/slides/sysdev-block-filesystems/sysdev-block-filesystems.tex b/slides/sysdev-block-filesystems/sysdev-block-filesystems.tex
index 4f32153d..2bd298ca 100644
--- a/slides/sysdev-block-filesystems/sysdev-block-filesystems.tex
+++ b/slides/sysdev-block-filesystems/sysdev-block-filesystems.tex
@@ -149,11 +149,10 @@ major minor #blocks name
     \begin{itemize}
     \item Thanks to the journal, the recovery at boot time is quick,
       since the operations in progress at the moment of the unclean
-      shutdown are clearly identified
+      shutdown are clearly identified. There's no need for a full
+      filesystem check.
     \item Does not mean that the latest writes made it to the storage:
       this depends on syncing the changes to the filesystem.
-    \item What matters is to avoid filesystem corruption and be able
-      to boot autonomously.
     \end{itemize}
     See \url{https://en.wikipedia.org/wiki/Journaling_file_system}
     for further details.
@@ -337,10 +336,11 @@ major minor #blocks name
     \item \code{-noappend}: re-create the image from scratch rather
       than appending to it
     \end{itemize}
-  \item Mounting a squashfs filesystem:
+  \item Examples mounting a squashfs filesystem:
     \begin{itemize}
-    \item \code{mount -o loop rootfs.sqfs /mnt} (filesystem image)
-    \item \code{mount /dev/<device> /mnt} (after copy to device)
+    \item Same way as for other block filesystems
+    \item \code{mount -o loop rootfs.sqfs /mnt} (filesystem image on the host)
+    \item \code{mount /dev/<device> /mnt} (on the target)
     \end{itemize}
   \end{itemize}
 \end{frame}