Hi, > I'm having trouble finding a good HOWTO for xorriso. There are examples at the end of the man pages. Online: https://www.gnu.org/software/xorriso/man_1_xorriso.html#EXAMPLES https://www.gnu.org/software/xorriso/man_1_xorrisofs.html#EXAMPLES https://www.gnu.org/software/xorriso/man_1_xorrecord.html#EXAMPLES > Most of the examples use the "-as-cdrecord" option. > Is that necessary to burn an ISO? The second and third link above describe the emulation modes which are intended for existing scripts which use the older programs mkisofs and cdrecord. xorriso -as cdrecord is not only for legacy scripts but also covers the use case of burning a readily prepared ISO 9660 image onto optical media. Your goal of archiving / backing up a collection of data files from your hard disk can be achieved by a pipe made of xorriso -as mkisofs and xorriso -as cdrecord. But xorriso's native command set serves the same purpose by a single program run. My proposed example runs for multi-layer BD-R will create an ISO 9660 filesystem directly on the -outdev drive. The BD-R medium will stay appendable. Further write runs to the same medium will have to use -dev instead of -outdev, so that the existing ISO directory tree gets loaded as base for the new session. (You need to take care that -for_backup comes before -dev, so that the MD5s of the existing data files get loaded. It was didactically suboptimal to show it in my proposals after -outdev.) If you want to close the medium to prevent further writing, add command -close "on" to the xorriso run: xorriso -for_backup \ -outdev /dev/sr0 \ -close on \ -map "$dir_with_pics1" /pics1 \ -map "$dir_with_pics2" /pics2 ----------------------------------------------------------------------- MD5 checksums will be recorded due to command -for_backup. The overall session can be verified by a run of xorriso -for_backup -indev /dev/sr0 -check_media -- This should report messages like: xorriso : UPDATE : Found matching MD5 superblock tag: start=32 size=18 ... xorriso : UPDATE : Found matching MD5 tree tag: start=32 size=10640 ... xorriso : UPDATE : Found matching MD5 session tag: start=32 size=2112019 If a mismatch is reported like xorriso : WARNING : Found NON-MATCHING MD5 session tag: start=32 size=2112019 but the directory tree is still ok, then you may look for damaged files by xorriso -for_backup -indev /dev/sr0 -check_md5_r sorry / -- which then reports something like MD5 MISMATCH: '...path.of.damaged.file.in.the.iso...' hopefully not about too many or too important files. 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
