Hi, Ian Grant wrote: > This is an empty filesystem AFAICS. It doesn't even have a boot loader on > it. The sha256sum of the file I got > is 472404f74ef4bfd6b1a30d003cce7037fa6a16d2c11dc3bddeaf1b7e2020639e
I got very different results: $ wget https://dl.t2sde.org/binary/2025/t2-25.4-x86-64-musl-base-wayland-musl-clang-nocona.iso ... 2025-05-27 13:38:21 (6.84 MB/s) - 't2-25.4-x86-64-musl-base-wayland-musl-clang-nocona.iso' saved [1711742976/1711742976] $ x=t2-25.4-x86-64-musl-base-wayland-musl-clang-nocona.iso $ sha256sum $x 446c919cd61655905bcaed2eadd04bcabf14f8cec2f760692bf3b8cb4902640b t2-25.4-x86-64-musl-base-wayland-musl-clang-nocona.iso $ xorriso -indev $x -report_el_torito plain -report_system_area plain ... El Torito images : N Pltf B Emul Ld_seg Hdpt Ldsiz LBA El Torito boot img : 1 BIOS y none 0x0000 0x00 4 785 El Torito boot img : 2 UEFI y none 0x0000 0x00 2880 834942 El Torito img path : 1 /boot/grub/i386-pc/eltorito.img El Torito img opts : 1 boot-info-table grub2-boot-info El Torito img blks : 2 720 ... System area summary: MBR grub2-mbr cyl-align-off ... MBR partition table: N Status Type Start Blocks MBR partition : 1 0x80 0x83 64 3339704 MBR partition : 2 0x00 0xef 3339768 2880 ... So the ISO is prepared to boot from optical medium and from USB stick via legacy BIOS and UEFI. Boot loader is obviously GRUB. The EFI system partition is not a data file in the ISO filesystem but rather an appended partition. $ sudo mount t2-25.4-x86-64-musl-base-wayland-musl-clang-nocona.iso /mnt/iso mount: /dev/loop0 is write-protected, mounting read-only $ du -s /mnt/iso 1665076 /mnt/iso $ find /mnt/iso | wc -l 3819 $ Lots of data and 3819 files or directories are represented by Linux. Have a nice day :) Thomas
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [email protected] with a subject of: unsubscribe t2
