[FE training-materials-updates] labs/sysdev-flash-filesystem: remove resizing

[Thomas Petazzoni]

Repository : git://git.free-electrons.com/training-materials.git
On branch  : master
Link       : http://git.free-electrons.com/training-materials/commit/?id=f19129e4086954ba298c32bf42af9c0a6dbed81b

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

commit f19129e4086954ba298c32bf42af9c0a6dbed81b
Author: Thomas Petazzoni <thomas.petazzoni at free-electrons.com>
Date:   Tue Sep 20 13:54:50 2016 +0200

    labs/sysdev-flash-filesystem: remove resizing
    
    The resizing "Going further" step doesn't work, as you can resize the
    volume but not the filesystem, which makes the whole exercise moot. So
    kill it with fire.
    
    Signed-off-by: Thomas Petazzoni <thomas.petazzoni at free-electrons.com>


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

f19129e4086954ba298c32bf42af9c0a6dbed81b
 .../sysdev-flash-filesystems.tex                   | 23 ----------------------
 1 file changed, 23 deletions(-)

diff --git a/labs/sysdev-flash-filesystems/sysdev-flash-filesystems.tex b/labs/sysdev-flash-filesystems/sysdev-flash-filesystems.tex
index 51b115a..51e2871 100644
--- a/labs/sysdev-flash-filesystems/sysdev-flash-filesystems.tex
+++ b/labs/sysdev-flash-filesystems/sysdev-flash-filesystems.tex
@@ -201,29 +201,6 @@ data using the web server.
 
 \section{Going further}
 
-\subsection{Resizing an existing volume and creating a new one}
-
-In some cases you might need to adapt your NAND partitioning without
-re-flashing everything. Thanks to UBI this is possible.
-
-First, from Linux, resize the \code{data} volume to consume 128 MiB.
-Check that this works as expected. However, you will notice that UBIFS
-is not able yet to take advantage of the new size. To do it, you would
-have to reflash this volume. 
-
-Next, create a new \code{log} volume of 16MiB. Mount this
-volume as a UBIFS filesystem and see what happens.
-
-Update your init script to mount the UBI \code{log} volume on \code{/var/log}.
-Reboot your system and check that the \code{log} is correcly mounted.
-
-% Hints:
-%
-%ubirsvol /dev/ubi0 -n 4 -s 128MiB
-%ubimkvol /dev/ubi0 -N log -s 16MiB
-%mount -t ubifs ubi0:log /var/log
-%
-
 \subsection{Using {\em squashfs} for the root filesystem}
 
 Root filesystems are often a sensitive part of your system, and you don't