summaryrefslogtreecommitdiff
path: root/en/using-d-i
diff options
context:
space:
mode:
Diffstat (limited to 'en/using-d-i')
-rw-r--r--en/using-d-i/modules/iso-scan.xml13
1 files changed, 11 insertions, 2 deletions
diff --git a/en/using-d-i/modules/iso-scan.xml b/en/using-d-i/modules/iso-scan.xml
index 926e44fb2..e3f6d8898 100644
--- a/en/using-d-i/modules/iso-scan.xml
+++ b/en/using-d-i/modules/iso-scan.xml
@@ -13,8 +13,8 @@ component <command>iso-scan</command> does exactly this.
</para><para>
At first, <command>iso-scan</command> automatically mounts all block
-devices (e.g. partitions) which have some known filesystem on them and
-sequentially searches for filenames ending with
+devices (e.g. partitions and logical volumes) which have some known
+filesystem on them and sequentially searches for filenames ending with
<filename>.iso</filename> (or <filename>.ISO</filename> for that
matter). Beware that the first attempt scans only files in the root
directory and in the first level of subdirectories (i.e. it finds
@@ -43,5 +43,14 @@ placed on a filesystem recognizable by &d-i;, and if it is not
corrupted (verify the checksum). Experienced Unix users could do this
without rebooting on the second console.
+</para><para>
+
+Note that the partition (or disk) hosting the ISO image can't be reused during the
+installation process as it will be in use by the installer. To work-around
+this, and provided that you have enough system memory, the installer can copy
+the ISO image into RAM before mounting it. This is controlled by the low
+priority <literal>iso-scan/copy_iso_to_ram</literal> debconf question (it is
+only asked if the memory requirement is met).
+
</para>
</sect3>