1XORRISOFS(1) General Commands Manual XORRISOFS(1)
2
6 xorrisofs - Emulation of ISO 9660 program mkisofs by program xorriso
7
9 xorrisofs [ options ] [-o filename ] pathspec [pathspecs ...]
10
12 xorrisofs produces Rock Ridge enhanced ISO 9660 filesystems and add-on
13 sessions to such filesystems. Optionally it can produce Joliet
14 directory trees too.
15 xorrisofs understands options of program mkisofs from cdrtools by Joerg
17 Schilling. Its implementation is part of program xorriso which shares
18 no source code with cdrtools.
19 ISO 9660, Rock Ridge, Joliet, HFS+:
21 ISO 9660 (aka ECMA-119) is a read-only filesystem that is mainly used
22 for optical media CD, DVD, BD, but may also reside on other storage
23 devices like disk files, USB sticks or disk partitions. It is widely
24 readable by many operating systems and by boot facilities of personal
25 computers.
26 ISO 9660 describes directories and data files by very restricted
27 filenames with no distinction of upper case and lower case. Its
28 metadata do not comply to fundamental POSIX specifications.
29 Rock Ridge is the name of a set of additional information which enhance
30 an ISO 9660 filesystem so that it can represent a POSIX compliant
31 filesystem with ownership, access permissions, symbolic links, and
32 other attributes. Rock Ridge allows filenames of up to 255 bytes and
33 paths of up to 1024 bytes.
34 xorrisofs produces Rock Ridge information by default. It is strongly
35 discouraged to disable this feature.
36 Joliet is the name of an additional directory tree which provides
37 filenames up to 64 characters encoded as UTF-16. A Joliet tree is
38 mainly interesting for reading the ISO image by operating systems of
39 Microsoft Corporation. Production of this directory tree may be
40 enabled by option -J.
41 ISO 9660:1999 is the name of an additional directory tree which
42 provides longer filenames. It allows single file names to have up to
43 207 characters. It might be of use with some older computer system
44 boot facilities which read neither Rock Ridge nor Joliet but need
45 longer filenames nevertheless. Production of this directory tree may
46 be enabled by option -iso-level 4.
47 HFS+ is the name of a filesystem which is normally used for writing and
48 reading on hard disks and similar devices. It is possible to embed a
49 HFS+ partition into the emerging ISO 9660 image and to mark it by Apple
50 Partition Map entries. This interferes with options which copy data
51 into the first 32 KiB of the ISO image, like -G or -isohybrid-mbr. See
52 option -hfsplus.
53 The main purpose for having an embedded HFS+ partition is booting of
54 certain models of Apple computers.
55 Inserting files into the ISO image:
57 xorrisofs deals with two kinds of file addresses:
58 disk_path is a path to an object in the local filesystem tree.
59 iso_rr_path is the Rock Ridge address of a file object in the ISO
60 image. If no Rock Ridge information shall be stored in an emerging
61 ISO, then the names will get mapped to ISO 9660 names of limited length
62 and character set.
63 A program argument is handled as a pathspec, if it is not recognized as
65 original mkisofs option or additional xorrisofs option. A pathspec
66 depicts an input file object by a disk_path. If option -graft-points
67 is not present, then the behavior depends on the file type of
68 disk_path. Directories get merged with the /-directory of the ISO
69 image. Files of other types get copied into the /-directory.
70 If -graft-points is present then each pathspec gets split at the first
71 occurrence of the =-character. The part before the = is taken as
72 target, i.e. the iso_rr_path for the file object in the ISO image. The
73 part after the first = is taken as source, i.e. the disk_path of the
74 input object.
75 It is possible to make =-characters part of the iso_rr_path by
76 preceding them with a \-character. The same must be done for
77 \-characters which shall be part of the iso_rr_path.
78 If the source part of the pathspec leads to a directory, then all files
80 underneath this directory get inserted into the image, too. It is
81 possible to exclude particular files from being inserted by help of
82 option -m.
83 In case that target already exists, the following rules apply:
84 Directories and other files may overwrite existing non-directories.
85 Directories get merged with existing directories. Non-directories may
86 not overwrite existing directories.
87 Relation to program xorriso:
89 xorrisofs is actually a command mode of program xorriso, which gets
90 entered either by xorriso command "-as mkisofs" or by starting the
91 program by one of the names "xorrisofs", "mkisofs", "genisoimage", or
92 "genisofs".
93 This command mode can be left by argument "--" which leads to generic
94 xorriso command mode. See man xorriso for its description.
95 xorriso performs image reading and writing by help of libburn, which is
97 mainly intended for optical drives, but also operates on all POSIX file
98 types except directories.
99 The program messages call any image file a "drive". File types which
100 are not supported for reading are reported as "blank". The reported
101 free media space may be quite fictional.
102 Nevertheless xorrisofs does not operate directly on optical drives, but
103 rather forces libburn to regard them as general device files. So for
104 writing of sequential optical media (CD, DVD-R, DVD+R, BD-R) one will
105 have to use a burn program. E.g the cdrecord emulation of xorriso. See
106 EXAMPLES.
107
110 Image loading:
111 The following options control loading of an existing ISO image for the
113 purpose of preparing a suitable add-on session. If they are missing
114 then a new image is composed from scratch.
115 -M disk_path
117 Set the path from which to load the existing ISO image directory
118 tree on which to base the upcomming directory tree as add-on
119 session. The path must lead to a random-access readable file
120 object. On GNU/Linux: regular data files or block device files.
121 A special kind of pseudo disk_path has the form
122 "/dev/fd/"number. It depicts the open file descriptor with the
123 given number, regardless whether the operating system supports
124 this feature by file nodes in /dev/fd or not. E.g. /dev/fd/3 is
125 file descriptor 3 which was opened by the program that later
126 started xorriso.
127 -prev-session disk_path
129 Alias of -M.
130 -dev disk_path
132 Alias of -M.
133 -C last_session_start,next_writeable_address
135 Set the 2 KiB block address last_session_start from where to
136 read the ISO image out of the file given by option -M.
137 Separated by a comma, set the next_writeable_address to which
138 the add-on session will finally be written. Decisive is actually
139 the block address which the intended readers will have to use as
140 superblock address on the intended medium.
141 Both values can be inquired from optical media by help of burn
142 programs and cdrecord option -msinfo. xorriso itself can obtain
143 it in its cdrecord emulation. Do not let it load the drive, but
144 rather do this manually or by a program like dd which reads a
145 few bytes. Only then it is sure that the device driver knows the
146 true readable size of the medium.
147 dd if=/dev/... count=1 >/dev/null 2>&1
148 values=$(xorriso -as cdrecord dev=/dev/... -msinfo)
149 echo $values
150 Option -C may be used without option -M to create an ISO image
151 from scratch and prepare it for being finally written to a block
152 address other than 0. Parameter last_session_start must then be
153 set to 0.
154 -cdrecord-params last_session_start,next_writeable_address
156 Alias of -C.
157 Settings for file insertion:
159 -path-list disk_path
161 Read pathspecs line-by-line from disk_file and insert the
162 depicted file objects into the ISO image. If disk_path is "-"
163 then read the pathspecs from standard input.
164 --quoted_path_list disk_path
166 Like option -path-list but reading quoted words rather than
167 plain lines. Whitespace outside of quotes will be discarded. On
168 the other hand it is possible to represent pathspecs which
169 contain newline characters.
170 The double quotation mark " and the single quotation mark ' can
171 be used to enclose whitespace and make it part of pathspecs.
172 Each mark type can enclose the marks of the other type. A
173 trailing backslash \ outside quotations or an open quotation
174 cause the next input line to be appended.
175 -f
177 Resolve symbolic links on disk rather than storing them as
178 symbolic links in the ISO image.
179 -follow-links
181 Alias of -f.
182 -graft-points
184 Enable interpretation of input file pathspecs as combination of
185 iso_rr_path and disk_path, separated by a =-character.
186 -m disk_pattern
188 Exclude files from being inserted into the image. Silently
189 ignored are those files of which the disk_path matches the given
190 shell parser pattern. If no /-character is part of the pattern,
191 then it gets matched against the leaf name of the disk file.
192 It is possible to give more than one -m option.
193 -exclude
195 Alias of -m.
196 -x
198 Alias of -m.
199 -old-exclude
201 Alias of -m.
202 -exclude-list disk_path
204 Perform -m using each line out of file disk_path as argument
205 disk_pattern.
206 -z
208 Enable recognition and proper processing of zisofs compressed
209 files as produced by program mkzftree. These files will get
210 equipped with the necessary meta data so that a Linux kernel
211 will recognize them and deliver their content in uncompressed
212 form.
213 -transparent-compression
215 Alias of -z.
216 -root iso_rr_path
218 Insert all files under the given iso_rr_path. If option
219 -graft-points is given, then iso_rr_path is prepended to each
220 target part of a pathspec.
221 The default for -root is "/".
222 -old-root iso_rr_path
224 Enable incremental insertion of files into the loaded image.
225 The effective target and source addresses of given pathspecs get
226 compared whether the target already exists in the ISO image and
227 is still identical to the source on disk. Metadata in the ISO
228 image will get adjusted, if they differ from those on disk. New
229 files and files with changed content will get newly added.
230 Target files which do not exist in any of the according pathspec
231 sources will get removed from the ISO directory tree.
232 If the effective setting of -root differs from the iso_rr_path
233 given with -old-root, then the files underneath the -old-root
234 directory get cloned underneath the -root directory. Cloning
235 happens before file comparison.
236 --old-root-no-ino
238 Disable recording and use of disk inode numbers. If no disk
239 inode numbers are recorded, then option -old-root will have to
240 read disk file content and compare it with the MD5 checksum that
241 is recorded in the ISO image.
242 With recorded disk inode numbers and with credible ctime and
243 mtime, it is possible to detect potential changes in the content
244 without actually reading it. A loophole remains if multiple
245 different filesystems may get mounted at the same directory,
246 like it is habit with /mnt. In this case one has to use option
247 --old-root-devno or disable the inode number shortcut by
248 --old-root-no-ino.
249 --old-root-devno
251 Enable comparison of recorded device numbers together with
252 recorded inode numbers. This works only with good old stable
253 device numbers which get out of fashion, regrettably. If the
254 hard disk has a different device number after each reboot, then
255 this comparison will see all files as changed and thus prevent
256 any incremental size saving.
257 --old-root-no-md5
259 Disable recording and use of MD5 checksums for data file
260 content. If neither checksums and nor disk inode numbers are
261 recorded, then option -old-root will have to read ISO image file
262 content when comparing it with disk file content.
263 Settings for image production:
265 -o disk_path
267 Set the output file address for the emerging ISO image. If the
268 address exists as regular file, it will be truncated to length 0
269 when image production begins. It may not already exist as
270 directory. If it does not exist yet then its parent directory
271 must exist and a regular file will get created.
272 A special kind of pseudo disk_path has the form
273 "/dev/fd/"number. It depicts the open file descriptor with the
274 given number, regardless whether the operating system supports
275 this feature by file nodes in /dev/fd or not. E.g. /dev/fd/4 is
276 file descriptor 4 which was opened by the program that later
277 started xorriso.
278 Default is standard output (/dev/fd/1) which may also be set by
279 disk_path "-".
280 -output disk_path
282 Alias of -o.
283 --stdio_sync "on"|"off"|"end"|number
285 Set the number of bytes after which to force output to disk in
286 order to keep the memory from being clogged with lots of pending
287 data for slow devices. "on" is the same as "16m". Forced output
288 can be disabled by "off", or be delayed by "end" until all data
289 are produced. If a number is chosen, then it must be at least
290 64k.
291 The default with xorriso mkisofs emulation is --stdio_sync
292 "off".
293 xorriso uses an inner fifo buffer with default size 4 MiB. So
294 forcing the operating system i/o cache to disk does not
295 necessarily block the simultaneous production of more image
296 content.
297 --emul-toc
299 Write a second superblock with the first session into
300 random-access files. If further sessions get appended and the
301 first superblock gets updated, then the second superblock will
302 not be overwritten. So it is still possible to mount the first
303 session and to find the start blocks of the further sessions.
304 The price is 64 KiB extra space consumption. If
305 -partition_offset is non-zero, then it is 128 KiB plus twice the
306 partition setup.
307 --no-emul-toc
309 Do not write a second superblock with the first session into
310 random-access files.
311 This is the default.
312 --sort-weight weight_number iso_rr_path
314 Attribute a LBA weight number to regular files. If iso_rr_path
315 leads to a directory then all regular files underneath will get
316 the weight_number.
317 The weight_number may range from -2147483648 to 2147483647. The
318 higher it is, the lower will be the block address of the file
319 data in the emerging ISO image. Currently the El Torito boot
320 catalog has a hardcoded weight of 1 billion. Normally it should
321 occupy the block with the lowest possible address. Data files
322 get added or loaded with initial weight 0. Boot image files have
323 a default weight of 2.
324 --sort-weight-list disk_path
326 Read pairs of weight number and iso_rr_path from a file of the
327 local filesystem. Apply each pair like with --sort-weight.
328 Only the last --sort-weight-list or --sort-weight-patterns of a
329 xorrisofs run gets into effect.
330 The weight number is read from the start of the line. The
331 iso_rr_path part of an input line begins immediately after the
332 first blank or tab character of the line.
333 Notes for the case that this feature is used within a sequence
334 of generic xorriso commands (not an issue with a pure mkisofs
335 emulation run):
336 The addressed files must already be in the ISO image model when
337 you execute
338 -as mkisofs --sort-weight-list disk_path --
339 Several such commands may be used to apply more than one weight
340 file.
341 Data files which are loaded by -indev or -dev get a weight
342 between 1 and 2 exp 28 = 268,435,456, depending on their block
343 address. This shall keep them roughly in the same order if the
344 write method of modifying is applied.
345 --sort-weight-patterns disk_path
347 Like --sort-weight-list , but expanding the iso_rr_paths as
348 shell parser patterns and applying --sort-weight to each
349 matching file.
350 -dir-mode mode
352 Set the access permissions for all directories in the image to
353 the given mode which is either an octal number beginning with
354 "0" or a comma separated list of statements of the form
355 [ugoa]*[+-=][rwxst]* . E.g. ug=rx,a-rwx
356 -file-mode mode
358 Like -dir-mode but for all regular data files in the image.
359 -pad
361 Add 300 KiB to the end of the produced ISO image. This
362 circumvents possible read errors from ISO images which have been
363 written to CD media in TAO mode. The additional bytes are
364 claimed as part of the ISO image if not --emul-toc is given.
365 Option -pad is the default.
366 -no-pad
368 Disable padding of 300 KiB to the end of the produced ISO image.
369 This is safe if the image is not meant to be written on CD or if
370 it gets written to CD as only track in write mode SAO.
371 --old-empty
373 Use the old way of of giving block addresses in the range of
374 [0,31] to files with no own data content. The new way is to have
375 a dedicated block to which all such files will point.
376 Settings for standards compliance:
378 -iso-level number
380 Specify the ISO 9660 version which defines the limitations of
381 file naming and data file size. The naming restrictions do not
382 apply to the Rock Ridge names but only to the low-level ISO 9660
383 names. There are three conformance levels:
384 Level 1 allows ISO names of the form 8.3 and file size up to 4
385 GiB - 1.
386 Level 2 allows ISO names with up to 32 characters and file size
387 up to 4 GiB - 1.
388 Level 3 allows ISO names with up to 32 characters and file size
389 of up to 400 GiB - 200 KiB. (This size limitation is set by the
390 xorriso implementation and not by ISO 9660 which would allow
391 nearly 8 TiB.)
392 Pseudo-level 4 enables production of an additional ISO 9660:1999
393 directory tree.
394 -disallow_dir_id_ext
396 Do not follow a bad habit of mkisofs which allows dots in the
397 ISO names of directories. On the other hand, some bootable
398 GNU/Linux images depend on this bad habit.
399 -U
401 This option allows ISO file names without dot and up to 37
402 characters, ISO file paths longer than 255 characters, and all
403 ASCII characters in file names. Further it omits the semicolon
404 and the version numbers at the end of ISO names.
405 This all violates ISO 9660 specs.
406 -untranslated-filenames
408 Alias of -U.
409 -untranslated_name_len number
411 Allow ISO file names up to the given number of characters
412 without any character conversion. The maximum number is 96. If
413 a file name has more characters, then image production will fail
414 deliberately.
415 This violates ISO 9660 specs.
416 -allow-lowercase
418 Allow lowercase character in ISO file names.
419 This violates ISO 9660 specs.
420 -relaxed-filenames
422 Allow nearly all 7-bit characters in ISO file names. Not
423 allowed are 0x0 and '/'. If not option -allow-lowercase is
424 given, then lowercase letters get converted to uppercase.
425 This violates ISO 9660 specs.
426 -d
428 Do not add trailing dot to ISO file names without dot.
429 This violates ISO 9660 specs.
430 -omit-period
432 Alias of -d.
433 -l
435 Allow up to 31 characters in ISO file names.
436 -full-iso9660-filenames
438 Alias of -l.
439 -max-iso9660-filenames
441 Allow up to 37 characters in ISO file names.
442 This violates ISO 9660 specs.
443 -N
445 Omit the semicolon and the version numbers at the end of ISO
446 names.
447 This violates ISO 9660 specs.
448 -omit-version-number
450 Alias of -N.
451 Settings for standards extensions:
453 -R
455 With mkisofs this option enables Rock Ridge extensions.
456 xorrisofs produces them by default. It is strongly discouraged
457 to disable them by option --norock.
458 -rock
460 Alias of -R.
461 -r
463 Enable Rock Ridge and set user and group id of all files in the
464 ISO image to 0. Grant r-permissions to all. Deny all
465 w-permissions. If any x-permission is set, grant x-permission
466 to all. Remove s-bit and t-bit.
467 These attribute changes stay delayed until mkisofs emulation
468 ends. Within the same -as mkisofs emulation command they can be
469 revoked by a subsequent option --norock. For compatibility
470 reasons, option -R does not revoke the changes ordered by -r.
471 -rational-rock
473 Alias of -r.
474 --norock
476 This option disables the production of Rock Ridge extensions for
477 the ISO 9660 file objects. The multi-session capabilities of
478 xorrisofs depend much on the naming fidelity of Rock Ridge. So
479 it is strongly discouraged to disable it by this option, except
480 for the special use case to revoke the effect of -r by:
481 --norock -R
482 --set_all_file_dates timestring
484 Set mtime, atime, and ctime of all files and directories to the
485 given time.
486 Valid timestring formats are: 'Nov 8 14:51:13 CET 2007',
487 110814512007.13, 2007110814511300. See also --modification-date=
488 and man xorriso, Examples of input timestrings.
489 If the timestring is "set_to_mtime", then the atime and ctime of
490 each file and directory get set to the value found in their
491 mtime.
492 These actions stay delayed until actual ISO production begins.
493 Up to then they can be revoked by --set_all_file_dates with
494 empty timestring or timestring "default".
495 The timestamps of the El Torito boot catalog file get refreshed
496 when the ISO is produced. They can be influenced by
497 --modification-date=.
498 -file_name_limit number
500 Set the maximum permissible length for file names in the range
501 of 64 to 255. Path components which are longer than the given
502 number will get truncated and have their last 33 bytes
503 overwritten by a colon ':' and the hex representation of the MD5
504 of the first 4095 bytes of the whole oversized name. Potential
505 incomplete UTF-8 characters will get their leading bytes
506 replaced by '_'.
507 Linux kernels up to at least 4.1 misrepresent names of length
508 254 and 255. If you expect such names in or under disk_paths
509 and plan to mount the ISO by such Linux kernels, consider to set
510 -file_name_limit 253.
511 -D The standard ECMA-119 demands that no path in the image shall
513 have more than 8 name components or 255 characters. Therefore it
514 would be necessary to move deeper directory trees to a higher
515 directory. Rock Ridge offers an opportunity to let these
516 relocated directories appear at their original deep position,
517 but this feature might not be implemented properly by operating
518 systems which mount the image.
519 Option -D disables this deep directory relocation, and thus
520 violates ISO 9660 specs.
521 xorrisofs has -D set by default. If given explicitly then it
522 overrides the options -rr_reloc_dir and -hide-rr-moved.
523 -disable-deep-relocation
525 Alias of -D.
526 -rr_reloc_dir name
528 Enable the relocation of deep directories and thus avoid
529 ECMA-119 file paths of more than 8 name components or 255
530 characters. Directories which lead to such file paths will get
531 moved to a directory in the root directory of the image. Its
532 name gets set by this option. It is permissible to use the root
533 directory itself.
534 The overall directory tree will appear originally deep when
535 interpreted as Rock Ridge tree. It will appear as re-arranged if
536 only ECMA-119 information is considered.
537 If the given relocation target directory does not already exist
538 when image production begins, then it will get created and
539 marked for Rock Ridge as relocation artefact. At least on
540 GNU/Linux it will not be displayed in mounted Rock Ridge images.
541 The name must not contain a '/' character after its first
542 character and it must not be longer than 255 bytes.
543 This option has no effect if option -D is present.
544 -hide-rr-moved
546 Alias of -rr_reloc_dir "/.rr_moved"
547 --for_backup
549 Enable options which improve backup fidelity: --acl, --xattr,
550 --md5, --hardlinks.
551 --acl
553 Enable recording and loading of ACLs from GNU/Linux or FreeBSD
554 (see man getfacl, man acl). They will not be in effect with
555 mounted ISO images. But xorriso can restore them on the same
556 systems when extracting files from the ISO image.
557 --xattr
559 Enable recording and loading of GNU/Linux or FreeBSD extended
560 attributes in user namespace (see man getfattr and man attr, man
561 getextattr and man 9 extattr, respectively). They will not be
562 in effect with mounted ISO images. But xorriso can restore them
563 on the same systems when extracting files from the ISO image.
564 --md5
566 Enable recording of MD5 checksums for the overall ISO image and
567 for each single data file in the image. xorriso can check the
568 content of an ISO image with these sums and raise alert on
569 mismatch. See man xorriso, options -check_media, check_md5_r.
570 xorriso can print recorded MD5 checksums. E.g. by:
571 -find / -exec get_md5
572 --hardlinks
574 Enable loading and recording of hardlink relations. Search for
575 families of iso_rr files which stem from the same disk file,
576 have identical content filtering and have identical properties.
577 The members of each family get the same inode number in the ISO
578 image.
579 Whether these numbers are respected at mount time depends on the
580 operating system. xorriso can create hardlink families when
581 extracting files from the ISO image.
582 --scdbackup_tag disk_path record_name
584 Append a scdbackup checksum record to the image. This works only
585 if the parameter next_writeable_address of option -C is 0 and
586 --md5 is enabled. If disk_path is not an empty string, then
587 append a scdbackup checksum record to the end of this file.
588 record_name is a word that gets part of tag and record.
589 Program scdbackup_verify will recognize and verify tag and file
590 record.
591 An empty record_name disables this feature.
592 -J
594 Enable the production of an additional Joliet directory tree
595 along with the ISO 9660 Rock Ridge tree.
596 -joliet
598 Alias of -J.
599 -joliet-long
601 Allow 103 characters in Joliet file names rather than 64 as is
602 prescribed by the specification. Allow Joliet paths longer than
603 the prescribed limit of 240 characters.
604 Oversized names get truncated. Without this option, oversized
605 paths get excluded from the Joliet tree.
606 -joliet-utf16
608 Encode Joliet file names in UTF-16BE rather than UCS-2. The
609 difference is with characters which are not present in UCS-2 and
610 get encoded in UTF-16 by 2 words of 16 bit each. Both words
611 then stem from a reserved subset of UCS-2.
612 -hfsplus
614 Enable the production of an additional HFS+ filesystem inside
615 the ISO 9660 image and mark it by Apple Partition Map (APM)
616 entries in the System Area, the first 32 KiB of the image.
617 This may collide with options like -G or -isohybrid-mbr which
618 submit user data for inclusion in the same address range. The
619 first 8 bytes of the System Area get overwritten by { 0x45,
620 0x52, 0x08 0x00, 0xeb, 0x02, 0xff, 0xff } which can be executed
621 as x86 machine code without negative effects. So if an MBR gets
622 combined with this feature, then its first 8 bytes should
623 contain no essential commands.
624 The next blocks of 2 KiB in the System Area will be occupied by
625 APM entries. The first one covers the part of the ISO image
626 before the HFS+ filesystem metadata. The second one marks the
627 range from HFS+ metadata to the end of file content data. If
628 more ISO image data follow, then a third partition entry gets
629 produced. Other features of xorriso might cause the need for
630 more APM entries.
631 Be aware that HFS+ is case-insensitive although it can record
632 file names with upper-case and lower-case letters. Therefore,
633 file names from the iso_rr name tree may collide in the HFS+
634 name tree. In this case they get changed by adding underscore
635 characters and counting numbers. In case of very long names, it
636 might be necessary to map them to "MANGLED_...".
637 -hfsplus-serial-no
639 Set a string of 16 digits "0" to "9" and letters "a" to "f",
640 which will be used as unique serial number of an emerging HFS+
641 filesystem.
642 -hfsplus-block-size number
644 Set the allocation block size to be used when producing HFS+
645 filesystems. Permissible are 512, 2048, or 0. The latter lets
646 the program decide.
647 -apm-block-size number
649 Set the block size to be used when describing partitions by an
650 Apple Partition Map. Permissible are 512, 2048, or 0. The latter
651 lets the program decide.
652 Note that size 512 is not compatible with production of GPT, and
653 that size 2048 will not be mountable -t hfsplus at least by
654 older Linux kernels.
655 -hfsplus-file-creator-type creator type iso_rr_path
657 Set the HFS+ creator and type attributes of a file in the
658 emerging image. These are two codes of 4 characters each.
659 -hfs-bless-by blessing iso_rr_path
661 Issue a HFS+ blessing. They are roles which can be attributed to
662 up to four directories and a data file:
663 "ppc_bootdir", "intel_bootfile", "show_folder", "os9_folder",
664 "osx_folder".
665 They may be abbreviated as "p", "i", "s", "9", and "x".
666 Each such role can be attributed to at most one file object.
667 "intel_bootfile" is the one that would apply to a data file. All
668 others apply to directories. No file object can bear more than
669 one blessing.
670 -hfs-bless disk_path
672 Issue HFS+ blessing "ppc_bootdir" to the directory which stems
673 from the directory disk_path in the local filesystem tree.
674 This works only if there is at least one data file underneath
675 the directory. disk_path can become ambiguous if files from
676 different local filesystem sub-trees are put into the same
677 sub-tree of the ISO image. Consider to use -hfs-bless-by "p"
678 for unambiguous addressing via iso_rr_path.
679 Settings for file hiding:
681 -hide disk_path_pattern
683 Make files invisible in the directory tree of ISO 9660 and Rock
684 Ridge, if their disk_path matches the given shell parser
685 pattern. The data content of such hidden files will be included
686 in the resulting image, even if they do not show up in any
687 directory. But you will need own means to find nameless data in
688 the image.
689 This command does not apply to the boot catalog.
690 -hide-list disk_path
692 Perform -hide using each line out of file disk_path as argument
693 disk_path_pattern.
694 -hide-joliet disk_path_pattern
696 Like option -hide but making files invisible in the directory
697 tree of Joliet, if their disk_path matches the given shell
698 parser pattern.
699 -hide-joliet-list disk_path
701 Perform -hide-joliet using each line out of file disk_path as
702 argument disk_path_pattern.
703 -hide-hfsplus disk_path_pattern
705 Like option -hide but making files invisible in the directory
706 tree of HFS+, if their disk_path matches the given shell parser
707 pattern.
708 -hide-hfsplus-list disk_path
710 Perform -hide-hfsplus using each line out of file disk_path as
711 argument disk_path_pattern.
712 ISO image ID strings:
714 The following strings and file addresses get stored in the Primary
716 Volume Descriptor of the ISO9660 image. The file addresses are ISO 9660
717 paths. These files should have iso_rr_paths which consist only of the
718 characters [A-Z0-9_] and exactly one dot which separates at most 8
719 characters from at most 3 characters.
720 -V text
722 Set the Volume Id of the ISO image. xorriso accepts any text up
723 to 32 characters, but according to rarely obeyed specs stricter
724 rules apply:
725 Conformant are ASCII characters out of [A-Z0-9_]. Like:
726 "IMAGE_23"
727 Joliet allows 16 UCS-2 characters. Like: "Windows name"
728 Be aware that the volume id might get used automatically as name
729 of the mount point when the medium is inserted into a playful
730 computer system.
731 -volid text
733 Alias of -V.
734 -volset text
736 Set the Volume Set Id of the ISO image. Permissible are up to
737 128 characters.
738 -P text
740 Set the Publisher Id of the ISO image. This may identify the
741 person or organisation who specified what shall be recorded.
742 Permissible are up to 128 characters.
743 -publisher text
745 Alias of -P.
746 -A text
748 Set the Application Id of the ISO image. This may identify the
749 specification of how the data are recorded. Permissible are up
750 to 128 characters.
751 The special text "@xorriso@" gets converted to the id string of
752 xorriso which is normally written as Preparer Id. It is a wrong
753 tradition to write the program id as Application Id.
754 -appid text
756 Alias of -A.
757 -sysid text
759 Set the System Id of the ISO image. This may identify the system
760 which can recognize and act upon the content of the System Area
761 in image blocks 0 to 15. Permissible are up to 32 characters.
762 -p text
764 Set the Preparer Id of the ISO image. This may identify the
765 person or other entity which controls the preparation of the
766 data which shall be recorded. Normally this should be the id of
767 xorriso and not of the person or program which operates xorriso.
768 Please avoid to change it. Permissible are up to 128
769 characters.
770 The special text "@xorriso@" gets converted to the id string of
771 xorriso which is default at program startup.
772 -preparer text
774 Alias of -p.
775 -abstract iso_path
777 Set the address of the Abstract File of the ISO image. This
778 should be the ISO 9660 path of a file in the image which
779 contains an abstract statement about the image content.
780 Permissible are up to 37 characters.
781 -biblio iso_path
783 Set the address of the Biblio File of the ISO image. This should
784 be the ISO 9660 path of a file in the image which contains
785 bibliographic records. Permissible are up to 37 characters.
786 -copyright iso_path
788 Set the address of the Copyright File of the ISO image. This
789 should be the ISO 9660 path of a file in the image which
790 contains a copyright statement. Permissible are up to 37
791 characters.
792 --modification-date=YYYYMMDDhhmmsscc
794 Set a timestring that overrides ISO image creation and
795 modification timestamps literally. It must consist of 16
796 decimal digits which form YYYYMMDDhhmmsscc, with YYYY between
797 1970 and 2999. Time zone is GMT. It is supposed to match this
798 GRUB line:
799 search --fs-uuid --set YYYY-MM-DD-hh-mm-ss-cc
800 E.g. 2010040711405800 is 7 Apr 2010 11:40:58 (+0 centiseconds).
801 Among the influenced timestamps are: isohybrid MBR id, El Torito
802 boot catalog file, HFS+ superblock.
803 --application_use character|0xXY|disk_path
805 Specify the content of the Application Use field which can take
806 at most 512 bytes.
807 If the parameter of this command is empty, then the field is
808 filled with 512 0-bytes. If it is a single character, then it
809 gets repeated 512 times. If it begins by "0x" followed by two
810 hex digits [0-9a-fA-F], then the digits are read as byte value
811 which gets repeated 512 times.
812 Any other parameter text is used as disk_path to open a data
813 file and to read up to 512 bytes from it. If the file is smaller
814 than 512 bytes, then the remaining bytes in the field get set to
815 binary 0.
816 El Torito Bootable ISO images:
818 The precondition for a bootable ISO image is to have in the ISO image
820 the files of a boot loader. The boot facilities of computers get
821 directed to such files, which usually execute further program files
822 from the ISO image. xorrisofs can produce several kinds of boot block
823 or boot record, which become part of the ISO image, and get interpreted
824 by the according boot facility.
825 An El Torito boot record points the bootstrapping facility to a boot
827 catalog with one or more boot images, which are binary program files
828 stored in the ISO image. The content of the boot image files is not in
829 the scope of El Torito.
830 xorriso composes the boot catalog according to the boot image files
831 given and structured by options -b, -e, -eltorito-alt-boot, and
832 --efi-boot. Often it contains only one entry.
833 Normally the boot images are data files inside the ISO filesystem. By
834 special path "--interval:appended_partition_NNN:all::" it is possible
835 to refer to an appended partition. The number NNN gives the partition
836 number as used with the corresponding option -append_partition. E.g.:
837 -append_partition 2 0xef /tmp/efi.img
838 -e --interval:appended_partition_2:all::
839 El Torito gets interpreted by boot facilities PC-BIOS and EFI. Most
840 bootable GNU/Linux CDs are equipped with ISOLINUX or GRUB boot images
841 for PC-BIOS.
842 xorrisofs supports the example options out of the ISOLINUX wiki, the
843 options used in GRUB script grub-mkrescue, and the example in the
844 FreeBSD AvgLiveCD wiki.
845 For CD booting via boot facilities other than PC-BIOS and EFI, and for
847 booting from USB sticks or hard disks, see the next section about the
848 System Area.
849 -b iso_rr_path
851 Specify the boot image file which shall be mentioned in the
852 current entry of the El Torito boot catalog. It will be marked
853 as suitable for PC-BIOS.
854 With boot images from ISOLINUX and GRUB this option should be
855 accompanied by options -c , -no-emul-boot , -boot-load-size 4 ,
856 -boot-info-table.
857 -eltorito-boot iso_rr_path
859 Alias of -b.
860 -eltorito-alt-boot
862 Finalize the current El Torito boot catalog entry and begin a
863 new one. A boot image file and all its necessary options shall
864 be specified before option -eltorito-alt-boot. All further El
865 Torito boot options apply to the new catalog entry. Up to 32
866 catalog entries are possible.
867 -e iso_rr_path
869 Specify the boot image file which shall be mentioned in the
870 current entry of the El Torito boot catalog. It will be marked
871 as suitable for EFI.
872 Option -e should be followed by option -no-emul-boot and no
873 other El Torito options before an eventual -eltorito-alt-boot.
874 --efi-boot iso_rr_path
876 Perform -eltorito-alt-boot, option -e with the given
877 iso_rr_path, -no-emul-boot, and again -eltorito-alt-boot. This
878 gesture is used for achieving EFI-bootability of the GRUB2
879 rescue CD.
880 -eltorito-platform "x86"|"PPC"|"Mac"|"efi"|0xnn|nnn
882 Set the Platform Id number for the next option -b or
883 -eltorito-boot. The number may be chosen by a platform name or
884 by a number between 0 and 255 (0x00 and 0xFF). "x86" = 0 is for
885 PC-BIOS, "PPC" = 1 for some PowerPC systems, "Mac" = 2 for some
886 MacIntosh systems, "efi" = 0xEF for EFI on modern PCs with x86
887 compatible CPUs or others.
888 If the new platform id differs from the previous one,
889 -eltorito-alt-boot gets performed.
890 -boot-load-size number|"full"
892 Set the number of 512-byte blocks to be loaded at boot time from
893 the boot image in the current catalog entry.
894 Non-emulating BIOS bootimages usually need a load size of 4.
895 Nevertheless the default setting of mkisofs is to use the full
896 size of the boot image rounded up to a multiple of 4 512-byte
897 blocks. This default may be explicitely enforced by the word
898 "full" instead of a number.
899 EFI boot images usually get set the number of blocks occupied by
900 the boot image file.
901 El Torito cannot represent load sizes higher than 65535.
902 -hard-disk-boot
904 Mark the boot image in the current catalog entry as emulated
905 hard disk. (Not suitable for any known boot loader.)
906 -no-emul-boot
908 Mark the boot image in the current catalog entry as not
909 emulating floppy or hard disk. (This is to be used with all
910 known boot loaders.)
911 If neither -hard-disk-boot nor -no-emul-boot is given, then the
912 boot image will be marked as emulating a floppy. (Not suitable
913 for any known boot loader.)
914 -eltorito-id text|56_hexdigits
916 Define the ID string of the boot catalog section where the boot
917 image will be listed. If the value consists of 56 characters
918 [0-9A-Fa-f] then it is converted into 28 bytes, else the first
919 28 characters become the ID string. The ID string of the first
920 boot image becomes the overall catalog ID. It is limited to 24
921 characters. Other id_strings become section IDs.
922 -eltorito-selcrit hexdigits
924 Define the Selection Criteria of the boot image. Up to 20 bytes
925 get read from the given characters [0-9A-Fa-f]. They get
926 attributed to the boot image entry in the catalog.
927 -boot-info-table
929 Overwrite bytes 8 to 63 in the current boot image. The
930 information will be supplied by xorriso in the course of image
931 production: Block address of the Primary Volume Descriptor,
932 block address of the boot image file, size of the boot image
933 file.
934 --grub2-boot-info
936 Overwrite bytes 2548 to 2555 in the current boot image by the
937 address of that boot image. The address is written as 64 bit
938 little-endian number. It is the 2KB block address of the boot
939 image content, multiplied by 4, and then incremented by 5.
940 -c iso_rr_path
942 Set the address of the El Torito boot catalog file within the
943 image. This file address is not significant for the booting
944 PC-BIOS or EFI, but it may later be read by other programs in
945 order to learn about the available boot images.
946 -eltorito-catalog iso_rr_path
948 Alias of -c.
949 --boot-catalog-hide
951 Prevent the El Torito boot catalog from appearing as file in the
952 directory trees of the image.
953 System Area, MBR, GPT, APM, other boot blocks:
955 The first 16 blocks of an ISO image are the System Area. It is
957 reserved for system dependent boot software. This may be the boot
958 facilities and partition tables of various hardware architectures.
959 A MBR (Master Boot Record) contains boot code and a partition table.
960 It is read by PC-BIOS when booting from USB stick or hard disk, and by
961 PowerPC CHRP or PReP when booting. An MBR partiton with type 0xee
962 indicates the presence of GPT.
963 A GPT (GUID Partition Table) marks partitions in a more modern way. It
964 is read by EFI when booting from USB stick or hard disk, and may be
965 used for finding and mounting a HFS+ partition inside the ISO image.
966 An APM (Apple Partition Map) marks the HFS+ partition. It is read by
967 Macs for booting and for mounting.
968 MBR, GPT and APM are combinable. APM occupies the first 8 bytes of MBR
969 boot code. All three do not hamper El Torito booting from CDROM.
970 xorrisofs supports further boot facilities: MIPS Big Endian (SGI), MIPS
971 Little Endian (DEC), SUN SPARC, HP-PA, DEC Alpha. Those are mutually
972 not combinable and also not combinable with MBR, GPT, or APM.
973 Several of the following options expect disk paths as input but also
975 accept description strings for the libisofs interval reader, which is
976 able to cut out data from disk files or -indev and to zeroize parts of
977 the content: -G, -generic-boot, --embedded-boot, --grub2-mbr,
978 -isohybrid-mbr, -efi-boot-part, -prep-boot-part, -B, -sparc-boot,
979 -append_partition.
980 The description string consists of the following components, separated
981 by colon ':'
982 "--interval:"Flags":"Interval":"Zeroizers":"Source
983 The component "--interval" states that this is not a plain disk path
984 but rather a interval reader description string.
985 The component Flags modifies the further interpretation:
986 "local_fs" demands to read from a file depicted by the path in Source.
987 "imported_iso" demands to read from the -indev. This works only if
988 -outdev is not the same as -indev. The Source component is ignored.
989 "appended_partition_NNN" with a decimal number NNN works only for
990 options which announce El Torito boot image paths: -b, -e, --efi-boot.
991 The number gives the partition number as used with the corresponding
992 option -append_partition.
993 The component Interval consists of two byte address numbers separated
994 by a "-" character. E.g. "0-429" means to read bytes 0 to 429.
995 The component Zeroizers consists of zero or more comma separated
996 strings. They define which part of the read data to zeroize. Byte
997 number 0 means the byte read from the Interval start address. Each
998 string may be one of:
999 "zero_mbrpt" demands to zeroize the MBR partition table if bytes 510
1000 and 511 bear the MBR signature 0x55 0xaa.
1001 "zero_gpt" demands to check for a GPT header in bytes 512 to 1023, to
1002 zeroize it and its partition table blocks.
1003 "zero_apm" demands to check for an APM block 0 and to zeroize its
1004 partition table blocks.
1005 Start_byte"-"End_byte demands to zeroize the read-in bytes beginning
1006 with number Start_byte and ending after End_byte.
1007 The component Source is the file path with flag "local_fs", and ignored
1008 with flag "imported_iso".
1009 Byte numbers may be scaled by a suffix out of {k,m,g,t,s,d} meaning
1010 multiplication by {1024, 1024k, 1024m, 1024g, 2048, 512}. A scaled
1011 value end number depicts the last byte of the scaled range.
1012 E.g. "0d-0d" is "0-511".
1013 Examples:
1014 "local_fs:0-32767:zero_mbrpt,zero_gpt,440-443:/tmp/template.iso"
1015 "imported_iso:45056d-47103d::"
1016 -G disk_path
1018 Copy at most 32768 bytes from the given disk file to the very
1019 start of the ISO image.
1020 Other than a El Torito boot image, the file disk_path needs not
1021 to be added to the ISO image. It will not show up as file in the
1022 directory trees.
1023 In multi-session situations, the special disk_path "." prevents
1024 reading of a disk file but nevertheless causes the adjustments
1025 in the existing MBR, which were ordered by other options.
1026 -generic-boot disk_path
1028 Alias of -G.
1029 --embedded-boot disk_path
1031 Alias of -G.
1032 --grub2-mbr disk_path
1034 Install disk_path in the System Area and treat it as modern
1035 GRUB2 MBR. The content start address of the first boot image is
1036 converted to a count of 512 byte blocks, and an offset of 4 is
1037 added. The result is written as 64 bit little-endian number to
1038 byte address 0x1b0.
1039 -isohybrid-mbr disk_path
1041 Install disk_path as ISOLINUX isohybrid MBR which makes the boot
1042 image given by option -b bootable from USB sticks and hard disks
1043 via PC-BIOS. This preparation is normally done by ISOLINUX
1044 program isohybrid on the already produced ISO image.
1045 The disk path should lead to one of the Syslinux files
1046 isohdp[fp]x*.bin . The MBR gets patched according to isohybrid
1047 needs. The first partition describes the range of the ISO image.
1048 Its start is at block 0 by default, but may be set to 64 disk
1049 blocks by option -partition_offset 16.
1050 For the meaning of special disk_path "." see option -G.
1051 -isohybrid-gpt-basdat
1053 Mark the current El Torito boot image (see options -b and -e) in
1054 GPT as partition of type Basic Data. This works only with
1055 -isohybrid-mbr and has the same impact on the system area as
1056 -efi-boot-part. It cannot be combined with -efi-boot-part or
1057 -hfsplus.
1058 The first three boot images which are marked by GPT will also
1059 show up as partition entries of type 0xef in MBR. The MBR
1060 partition for PC-BIOS gets type 0x00 rather than 0x17 in this
1061 case. Often the further MBR entries are the ones which actually
1062 get used by EFI.
1063 -isohybrid-gpt-hfsplus
1065 Mark the current El Torito boot image (see options -b and -e) in
1066 GPT as partition of type HFS+. Impact and restrictions are like
1067 with -isohybrid-gpt-basdat.
1068 -isohybrid-apm-hfsplus
1070 Mark the current El Torito boot image (see options -b and -e) in
1071 Apple Partition Map as partition of type HFS+. This works only
1072 with -isohybrid-mbr and has a similar impact on the system area
1073 as -hfsplus. It cannot be combined with -efi-boot-part or
1074 -hfsplus.
1075 The ISOLINUX isohybrid MBR file must begin by a known pattern of
1076 32 bytes of x86 machine code which essentially does nothing. It
1077 will get overwritten by 32 bytes of APM header mock-up.
1078 -part_like_isohybrid
1080 Control whether -isohybrid-gpt-basdat, -isohybrid-gpt-hfsplus,
1081 and -isohybrid-apm-hfsplus apply even if not -isohybrid-mbr is
1082 present. No MBR partition of type 0xee emerges, even if GPT
1083 gets produced. Gaps between GPT and APM partitions will not be
1084 filled by more partitions. Appended partitions get mentioned in
1085 APM if other APM partitions emerge.
1086 -iso_mbr_part_type "default"|number
1088 Set the partition type of the MBR partition which represents the
1089 ISO or at least protects it. Number may be 0x00 to 0xff. The
1090 text "default" re-enables the default types of the various
1091 occasions to create an ISO MBR partition.
1092 This is without effect if no such partition emerges by other
1093 settings or if the partition type is prescribed mandatorily like
1094 0xee for GPT protective MBR or 0x96 for CHRP.
1095 --protective-msdos-label
1097 Patch the System Area by a simple PC-DOS partition table where
1098 partition 1 claims the range of the ISO image but leaves the
1099 first block unclaimed.
1100 --mbr-force-bootable
1102 Enforce an MBR partition with "bootable/active" flag if options
1103 like --protective-msdos-label or --grub2-mbr are given. These
1104 options normally cause the flag to be set if there is an MBR
1105 partition of type other than 0xee or 0xef. If no such partition
1106 exists, then no bootflag is set, unless --mbr-force-bootable
1107 forces creation of a dummy partition of type 0x00 which covers
1108 only the first block of the ISO image.
1109 If no bootable MBR is indicated by other options and a partition
1110 gets created by -append_partition, then --mbr-force-bootable
1111 causes a bootflag like it would do with e.g.
1112 --protective-msdos-label.
1113 -partition_offset 2kb_block_adr
1115 Cause a partition table with a single partition that begins at
1116 the given block address. This is counted in 2048 byte blocks,
1117 not in 512 byte blocks. If the block address is non-zero then it
1118 must be at least 16. Values larger than 16 are hardly of use. A
1119 non-zero partition offset causes two superblocks to be generated
1120 and two sets of directory trees. The image is then mountable
1121 from its absolute start as well as from the partition start.
1122 The offset value of an ISO image gets preserved when a new
1123 session is added to a loaded image. So the value defined here
1124 is only in effect if a new ISO image gets written.
1125 -partition_hd_cyl number
1127 Set the number of heads per cylinder for the MBR partition
1128 table. 0 chooses a default value. Maximum is 255.
1129 -partition_sec_hd number
1131 Set the number of sectors per head for the MBR partition table.
1132 0 chooses a default value. Maximum is 63.
1133 The product partition_sec_hd * partition_hd_cyl * 512 is the
1134 cylinder size. It should be divisible by 2048 in order to make
1135 exact alignment possible. With appended partitions and
1136 -appended_part_as_gpt there is no limit for the number of
1137 cylinders. Else there may be at most 1024 of them. If the
1138 cylinder size is too small to stay below the limit, then
1139 appropriate values of partition_hd_cyl are chosen with
1140 partition_sec_hd 32 or 63. If the image is larger than
1141 8,422,686,720 bytes, then the cylinder size constraints cannot
1142 be fulfilled for MBR. They seem not overly important anyway.
1143 Flat block addresses in partition tables are good for 1 TiB.
1144 -partition_cyl_align mode
1146 Control image size alignment to an integer number of cylinders.
1147 It is prescribed by isohybrid specs and it seems to please
1148 program fdisk. Cylinder size must be divisible by 2048. Images
1149 larger than 8,323,596,288 bytes cannot be aligned in MBR
1150 partition table.
1151 Mode "auto" is default. Alignment by padding happens only if
1152 option -isohybrid-mbr is given.
1153 Mode "on" causes alignment by padding with option
1154 --protective-msdos-label too. Mode "all" is like "on" but also
1155 pads up partitions from -append_partition to an aligned size.
1156 Mode "off" disables alignment unconditionally.
1157 -append_partition partition_number type_code disk_path
1159 Cause a prepared filesystem image to be appended to the ISO
1160 image and to be described by a partition table entry in a boot
1161 block at the start of the emerging ISO image. The partition
1162 entry will bear the size of the submitted file rounded up to the
1163 next multiple of 2048 bytes or to the next multiple of the
1164 cylinder size.
1165 Beware of subsequent multi-session runs. The appended partition
1166 will get overwritten.
1167 partition_number may be 1 to 4. Number 1 will put the whole ISO
1168 image into the unclaimed space before partition 1. So together
1169 with most xorriso MBR or GPT features, number 2 would be the
1170 most natural choice.
1171 The type_code may be "FAT12", "FAT16", "Linux", or a hexadecimal
1172 number between 0x00 and 0xff. Not all those numbers will yield
1173 usable results. For a list of codes search the Internet for
1174 "Partition Types" or run fdisk command "L". This code matters
1175 only with MBR, not with GPT.
1176 If some other command causes the production of GPT, then the
1177 appended partitions will be mentioned there too, even if not
1178 -appended_part_as_gpt is given.
1179 -appended_part_as_gpt
1181 Marks partitions from -append_partition in GPT rather than in
1182 MBR. In this case the MBR shows a single partition of type 0xee
1183 which covers the whole output data.
1184 By default, appended partitions get marked in GPT only if GPT is
1185 produced because of other options.
1186 -appended_part_as_apm
1188 Marks partitions from -append_partition in Apple Partition Map,
1189 too.
1190 By default, appended partitions get marked in APM only if APM is
1191 produced because of other options and -part_like_isohybrid is
1192 enabled.
1193 -efi-boot-part disk_path
1195 Copy a file from disk into the emerging ISO image and mark it by
1196 a GPT entry as EFI System Partition. EFI boot firmware is
1197 supposed to use a FAT filesystem image in such a partition for
1198 booting from USB stick or hard disk.
1199 Instead of a disk_path, the word --efi-boot-image may be given.
1200 It exposes in GPT the content of the first El Torito EFI boot
1201 image as EFI system partition. EFI boot images are introduced by
1202 options -e or --efi-boot. The affected EFI boot image cannot
1203 show up in HFS+ because it is stored outside the HFS+ partition.
1204 --gpt_disk_guid value
1206 Control whether an emerging GPT shall get a randomly generated
1207 disk GUID or whether the GUID is supplied by the user. Value
1208 "random" is default. Value "modification-date" produces a low
1209 quality GUID from the value set by option --modification-date=.
1210 A string of 32 hex digits, or a RFC 4122 compliant GUID string
1211 may be used to set the disk GUID directly. UEFI prescribes the
1212 first three components of a RFC 4122 GUID string to be
1213 byte-swapped in the binary representation:
1214 E.g. --gpt_disk_guid 2303cd2a-73c7-424a-a298-25632da7f446 equals
1215 --gpt_disk_guid 2acd0323c7734a42a29825632da7f446
1216 The partition GUIDs get generated by minimally varying the disk
1217 GUID.
1218 -chrp-boot-part
1220 Mark the block range of the whole emerging ISO image as MBR
1221 partition of type 0x96. This is not compatible with any other
1222 feature that produces MBR partition entries. It makes GPT
1223 unrecognizable.
1224 CHRP is often used in conjunction with HFS. It is not yet tested
1225 whether HFS+ filesystems produced with option -hfsplus would
1226 boot on any CHRP capable machine which does not boot pure ISO
1227 9660 as well.
1228 -chrp-boot
1230 Alias of -chrp-boot-part.
1231 -prep-boot-part disk_path
1233 Copy a file from disk into the emerging ISO image and mark it by
1234 a MBR partition entry of type 0x41. PReP boot firmware is
1235 supposed to read the content of the partition as single ELF
1236 executable file. This option is compatible with other MBR
1237 partitions and with GPT.
1238 -mips-boot iso_rr_path
1240 Declare a data file in the image to be a MIPS Big Endian boot
1241 file and cause production of a MIPS Big Endian Volume Header.
1242 This is mutually exclusive with production of other boot blocks
1243 like MBR. It will overwrite the first 512 bytes of any data
1244 provided by -G. Up to 15 boot files can be declared by multiple
1245 -mips-boot options.
1246 -mipsel-boot iso_rr_path
1248 Declare a data file in the image to be the MIPS Little Endian
1249 boot file. This is mutually exclusive with other boot blocks.
1250 It will overwrite the first 512 bytes of any data provided by
1251 -G. Only a single boot file can be declared by -mipsel-boot.
1252 -B disk_path[,disk_path ...]
1254 Cause one or more data files on disk to be written after the end
1255 of the ISO image. A SUN Disk Label will be written into the
1256 first 512 bytes of the ISO image which lists this image as
1257 partition 1 and the given disk_paths as partition 2 up to 8.
1258 The disk files should contain suitable boot images for SUN SPARC
1259 systems.
1260 The pseudo disk_path "..." causes that all empty partition
1261 entries become copies of the last non-empty entry. If no other
1262 disk_path is given before "..." then all partitions describe the
1263 ISO image. In this case, the boot loader code has to be imported
1264 by option -G.
1265 -sparc-boot disk_path[,disk_path ...]
1267 Alias of -B.
1268 -sparc-label text
1270 Set the ASCII label text of a SUN Disk Label.
1271 --grub2-sparc-core iso_rr_path
1273 Cause the content address and size of the given data file in the
1274 image to be written after the SUN Disk Label. Both numbers are
1275 counted in bytes. The address is written as 64 bit big-endian
1276 number to byte 0x228. The size is written as 32 bit big-endian
1277 number to byte 0x230.
1278 -hppa-cmdline text
1280 Set the PALO command line for HP-PA. Up to 1023 characters are
1281 permitted by default. With -hppa-hdrversion 4 the limit is 127.
1282 Note that the first five -hppa options are mandatory, if any of
1283 the -hppa options is given. Only option -hppa-hdrversion is
1284 allowed to be missing.
1285 -hppa-bootloader iso_rr_path
1287 Designate the given path as HP-PA bootloader file.
1288 -hppa-kernel-32 iso_rr_path
1290 Designate the given path as HP-PA 32 bit kernel file.
1291 -hppa-kernel-64 iso_rr_path
1293 Designate the given path as HP-PA 64 bit kernel file.
1294 -hppa-ramdisk iso_rr_path
1296 Designate the given path as HP-PA RAM disk file.
1297 -hppa-hdrversion number
1299 Choose between PALO header version 5 (default) and version 4.
1300 For the appropriate value see in PALO source code:
1301 PALOHDRVERSION.
1302 -alpha-boot iso_rr_path
1304 Declare a data file in the image to be the DEC Alpha SRM
1305 Secondary Bootstrap Loader and cause production of a boot sector
1306 which points to it. This is mutually exclusive with production
1307 of other boot blocks like MBR.
1308 Character sets:
1310 Character sets should not matter as long as only english alphanumeric
1312 characters are used for file names or as long as all writers and
1313 readers of the medium use the same character set. Outside these
1314 constraints it may be necessary to let xorriso convert byte codes.
1315 A conversion from input character set to the output character set is
1316 performed when an ISO image gets written. Vice versa there is a
1317 conversion from output character set to the input character set when an
1318 ISO image gets loaded. The sets can be defined by options
1319 -input-charset and -output-charset, if needed.
1320 -input-charset character_set_name
1322 Set the character set from which to convert disk file names when
1323 inserting them into the ISO image.
1324 -output-charset character_set_name
1326 Set the character set from which to convert names of loaded ISO
1327 images and to which to convert names when writing ISO images.
1328 Jigdo Template Extraction:
1330 From man genisoimage: "Jigdo is a tool to help in the distribution of
1332 large files like CD and DVD images; see http://atterer.net/jigdo/ for
1333 more details. Debian CDs and DVD ISO images are published on the web in
1334 jigdo format to allow end users to download them more efficiently."
1335 If the use of libjte was enabled at compile time of xorriso, then
1336 xorrisofs can produce a .jigdo and a .template file together with a
1337 single-session ISO image. If not, then Jigdo options will cause a
1338 FAILURE event, which normally leads to program abort.
1339 One may determine the ability for Jigdo by:
1340 $ xorrisofs -version 2>&1 | grep '^libjte' && echo YES
1341 The .jigdo file contains checksums and symbolic file addresses. The
1343 .template file contains the compressed ISO image with reference tags
1344 instead of the content bytes of the listed files.
1345 Input for this process are the normal arguments for a xorrisofs session
1346 with no image loaded, and a .md5 file which lists those data files
1347 which may be listed in the .jigdo file and externally referenced in the
1348 .template file. Each designated file is represented in the .md5 file
1349 by a single text line:
1350 MD5 as 32 hex digits, 2 blanks, size as 12 decimal digits or blanks, 2
1351 blanks, symbolic file address
1352 The file address in an .md5 line has to bear the same basename as the
1353 disk_path of the file which it shall match. The directory path of the
1354 file address is decisive for To=From mapping, not for file recognition.
1355 After To=From mapping, the file address gets written into the .jigdo
1356 file. Jigdo restore tools will convert these addresses into really
1357 reachable data source addresses from which they can read.
1358 If the list of jigdo parameters is not empty, then padding will be
1359 counted as part of the ISO image.
1360 -jigdo-jigdo disk_path
1362 Set the disk_path for the .jigdo file with the checksums and
1363 download addresses for filling the holes in .template.
1364 -jigdo-template disk_path
1366 Set the disk_path for the .template file with the holed and
1367 compressed ISO image copy.
1368 -jigdo-min-file-size size
1370 Set the minimum size for a data file to be listed in the .jigdo
1371 file and being a hole in the .template file. size may be a
1372 plain number counting bytes, or a number with appended letter
1373 "k", "m", "g" to count KiB (1024 bytes), MiB (1024 KiB), or GiB
1374 (1024 MiB).
1375 -jigdo-force-md5 disk_path_pattern
1377 adds a regular expression pattern which will get compared with
1378 the absolute disk_path of any data file that was not found in
1379 the .md5 list. A match causes a MISHAP event, which normally
1380 does not abort the program run but finally causes a non-zero
1381 exit value of the program.
1382 -jigdo-exclude disk_path_pattern
1384 Add a regular expression pattern which will get compared with
1385 the absolute disk_path of any data file. A match causes the file
1386 to stay in .template in any case.
1387 -jigdo-map To=From
1389 Add a string pair of the form To=From to the parameter list. If
1390 a data file gets listed in the .jigdo file, then it is referred
1391 by the file address from its line in the .md5 file. This file
1392 address gets checked whether it begins with the From string. If
1393 so, then this string will be replaced by the To string and a ':'
1394 character, before it goes into the .jigdo file. The From string
1395 should end by a '/' character.
1396 -md5-list disk_path
1398 Set the disk_path where to find the .md5 input file.
1399 -jigdo-template-compress "gzip"|"bzip2"
1401 Choose one of "bzip2" or "gzip" for the compression of the
1402 template file. The jigdo file is put out uncompressed.
1403 -checksum_algorithm_iso list_of_names
1405 Choose one or more of "md5", "sha1", "sha256", "sha512" for the
1406 auxiliary "# Image Hex" checksums in the .jigdo file. The
1407 list_of_names may e.g. look like "md5,sha1,sha512". Value "all"
1408 chooses all available algorithms. Note that MD5 stays always
1409 enabled.
1410 -checksum_algorithm_template list_of_names
1412 Choose the algorithms for the "# Template Hex" checksums in the
1413 .jigdo file. The rules for list_of_names are the same as with
1414 -checksum_algorithm_iso.
1415 Miscellaneous options:
1417 -print-size
1419 Print to stdandard output the foreseeable number of 2048 byte
1420 blocks in the emerging ISO image. Do not produce this image.
1421 The result depends on several settings.
1422 If option --emul-toc is given, then padding (see -pad) is not
1423 counted as part of the image size. In this case either use
1424 -no-pad or add 150 (= 300 KiB) to the resulting number.
1425 If mkisofs emulation ends after option -print-size, then the
1426 properties of the most recently specified boot image file cannot
1427 be edited by subsequent xorriso commands.
1428 --no_rc
1430 Only if used as first argument this option prevents reading and
1431 interpretation of startup files. See section FILES below.
1432 -help
1434 List supported options to stderr. Original mkisofs options bear
1435 their original mkisofs description texts.
1436 -quiet
1438 Suppress most messages of the program run, except those which
1439 indicate problems or errors.
1440 -gui
1442 Increase the frequency of pacifier messages while writing an ISO
1443 image.
1444 -log-file disk_path
1446 Truncate file disk_path to 0 size and redirect to it all
1447 messages which would normally appear on stderr. -log-file with
1448 empty text as disk_path re-enables output to stderr.
1449 -v
1451 Enable the output of informational program messages.
1452 -verbose
1454 Alias of -v.
1455 -version
1457 Print to standard output a text that begins with
1458 "mkisofs 2.01-Emulation Copyright (C)"
1459 and to standard error the version information of xorriso.
1460
1462 Overview of examples:
1463 A simple image production run
1464 Set ISO image paths by -graft-points
1465 Perform multi-session runs
1466 Let xorrisofs work underneath growisofs
1467 Incremental backup of a few directory trees
1468 Incremental backup with accumulated trees
1469 Create bootable images for PC-BIOS and EFI
1470 A simple image production run
1472 A prepared file tree in directory ./for_iso gets copied into the root
1473 directory of the ISO image. File permissions get set to read-only for
1474 everybody. Joliet attributes for Microsoft systems get added. The
1475 resulting image gets written as data file ./image.iso on disk.
1476 $ xorrisofs -r -J -o ./image.iso ./for_iso
1477 Set ISO image paths by -graft-points
1479 Without option -graft-points each given disk file is copied into the
1480 root directory of the ISO image, maintaining its name. If a directory
1481 is given, then its files and sub-directories are copied into the root
1482 directory, maintaining their names.
1483 $ xorrisofs ... /home/me/datafile /tmp/directory
1484 yields in the ISO image root directory:
1485 /datafile
1486 /file_1_from_directory
1487 ...
1488 /file_N_from_directory
1489 With option -graft-points it is possible to put files and directories
1491 to arbitrary paths in the ISO image.
1492 $ xorrisofs ... -graft-points /home/me/datafile /dir=/tmp/directory
1493 yields in the ISO image root directory:
1494 /datafile
1495 /dir
1496 Eventually needed parent directories in the image will be created
1497 automatically:
1498 /datafiles/file1=/home/me/datafile
1499 yields in the ISO image:
1500 /datafiles/file1
1501 The attributes of directory /datafiles get copied from /home/me on
1502 disk.
1503 Normally one should avoid = and \ characters in the ISO part of a
1505 pathspec. But if it must be, one may escape them:
1506 /with_\=_and_\\/file=/tmp/directory/file
1507 yields in the ISO image:
1508 /with_=_and_\/file
1509 Perform multi-session runs
1511 This example works for multi-session media only: CD-R[W], DVD-R[W],
1512 DVD+R, BD-R. Add cdrskin option --grow_overwriteable_iso to all -as
1513 cdrecord runs in order to enable multi-session emulation on
1514 overwriteable media.
1515 The first session is written like this:
1516 $ xorrisofs -graft-points \
1517 /tree1=prepared_for_iso/tree1 \
1518 | xorriso -as cdrecord -v dev=/dev/sr0 blank=fast -multi -eject -
1519 Follow-up sessions are written like this:
1520 $ dd if=/dev/sr0 count=1 >/dev/null 2>&1
1521 $ m=$(xorriso -as cdrecord dev=/dev/sr0 -msinfo)
1522 $ xorrisofs -M /dev/sr0 -C $m -graft-points \
1523 /tree2=prepared_for_iso/tree2 \
1524 | xorriso -as cdrecord -v dev=/dev/sr0 -waiti -multi -eject -
1525 Always eject the drive tray between sessions. The old sessions get read
1526 via /dev/sr0. Its device driver might not be aware of the changed
1527 content before it loads the medium again. In this case the previous
1528 session would not be loaded and the new session would contain only the
1529 newly added files.
1530 For the same reason do not let xorriso -as cdrecord load the medium,
1531 but rather do this manually or by a program that reads from /dev/sr0.
1532 Let xorrisofs work underneath growisofs
1534 growisofs expects an ISO formatter program which understands options -C
1535 and -M. A variable is defined to override the hardcoded default name.
1536 $ export MKISOFS="xorrisofs"
1537 $ growisofs -Z /dev/dvd /some/files
1538 $ growisofs -M /dev/dvd /more/files
1539 If no "xorrisofs" is available on your system, then you will have to
1540 create a link pointing to the xorriso binary and tell growisofs to use
1541 it. E.g. by:
1542 $ ln -s $(which xorriso) "$HOME/xorrisofs"
1543 $ export MKISOFS="$HOME/xorrisofs"
1544 One may quit mkisofs emulation by argument "--" and make use of all
1545 xorriso commands. growisofs dislikes options which start with "-o" but
1546 -outdev must be set to "-". So use "outdev" instead:
1547 $ growisofs -Z /dev/dvd --for_backup -- \
1548 outdev - -update_r /my/files /files
1549 $ growisofs -M /dev/dvd --for_backup -- \
1550 outdev - -update_r /my/files /files
1551 Note that --for_backup is given in the mkisofs emulation. To preserve
1552 the recorded extra data it must already be in effect, when the
1553 emulation loads the image.
1554 Incremental backup of a few directory trees
1556 This changes the directory trees /open_source_project and
1557 /personal_mail in the ISO image so that they become exact copies of
1558 their disk counterparts. ISO file objects get created, deleted or get
1559 their attributes adjusted accordingly.
1560 ACL, xattr, hard links and MD5 checksums will be recorded. It is
1561 expected that inode numbers in the disk filesystem are persistent over
1562 cycles of mounting and booting. Files with names matching *.o or *.swp
1563 get excluded explicitly.
1564 To be used several times on the same medium, whenever an update of the
1566 two disk trees to the medium is desired. Begin with a blank medium and
1567 update it until he run fails gracefully due to lack of remaining space
1568 on the old one.
1569 Do not let xorriso -as cdrecord load the medium, but rather do this
1570 manually or by a program that reads from /dev/sr0.
1571 $ dd if=/dev/sr0 count=1 >/dev/null 2>&1
1572 $ msinfo=$(xorriso -as cdrecord dev=/dev/sr0 -msinfo)
1573 $ load_opts=
1574 $ test -n "$msinfo" && load_opts="-M /dev/sr0 -C $msinfo"
1575 $ xorrisofs $load_opts -o - --for_backup -m '*.o' -m '*.swp' \
1576 -V PROJ_MAIL_"$(date '+%Y_%m_%d_%H%M%S')" -graft-points \
1577 -old-root / \
1578 /projects=/home/thomas/projects \
1579 /personal_mail=/home/thomas/personal_mail \
1580 | xorriso -as cdrecord dev=/dev/sr0 -v -multi -waiti -eject -
1581 This makes sense if the full backup leaves substantial remaining
1583 capacity on media and if the expected changes are much smaller than the
1584 full backup.
1585 Better do not use your youngest backup for -old-root. Have at least
1587 two media which you use alternatingly. So only older backups get
1588 endangered by the new write operation, while the newest backup is
1589 stored safely on a different medium.
1590 Always have a blank medium ready to perform a full backup in case the
1591 update attempt fails due to insufficient remaining capacity. This
1592 failure will not spoil the old medium, of course.
1593 If inode numbers on disk are not persistent, then use option
1595 --old-root-no-ino . In this case an update run will compare recorded
1596 MD5 sums against the current file content on hard disk.
1597 With mount option -o "sbsector=" on GNU/Linux or -s on FreeBSD or
1599 NetBSD it is possible to access the session trees which represent the
1600 older backup versions. With CD media, GNU/Linux mount accepts session
1601 numbers directly by its option "session=".
1602 Multi-session media and most overwriteable media written by xorriso can
1603 tell the sbsectors of their sessions by xorriso option -toc:
1604 $ xorriso -dev /dev/sr0 -toc
1605 xorriso can print the matching mount command for a session number:
1606 $ xorriso -mount_cmd /dev/sr0 session 12 /mnt
1607 or for a volume id that matches a search expression:
1608 $ xorriso -mount_cmd /dev/sr0 volid '*2008_12_05*' /mnt
1609 Both yield on standard output something like:
1610 mount -t iso9660 -o nodev,noexec,nosuid,ro,sbsector=1460256
1611 '/dev/sr0' '/mnt'
1612 The superuser may let xorriso execute the mount command directly:
1613 # osirrox -mount /dev/sr0 "volid" '*2008_12_05*' /mnt
1614 Incremental backup with accumulated trees
1616 Solaris does not offer the option to mount older sessions. In order to
1617 keep them accessible, one may map all files to a file tree under a
1618 session directory and accumulate those directories from session to
1619 session. The -root tree is cloned from the -old-root tree before it
1620 gets compared with the appropriate trees on disk.
1621 This demands to know the previously used session directory name.
1622 With the first session:
1623 $ xorrisofs -root /session1 \
1624 -o - --for_backup -m '*.o' -m '*.swp' \
1625 -V PROJ_MAIL_"$(date '+%Y_%m_%d_%H%M%S')" -graft-points \
1626 /projects=/home/thomas/projects \
1627 /personal_mail=/home/thomas/personal_mail \
1628 | xorriso -as cdrecord dev=/dev/sr0 -v blank=as_needed \
1629 -multi -waiti -eject -
1630 With the second session, option -old-root refers to /session1 and the
1632 new -root is /session2.
1633 Do not let xorriso -as cdrecord load the medium, but rather do this
1634 manually or by a program that reads from /dev/sr0.
1635 $ dd if=/dev/sr0 count=1 >/dev/null 2>&1
1636 $ msinfo=$(xorriso -as cdrecord dev=/dev/sr0 -msinfo)
1637 $ load_opts=
1638 $ test -n "$msinfo" && load_opts="-M /dev/sr0 -C $msinfo"
1639 $ xorrisofs $load_opts -root /session2 -old-root /session1 \
1640 -o - --for_backup -m '*.o' -m '*.swp' \
1641 -V PROJ_MAIL_"$(date '+%Y_%m_%d_%H%M%S')" -graft-points \
1642 /projects=/home/thomas/projects \
1643 /personal_mail=/home/thomas/personal_mail \
1644 | xorriso -as cdrecord dev=/dev/sr0 -v -multi -waiti -eject -
1645 With the third session, option -old-root refers to /session2. The new
1646 -root is /session3. And so on.
1647 Create bootable images for PC-BIOS and EFI
1649 The SYSLINUX/ISOLINUX boot loader suite is popular for booting PC-BIOS.
1650 The ISOLINUX wiki prescribes to create on disk a directory ./CD_root
1651 and to copy all desired files underneath that directory. Especially
1652 file isolinux.bin shall be copied to ./CD_root/isolinux/isolinux.bin .
1653 This is the boot image file.
1654 The prescribed mkisofs options can be used unchanged with xorrisofs:
1655 $ xorrisofs -o output.iso \
1656 -b isolinux/isolinux.bin -c isolinux/boot.cat \
1657 -no-emul-boot -boot-load-size 4 -boot-info-table \
1658 ./CD_root
1659 Put it on CD by a burn program. E.g.:
1660 $ xorriso -as cdrecord -v dev=/dev/sr0 blank=as_needed output.iso
1661 The image from above example will boot from CD, DVD or BD, but not from
1663 USB stick or other hard-disk-like devices. This can be done by help of
1664 an isohybrid MBR. Syslinux provides matching template files as
1665 isohdp[fp]x*.bin . E.g. /usr/lib/syslinux/isohdpfx.bin .
1666 If a few hundred KB of size do not matter, then option
1667 -partition_offset can be used to create a partition table where
1668 partition 1 starts not at block 0. This facilitates later manipulations
1669 of the USB stick by tools for partitioning and formatting.
1670 The image from the following example will be prepared for booting via
1671 MBR and its first partition will start at hard disk block 64.
1672 It will also boot from optical media.
1673 $ xorrisofs -o output.iso \
1674 -b isolinux/isolinux.bin -c isolinux/boot.cat \
1675 -no-emul-boot -boot-load-size 4 -boot-info-table \
1676 -isohybrid-mbr /usr/lib/syslinux/isohdpfx.bin \
1677 -partition_offset 16 \
1678 ./CD_root
1679 Become superuser and copy the image to the unpartitioned base device
1680 file of the USB stick. On GNU/Linux this is e.g. /dev/sdb, not
1681 /dev/sdb1.
1682 CAUTION: This will overwrite any partitioning on the USB stick and make
1683 remaining data unaccessible.
1684 So first make sure you got the correct address of the intended device.
1685 E.g. by reading 100 MiB data from it and watching it blinking:
1686 # dd bs=2K if=/dev/sdb count=50K >/dev/null
1687 Now copy the image onto it
1688 # dd bs=2K if=output.iso of=/dev/sdb
1689 Now for EFI:
1691 The boot image file has to be the image of an EFI System Partition,
1692 i.e. a FAT filesystem with directory /EFI/BOOT and boot files with EFI
1693 prescribed names: BOOTIA32.EFI for 32 bit x86, BOOTx64.EFI for 64 bit
1694 AMD/x86 (in UEFI-2.4 there is indeed a lower case "x"), BOOTAA64.EFI
1695 for 64 bit ARM. The software in the FAT filesystem should be able to
1696 find and inspect the ISO filesystem for boot loader configuration and
1697 start of operating system. GRUB2 program grub-mkimage can produce such
1698 a FAT filesystem with suitable content, which then uses further GRUB2
1699 software from the ISO filesystem.
1700 EFI boot equipment may be combined with above ISOLINUX isohybrid for
1701 PC-BIOS in a not really UEFI-2.4 compliant way, which obviously works
1702 well. It yields MBR and GPT partition tables, both with nested
1703 partitions. Assumed the EFI System Partition image is ready as
1704 ./CD_root/boot/grub/efi.img, add the following options before the
1705 directory address ./CD_root:
1706 -eltorito-alt-boot -e 'boot/grub/efi.img' -no-emul-boot \
1707 -isohybrid-gpt-basdat \
1708 More compliant with UEFI-2.4 is to decide for either MBR or GPT and to
1709 append a copy of the EFI System Partition in order to avoid overlap of
1710 ISO partition and EFI partition. Here for MBR:
1711 -eltorito-alt-boot -e 'boot/grub/efi.img' -no-emul-boot \
1712 -append_partition 2 0xef ./CD_root/boot/grub/efi.img \
1713 The resulting ISOs are supposed to boot from optical media and USB
1714 stick. One may omit option -eltorito-alt-boot if no option -b is used
1715 to make the ISO bootable via PC-BIOS.
1716 For ISOs with pure GRUB2 boot equipment consider to use GRUB2 tool
1718 grub-mkrescue as frontend to xorrisofs.
1719 If you have a bootable ISO filesystem and want to know its equipment
1721 plus a proposal how to reproduce it, try:
1722 $ xorriso -hfsplus on -indev IMAGE.iso \
1723 -report_el_torito plain -report_system_area plain \
1724 -print "" -print "======= Proposal for xorrisofs options:" \
1725 -report_el_torito as_mkisofs
1726
1728 Startup files:
1729 If not --no_rc is given as the first argument then xorrisofs attempts
1730 on startup to read and execute lines from the following files:
1731 /etc/default/xorriso
1732 /etc/opt/xorriso/rc
1733 /etc/xorriso/xorriso.conf
1734 $HOME/.xorrisorc
1735 The files are read in the sequence given here, but none of them is
1736 required to exist. The lines are not interpreted as xorrisofs options
1737 but as generic xorriso commands. See man xorriso.
1738 After the xorriso startup files, the program tries one by one to open
1740 for reading:
1741 ./.mkisofsrc
1742 $MKISOFSRC
1743 $HOME/.mkisofsrc
1744 $(dirname $0)/.mkisofsrc
1745 On success it interprets the file content and does not try further
1746 files. The last address is used only if start argument 0 has a
1747 non-trivial dirname.
1748 The reader currently interprets the following NAME=VALUE pairs:
1749 APPI default for -A
1750 PUBL default for -publisher
1751 SYSI default for -sysid
1752 VOLI default for -V
1753 VOLS default for -volset
1754 Any other lines will be silently ignored.
1755
1757 The following environment variables influence the program behavior:
1758 HOME is used to find xorriso and mkisofs startup files.
1759 MKISOFSRC may be used to point the program to a mkisofs startup file.
1760 SOURCE_DATE_EPOCH belongs to the specs of reproducible-builds.org. It
1761 is supposed to be either undefined or to contain a decimal number which
1762 tells the seconds since january 1st 1970. If it contains a number, then
1763 it is used as time value to set the default of --modification-date=.
1764 --gpt_disk_guid defaults to "modification-date". The default of
1765 --set_all_file_dates is then "set_to_mtime".
1766 Startup files and program options can override the effect of
1767 SOURCE_DATE_EPOCH.
1768
1771 For generic xorriso command mode
1772 xorriso(1)
1773 For the cdrecord emulation of xorriso
1775 xorrecord(1)
1776 For mounting xorriso generated ISO 9660 images (-t iso9660)
1778 mount(8)
1779 Other programs which produce ISO 9660 images
1781 mkisofs(8), genisoimage(8)
1782 Programs which burn sessions to optical media
1784 growisofs(1), cdrecord(1), wodim(1), cdrskin(1), xorriso(1)
1785 ACL and xattr
1787 getfacl(1), setfacl(1), getfattr(1), setfattr(1)
1788 MD5 checksums
1790 md5sum(1)
1791 On FreeBSD the commands for xattr and MD5 differ
1793 getextattr(8), setextattr(8), md5(1)
1794
1796 To report bugs, request help, or suggest enhancements for xorriso,
1797 please send electronic mail to the public list <bug-xorriso@gnu.org>.
1798 If more privacy is desired, mail to <scdbackup@gmx.net>.
1799 Please describe what you expect xorriso to do, the program arguments or
1800 dialog commands by which you tried to achieve it, the messages of
1801 xorriso, and the undesirable outcome of your program run.
1802 Expect to get asked more questions before solutions can be proposed.
1803
1805 Thomas Schmitt <scdbackup@gmx.net>
1806 for libburnia-project.org
1807
1809 Copyright (c) 2011 - 2017 Thomas Schmitt
1810 Permission is granted to distribute this text freely. It shall only be
1811 modified in sync with the technical properties of xorriso. If you make
1812 use of the license to derive modified versions of xorriso then you are
1813 entitled to modify this text under that same license.
1814
1816 xorrisofs is in part based on work by Vreixo Formoso who provides
1817 libisofs together with Mario Danic who also leads the libburnia team.
1818 Vladimir Serbinenko contributed the HFS+ filesystem code and related
1819 knowledge.
1820 Compliments towards Joerg Schilling whose cdrtools served me for ten
1821 years.
1822 Version 1.4.8, Sep 12, 2017 XORRISOFS(1)