Hi, > But when I add an output device to the image like > xorriso -indev test.iso \ > -boot_image any keep \ > -map "$file_or_tree_on_disk" "$path_in_iso" \ > -outdev test.iso > > Everything magically works. > Weird. Hm. This should yield the same result as -dev test.iso. I still get mount: /dev/loop0p1: can't read superblock if i let losetup create a partition device and try to mount it. It would be explainable if -indev was a different file than test.iso. Partition 1 would still be smaller than the ISO image. But with -indev not equal -outdev you'd created no add-on session with metadata after the end of the partition. So the metadata would sit at the partition start and the mount command does not yet run into an error. You would probably get problems with reading data file content from the end of the image. E.g. if you tar up the mounted ISO. tar cf - /mnt/iso | wc You can compare partition size and image size by xorriso -indev test.iso -report_system_area plain For me it reports after above run ISO image size/512 : 3768452 ... MBR partition table: N Status Type Start Blocks MBR partition : 1 0x80 0x00 0 3768320 So partition 1 is too small by 3768452 - 3768320 = 132 blocks of 512 bytes. With a larger add-on file this gap would grow more. Have a nice day :) Thomas _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
