[FE training-materials-updates] Tinysystem lab: warn about NFS client update delay

[Michael Opdenacker]

Repository : git://git.free-electrons.com/training-materials.git

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

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

commit 265f9f12a02758f2fc1f6e6abf2fd405c1d68de5
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Wed Dec 10 12:10:38 2014 +0100

    Tinysystem lab: warn about NFS client update delay
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at free-electrons.com>


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

265f9f12a02758f2fc1f6e6abf2fd405c1d68de5
 labs/sysdev-tinysystem/sysdev-tinysystem.tex | 12 +++++++++---
 1 file changed, 9 insertions(+), 3 deletions(-)

diff --git a/labs/sysdev-tinysystem/sysdev-tinysystem.tex b/labs/sysdev-tinysystem/sysdev-tinysystem.tex
index 9591d83..6ef534d 100644
--- a/labs/sysdev-tinysystem/sysdev-tinysystem.tex
+++ b/labs/sysdev-tinysystem/sysdev-tinysystem.tex
@@ -215,9 +215,15 @@ memento sheet), look for this file in the toolchain install directory,
 and copy it to the \code{lib/} directory on the target.
 
 Then, running the executable again and see that the loader executes
-and finds out which shared libraries are missing. Similarly, find
-these libraries in the toolchain and copy them to \code{lib/} on the
-target.
+and finds out which shared libraries are missing.
+
+If you still get the same error message, work, just try again a
+few seconds later.  Such a delay can be needed because the NFS
+client can take a little time (at most 30-60 seconds) before
+seeing the changes made on the NFS server.
+
+Similarly, find the missing libraries in the toolchain and copy
+them to \code{lib/} on the target.
 
 Once the small test program works, we are going to recompile Busybox
 without the static compilation option, so that Busybox takes