[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#939071: 6.4 Load Missing Firmware should mention unpacking zip/tar



Hi Joey, 

Dixit Joey Hess, le 31/08/2019 :

>The instructions assume that the user will unpack the zip or tarball
>they download, but they don't say to do so. 
The section you mention says
(https://www.debian.org/releases/buster/amd64/ch06s04.en.html) :
>Just download the tarball or zip file for the correct release and
>unpack it to the file system on the medium.
…unpack is here !

>There's an implicit
>assumption that the user won't consider firmware.zip to be a
>firmware file. Also that the user knows how to extract zip files or
>tarballs or what any of these file types are.
I don't think the installation guide must cover the "how to use a zip
archive" case, but it can maybe suggest to use an external soft and
that firmaware files are *.deb.

For example, in installation-guide/en/using-d-i/loading-firmware.xml:
[...] and unpack it to
-the file system on the medium.
+the file system on the medium. Use an appropriate software like
+7-Zip (https://www.7-zip.org/)
+or tar (https://www.gnu.org/software/tar/) to obtain a list of *.deb
+files to put in the <filename>/firmware</filename> directory mentioned.
[...]
It is also possible to copy individual firmware files to the medium. Loose
firmware could be obtained for example from an already installed system or
-from a hardware vendor.
+from a hardware vendor. These files are generally binary files and
+named *.bin.

Baptiste


diff --git a/en/using-d-i/loading-firmware.xml b/en/using-d-i/loading-firmware.xml
index ff75bd668..141a44e14 100644
--- a/en/using-d-i/loading-firmware.xml
+++ b/en/using-d-i/loading-firmware.xml
@@ -77,7 +77,10 @@ available from:
 </itemizedlist>
 
 Just download the tarball or zip file for the correct release and unpack it to
-the file system on the medium.
+the file system on the medium. Use an appropriate software like
+7-Zip (https://www.7-zip.org/)
+or tar (https://www.gnu.org/software/tar/) to obtain a list of *.deb
+files to put in the <filename>/firmware</filename> directory mentioned.
 
 </para><para>
 
@@ -97,7 +100,8 @@ non-firmware packages:
 
 It is also possible to copy individual firmware files to the medium. Loose
 firmware could be obtained for example from an already installed system or
-from a hardware vendor.
+from a hardware vendor. These files are generally binary files and
+named *.bin.
 
 </para>
   </sect2>

Attachment: pgpdvY80dbA9a.pgp
Description: Signature digitale OpenPGP


Reply to: