diff --git a/README.md b/README.md
index 3fe92431..e43fcef3 100644
--- a/README.md
+++ b/README.md
@@ -1704,12 +1704,40 @@ If you need help please contact Matthias Jung.
 
 ### DRAMSys + GEM5 Log Collector Script
 
-Users can profit of running multiple simulations automatically with
-[gem5ilva](DRAMSys/library/resources/scripts/DRAMSylva/gem5ilva.sh).
+Users can profit of running multiple **DRAMSys + gem5 simulations**
+automatically with
+[gem5ilva](DRAMSys/library/resources/scripts/DRAMSylva/gem5ilva.sh) for **gem5
+syscall emulation (SE) mode** and
+[gem5ilva_fs](DRAMSys/library/resources/scripts/DRAMSylva/gem5ilva.sh) for
+**gem5 full system (FS) mode**.
+
+Normally you will have to push your changes before running the scripts. This
+approach makes it easier to track back what exactly was tested by the scripts.
+
+In the scripts there are variables to tell **git** where to get the source
+code from, user name, **branch**, etc. The variable are:
+
+```bash
+# Git info.
+git_user="$USER"
+git_branch="master"
+git_url="git.eit.uni-kl.de:ems/astdm/dram.sys.git"
+git_url_https="git.eit.uni-kl.de/ems/astdm/dram.sys.git"
+```
+
+Nevertheless, for some cases, you may want to have gem5 files out of the main
+repository (usually because they are too big to be added to the repository).
+
+For those cases uncomment and properly set the variable
+**external_inifile_path** in
+[gem5ilva_fs](DRAMSys/library/resources/scripts/DRAMSylva/gem5ilva.sh).
+
+This will allow you to use a gem5 **config.ini** file external to the
+repository. Note, however, that in this case it is up to you to keep track of
+your simulation files.
 
 ### Notes for [Elwetritsch](https://elwe.rhrk.uni-kl.de/) Users
 
-
 Firstly, take a look at [High Performance Computing at the TU
 Kaiserslautern](https://elwe.rhrk.uni-kl.de/).