Probably problem with ISO image debian-8.6.0-arm64-netinst.iso
Looking at debian-8.6.0-arm64-netinst.iso using ISOBuster.
In the Primary Volume Descriptor file hierarchy, there's a file
/FIRMWARE/FIRMWARE.DEB;1 (size 0).
In the Supplementary Volume Descriptor (Joliet), that file isn't there.
The directory /firmware is present, but it is empty.
Assuming the Rockridge name hierarchy is anything to go by, there should
probably be a /firmware/firmware-linux-free_3.3_all.deb file there.
(Although it seems weird that it should be empty ...)
There *is* a file of that basename+extension in
\pool\main\f\firmware-free\firmware-linux-free_3.3_all.deb, and it is
not empty. Might be a coincidence, might be relevant.
The Primary Volume Descriptor directory /FIRMWARE is at logical block
117. Manual examination confirms that there is a FIRMWARE.DEB;1 there,
and also that it has RockRidge information (as stated above)
The Joliet directory Firmware is at logical block 549. Manual
inspection shows only the ISO 9660 equivalents of . and .. entries, but
nothing more: that directory is empty.
So ... Debian CD production may have some kind of problem. In this
case, the Joliet part of the file tree does not contain the file that
the main file tree does.
I have no idea how this affects anything -- but it seems weird.
I was using this ISO image (the smallest ISO image in 8.6.0) to test a
program for hashing files, and when I compared results against that from
md5sum I found that I was hashing a file that did not turn up in the
md5sum list. My program looked at the primary volume descriptor list,
while the operating system I used for md5sum apparently used the Joliet
file tree.
I'm not on this mailing list, so if you have nay questions, or if I can
add any clarifications, please send to my mail address.
best wishes,
/AThulin
Reply to: