From 2c92ef960b30b6fc7c021a95ea80b7a02e5a0e8d Mon Sep 17 00:00:00 2001 From: Thomas Schmitt Date: Tue, 30 Jun 2015 14:41:14 +0000 Subject: [PATCH] Added EFI information to manual page example of bootable ISO --- xorriso/xorrisofs.1 | 64 +- xorriso/xorrisofs.info | 1847 +++++++++++++++++++--------------------- xorriso/xorrisofs.texi | 77 +- 3 files changed, 997 insertions(+), 991 deletions(-) diff --git a/xorriso/xorrisofs.1 b/xorriso/xorrisofs.1 index f7437d70..9d92cc6b 100644 --- a/xorriso/xorrisofs.1 +++ b/xorriso/xorrisofs.1 @@ -9,7 +9,7 @@ .\" First parameter, NAME, should be all caps .\" Second parameter, SECTION, should be 1-8, maybe w/ subsection .\" other parameters are allowed: see man(7), man(1) -.TH XORRISOFS 1 "Version 1.4.1, May 17, 2015" +.TH XORRISOFS 1 "Version 1.4.1, Jun 30, 2015" .\" Please adjust this date whenever revising the manpage. .\" .\" Some roff macros, for reference: @@ -928,13 +928,12 @@ entry. Up to 32 catalog entries are possible. Specify the boot image file which shall be mentioned in the current entry of the El Torito boot catalog. It will be marked as suitable for EFI. .br -Normally no other El Torito options should be used with the catalog entry -that points to an EFI image. -Consider to use \-\-efi\-boot rather than \-e. +Option \-e should be followed by option \-no\-emul\-boot and no other El Torito +options before an eventual \-eltorito\-alt\-boot. .TP \fB--efi-boot\fR iso_rr_path Perform \-eltorito\-alt\-boot, option \-e with the given -iso_rr_path, and again \-eltorito\-alt\-boot. This gesture is +iso_rr_path, \-no\-emul\-boot, and again \-eltorito\-alt\-boot. This gesture is used for achieving EFI\-bootability of the GRUB2 rescue CD. .TP \fB\-boot-load-size\fR number @@ -1512,7 +1511,7 @@ Incremental backup of a few directory trees .br Incremental backup with accumulated trees .br -Create bootable images for PC-BIOS +Create bootable images for PC-BIOS and EFI .br .SS .B A simple image production run @@ -1788,7 +1787,8 @@ but rather do this manually or by a program that reads from /dev/sr0. With the third session, option \-old\-root refers to /session2. The new \-root is /session3. And so on. .SS -.B Create bootable images for PC-BIOS +.B Create bootable images for PC-BIOS and EFI +The SYSLINUX/ISOLINUX boot loader suite is popular for booting PC\-BIOS. The ISOLINUX wiki prescribes to create on disk a directory ./CD_root and to copy all desired files underneath that directory. Especially file isolinux.bin shall be copied to ./CD_root/isolinux/isolinux.bin . @@ -1820,7 +1820,7 @@ at block 0. This facilitates later manipulations of the USB stick by tools for partitioning and formatting. .br The image from the following example will be prepared for booting via MBR -and its first parttion will start at hard disk block 64. +and its first partition will start at hard disk block 64. .br It will also boot from optical media. .br @@ -1852,6 +1852,54 @@ Now copy the image onto it .br # dd bs=2K if=output.iso of=/dev/sdb .br +.sp 1 +Now for EFI: +.br +The boot image file has to be the image of an EFI System Partition, +i.e. a FAT filesystem with directory /EFI/BOOT and boot files with +EFI prescribed names: BOOTIA32.EFI for 32 bit x86, +BOOTx64.EFI for 64 bit AMD/x86 (in UEFI\-2.4 there is indeed a lower case "x"), +BOOTAA64.EFI for 64 bit ARM. The software in the FAT filesystem should be +able to find and inspect the ISO filesystem for boot loader configuration and +start of operating system. GRUB2 program grub\-mkimage can produce such a +FAT filesystem with suitable content, which then uses further GRUB2 +software from the ISO filesystem. +.br +EFI boot equipment may be combined with above ISOLINUX isohybrid for PC\-BIOS +in a not really UEFI\-2.4 compliant way, which obviously works well. It yields +MBR and GPT partition tables, both with nested partitions. +Assumed the EFI System Partition image is ready as ./CD_root/boot/grub/efi.img, +add the following options before the directory address ./CD_root: +.br + \-eltorito\-alt\-boot \-e 'boot/grub/efi.img' \-no\-emul\-boot \\ +.br + \-isohybrid\-gpt\-basdat \\ +.br +More compliant with UEFI\-2.4 is to decide for either MBR or GPT and to +append a copy of the EFI System Partition in order to avoid overlap of +ISO partition and EFI partition. Here for MBR: +.br + \-eltorito\-alt\-boot \-e 'boot/grub/efi.img' \-no\-emul\-boot \\ + \-append_partition 2 0xef ./CD_root/boot/grub/efi.img \\ +.br +The resulting ISOs are supposed to boot from optical media and USB stick. +One may omit option \-eltorito\-alt\-boot if no option \-b is used to make +the ISO bootable via PC\-BIOS. +.br +.sp 1 +For ISOs with pure GRUB2 boot equipment consider to use GRUB2 tool +grub\-mkrescue as frontend to xorrisofs. +.br +.sp 1 +If you have a bootable ISO filesystem and want to know its equipment plus +a proposal how to reproduce it, try: +.br + $ xorriso \-hfsplus on \-indev IMAGE.iso \\ + \-report_el_torito plain \-report_system_area plain \\ + \-print "" \-print "======= Proposal for xorrisofs options:" \\ + \-report_el_torito as_mkisofs +.br +.br .SH FILES .SS .B Startup files: diff --git a/xorriso/xorrisofs.info b/xorriso/xorrisofs.info index 52990448..223d3b8f 100644 --- a/xorriso/xorrisofs.info +++ b/xorriso/xorrisofs.info @@ -1,15 +1,15 @@ -This is xorrisofs.info, produced by makeinfo version 4.8 from -./xorrisofs.texi. +This is xorrisofs.info, produced by makeinfo version 5.2 from +xorrisofs.texi. -INFO-DIR-SECTION Archiving -START-INFO-DIR-ENTRY -* Xorrisofs: (xorrisofs). Emulates ISO 9660 program mkisofs -END-INFO-DIR-ENTRY - xorrisofs - Emulation of ISO 9660 program mkisofs by program xorriso +xorrisofs - Emulation of ISO 9660 program mkisofs by program xorriso Copyright (C) 2011 - 2015 Thomas Schmitt Permission is granted to distrubute this text freely. +INFO-DIR-SECTION Archiving +START-INFO-DIR-ENTRY +* Xorrisofs: (xorrisofs). Emulates ISO 9660 program mkisofs +END-INFO-DIR-ENTRY  File: xorrisofs.info, Node: Top, Next: Overview, Up: (dir) @@ -17,8 +17,7 @@ File: xorrisofs.info, Node: Top, Next: Overview, Up: (dir) xorrisofs 1.4.1 *************** -xorrisofs - Emulation of ISO 9660 program mkisofs by program xorriso - +xorrisofs - Emulation of ISO 9660 program mkisofs by program xorriso * Menu: * Overview:: Overview @@ -40,11 +39,11 @@ File: xorrisofs.info, Node: Overview, Next: Standards, Prev: Top, Up: Top 1 Overview ********** -`xorrisofs' produces Rock Ridge enhanced ISO 9660 filesystems and -add-on sessions to such filesystems. Optionally it can produce Joliet +'xorrisofs' produces Rock Ridge enhanced ISO 9660 filesystems and add-on +sessions to such filesystems. Optionally it can produce Joliet directory trees too. -`xorrisofs' understands options of program mkisofs from cdrtools by + 'xorrisofs' understands options of program mkisofs from cdrtools by Joerg Schilling. Its implementation is part of program xorriso which shares no source code with cdrtools. @@ -55,35 +54,35 @@ File: xorrisofs.info, Node: Standards, Next: Insert, Prev: Overview, Up: Top ************************************ *ISO 9660* (aka *ECMA-119*) is a read-only filesystem that is mainly -used for optical media CD, DVD, BD, but may also reside on other -storage devices like disk files, USB sticks or disk partitions. It is -widely readable by many operating systems and by boot facilities of -personal computers. +used for optical media CD, DVD, BD, but may also reside on other storage +devices like disk files, USB sticks or disk partitions. It is widely +readable by many operating systems and by boot facilities of personal +computers. ISO 9660 describes directories and data files by very restricted filenames with no distinction of upper case and lower case. Its metadata do not comply to fundamental POSIX specifications. *Rock Ridge* is the name of a set of additional information which enhance an ISO 9660 filesystem so that it can represent a POSIX -compliant filesystem with ownership, access permissions, symbolic -links, and other attributes. Rock Ridge allows filenames of up to 255 -bytes and paths of up to 1024 bytes. -xorrisofs produces Rock Ridge information by default. It is strongly +compliant filesystem with ownership, access permissions, symbolic links, +and other attributes. Rock Ridge allows filenames of up to 255 bytes +and paths of up to 1024 bytes. +xorrisofs produces Rock Ridge information by default. It is strongly discouraged to disable this feature. *Joliet* is the name of an additional directory tree which provides filenames up to 64 characters encoded as UTF-16. A Joliet tree is mainly interesting for reading the ISO image by operating systems of -Microsoft Corporation. Production of this directory tree may be -enabled by option -J. +Microsoft Corporation. Production of this directory tree may be enabled +by option -J. *ISO 9660:1999* is the name of an additional directory tree which -provides longer filenames. It allows single file names to have up to +provides longer filenames. It allows single file names to have up to 207 characters. It might be of use with some older computer system boot facilities which read neither Rock Ridge nor Joliet but need longer filenames nevertheless. Production of this directory tree may be enabled by option -iso-level 4. *HFS+* is the name of a filesystem which is normally used for writing -and reading on hard disks and similar devices. It is possible to embed +and reading on hard disks and similar devices. It is possible to embed a HFS+ partition into the emerging ISO 9660 image and to mark it by -Apple Partition Map entries. This interferes with options which copy +Apple Partition Map entries. This interferes with options which copy data into the first 32 KiB of the ISO image, like -G or -isohybrid-mbr. See option -hfsplus. The main purpose for having an embedded HFS+ partition is booting of @@ -95,30 +94,30 @@ File: xorrisofs.info, Node: Insert, Next: Xorriso, Prev: Standards, Up: Top 3 Inserting files into the ISO image ************************************ -`xorrisofs' deals with two kinds of file addresses: +'xorrisofs' deals with two kinds of file addresses: *disk_path* is a path to an object in the local filesystem tree. *iso_rr_path* is the Rock Ridge address of a file object in the ISO -image. If no Rock Ridge information shall be stored in an emerging -ISO, then the names will get mapped to ISO 9660 names of limited length -and character set. +image. If no Rock Ridge information shall be stored in an emerging ISO, +then the names will get mapped to ISO 9660 names of limited length and +character set. -A program argument is handled as a *pathspec*, if it is not recognized -as original mkisofs option or additional `xorrisofs' option. A -pathspec depicts an input file object by a disk_path. If option --graft-points is not present, then the behavior depends on the file -type of disk_path. Directories get merged with the /-directory of the -ISO image. Files of other types get copied into the /-directory. + A program argument is handled as a *pathspec*, if it is not +recognized as original mkisofs option or additional 'xorrisofs' option. +A pathspec depicts an input file object by a disk_path. If option +-graft-points is not present, then the behavior depends on the file type +of disk_path. Directories get merged with the /-directory of the ISO +image. Files of other types get copied into the /-directory. If -graft-points is present then each pathspec gets split at the first occurence of the =-character. The part before the = is taken as -*target*, i.e. the iso_rr_path for the file object in the ISO image. -The part after the first = is taken as *source*, i.e. the disk_path of +*target*, i.e. the iso_rr_path for the file object in the ISO image. +The part after the first = is taken as *source*, i.e. the disk_path of the input object. It is possible to make =-characters part of the iso_rr_path by preceding -them with a \-character. The same must be done for \-characters which +them with a \-character. The same must be done for \-characters which shall be part of the iso_rr_path. -If the source part of the pathspec leads to a directory, then all files -underneath this directory get inserted into the image, too. It is + If the source part of the pathspec leads to a directory, then all +files underneath this directory get inserted into the image, too. It is possible to exclude particular files from being inserted by help of option -m. In case that target already exists, the following rules apply: @@ -132,23 +131,23 @@ File: xorrisofs.info, Node: Xorriso, Next: Options, Prev: Insert, Up: Top 4 Relation to program xorriso ***************************** -`xorrisofs' is actually a command mode of program *xorriso*, which gets +'xorrisofs' is actually a command mode of program *xorriso*, which gets entered either by xorriso command "-as mkisofs" or by starting the program by one of the names "xorrisofs", "mkisofs", "genisoimage", or "genisofs". This command mode can be left by argument "--" which leads to generic -xorriso command mode. See *man xorriso* for its description. +xorriso command mode. See *man xorriso* for its description. -xorriso performs image reading and writing by help of libburn, which is -mainly intended for optical drives, but also operates on all POSIX file -types except directories. -The program messages call any image file a "drive". File types which -are not supported for reading are reported as "blank". The reported + xorriso performs image reading and writing by help of libburn, which +is mainly intended for optical drives, but also operates on all POSIX +file types except directories. +The program messages call any image file a "drive". File types which +are not supported for reading are reported as "blank". The reported free media space may be quite fictional. -Nevertheless `xorrisofs' does not operate directly on optical drives, +Nevertheless 'xorrisofs' does not operate directly on optical drives, but rather forces libburn to regard them as general device files. So for writing of sequential optical media (CD, DVD-R, DVD+R, BD-R) one -will have to use a burn program. E.g the cdrecord emulation of xorriso. +will have to use a burn program. E.g the cdrecord emulation of xorriso. See EXAMPLES.  @@ -190,37 +189,33 @@ then a new image is composed from scratch. A special kind of pseudo disk_path has the form "/dev/fd/"number. It depicts the open file descriptor with the given number, regardless whether the operating system supports this feature by - file nodes in /dev/fd or not. E.g. /dev/fd/3 is file descriptor 3 + file nodes in /dev/fd or not. E.g. /dev/fd/3 is file descriptor 3 which was opened by the program that later started xorriso. - -prev-session disk_path Alias of -M. - -dev disk_path Alias of -M. - -C last_session_start,next_writeable_address Set the 2 KiB block address last_session_start from where to read the ISO image out of the file given by option -M. Separated by a comma, set the next_writeable_address to which the - add-on session will finally be written. Decisive is actually the + add-on session will finally be written. Decisive is actually the block address which the intended readers will have to use as superblock address on the intended medium. Both values can be inquired from optical media by help of burn - programs and cdrecord option -msinfo. xorriso itself can obtain it - in its cdrecord emulation. Do not let it load the drive, but + programs and cdrecord option -msinfo. xorriso itself can obtain it + in its cdrecord emulation. Do not let it load the drive, but rather do this manually or by a program like dd which reads a few - bytes. Only then it is sure that the device driver knows the true + bytes. Only then it is sure that the device driver knows the true readable size of the medium. - dd if=/dev/... count=1 >/dev/null 2>&1 - values=$(xorriso -as cdrecord dev=/dev/... -msinfo) + dd if=/dev/... count=1 >/dev/null 2>&1 + values=$(xorriso -as cdrecord dev=/dev/... -msinfo) echo $values Option -C may be used without option -M to create an ISO image from scratch and prepare it for being finally written to a block address - other than 0. Parameter last_session_start must then be set to 0. - + other than 0. Parameter last_session_start must then be set to 0. -cdrecord-params last_session_start,next_writeable_address Alias of -C. @@ -233,80 +228,69 @@ File: xorrisofs.info, Node: SetInsert, Next: SetProduct, Prev: Loading, Up: -path-list disk_path Read pathspecs line-by-line from disk_file and insert the depicted - file objects into the ISO image. If disk_path is "-" then read the + file objects into the ISO image. If disk_path is "-" then read the pathspecs from standard input. - --quoted_path_list disk_path Like option -path-list but reading quoted words rather than plain - lines. Whitespace outside of quotes will be discarded. On the + lines. Whitespace outside of quotes will be discarded. On the other hand it is possible to represent pathspecs which contain newline characters. The double quotation mark " and the single quotation mark ' can be - used to enclose whitespace and make it part of pathspecs. Each mark - type can enclose the marks of the other type. A trailing backslash - \ outside quotations or an open quotation cause the next input - line to be appended. - + used to enclose whitespace and make it part of pathspecs. Each + mark type can enclose the marks of the other type. A trailing + backslash \ outside quotations or an open quotation cause the next + input line to be appended. -f + Resolve symbolic links on disk rather than storing them as symbolic links in the ISO image. - -follow-links Alias of -f. - -graft-points Enable interpretation of input file pathspecs as combination of iso_rr_path and disk_path, separated by a =-character. - -m disk_pattern - Exclude files from being inserted into the image. Silently ignored + Exclude files from being inserted into the image. Silently ignored are those files of which the disk_path matches the given shell parser pattern. If no /-character is part of the pattern, then it gets matched against the leaf name of the disk file. It is possible to give more than one -m option. - -exclude Alias of -m. - -x - Alias of -m. + Alias of -m. -old-exclude Alias of -m. - -exclude-list disk_path Perform -m using each line out of file disk_path as argument disk_pattern. - -z + Enable recognition and proper processing of zisofs compressed files - as produced by program mkzftree. These files will get equipped + as produced by program mkzftree. These files will get equipped with the necessary meta data so that a Linux kernel will recognize them and deliver their content in uncompressed form. - -transparent-compression Alias of -z. - -root iso_rr_path - Insert all files under the given iso_rr_path. If option + Insert all files under the given iso_rr_path. If option -graft-points is given, then iso_rr_path is prepended to each target part of a pathspec. The default for -root is "/". - -old-root iso_rr_path Enable incremental insertion of files into the loaded image. The effective target and source addresses of given pathspecs get compared whether the target already exists in the ISO image and is - still identical to the source on disk. Metadata in the ISO image + still identical to the source on disk. Metadata in the ISO image will get adjusted, if they differ from those on disk. New files and files with changed content will get newly added. Target files which do not exist in any of the according pathspec sources will get removed from the ISO directory tree. If the effective setting of -root differs from the iso_rr_path given with -old-root, then the files underneath the -old-root - directory get cloned underneath the -root directory. Cloning + directory get cloned underneath the -root directory. Cloning happens before file comparison. - --old-root-no-ino Disable recording and use of disk inode numbers. If no disk inode numbers are recorded, then option -old-root will have to read disk @@ -315,19 +299,16 @@ File: xorrisofs.info, Node: SetInsert, Next: SetProduct, Prev: Loading, Up: With recorded disk inode numbers and with credible ctime and mtime, it is possible to detect potential changes in the content without actually reading it. A loophole remains if multiple different - filesystems may get mounted at the same directory, like it is - habit with /mnt. In this case one has to use option - --old-root-devno or disable the inode number shortcut by - --old-root-no-ino. - + filesystems may get mounted at the same directory, like it is habit + with /mnt. In this case one has to use option --old-root-devno or + disable the inode number shortcut by --old-root-no-ino. --old-root-devno Enable comparison of recorded device numbers together with recorded - inode numbers. This works only with good old stable device numbers - which get out of fashion, regrettably. If the hard disk has a + inode numbers. This works only with good old stable device numbers + which get out of fashion, regrettably. If the hard disk has a different device number after each reboot, then this comparison - will see all files as changed and thus prevent any incremental - size saving. - + will see all files as changed and thus prevent any incremental size + saving. --old-root-no-md5 Disable recording and use of MD5 checksums for data file content. If neither checksums and nor disk inode numbers are recorded, then @@ -344,61 +325,54 @@ File: xorrisofs.info, Node: SetProduct, Next: SetCompl, Prev: SetInsert, Up: -o disk_path Set the output file address for the emerging ISO image. If the address exists as regular file, it will be truncated to length 0 - when image production begins. It may not already exist as - directory. If it does not exist yet then its parent directory - must exist and a regular file will get created. + when image production begins. It may not already exist as + directory. If it does not exist yet then its parent directory must + exist and a regular file will get created. A special kind of pseudo disk_path has the form "/dev/fd/"number. It depicts the open file descriptor with the given number, regardless whether the operating system supports this feature by - file nodes in /dev/fd or not. E.g. /dev/fd/4 is file descriptor 4 + file nodes in /dev/fd or not. E.g. /dev/fd/4 is file descriptor 4 which was opened by the program that later started xorriso. Default is standard output (/dev/fd/1) which may also be set by disk_path "-". - -output disk_path Alias of -o. - --stdio_sync "on"|"off"|"end"|number Set the number of bytes after which to force output to disk in order to keep the memory from being clogged with lots of pending - data for slow devices. "on" is the same as "16m". Forced output - can be disabled by "off", or be delayed by "end" until all data - are produced. If a number is chosen, then it must be at least 64k. + data for slow devices. "on" is the same as "16m". Forced output + can be disabled by "off", or be delayed by "end" until all data are + produced. If a number is chosen, then it must be at least 64k. The default with xorriso mkisofs emulation is --stdio_sync "off". xorriso uses an inner fifo buffer with default size 4 MiB. So - forcing the operating system i/o cache to disk does not - necessarily block the simultaneous production of more image - content. - + forcing the operating system i/o cache to disk does not necessarily + block the simultaneous production of more image content. --emul-toc Write a second superblock with the first session into random-access - files. If further sessions get appended and the first superblock + files. If further sessions get appended and the first superblock gets updated, then the second superblock will not be overwritten. This allows to still mount the first session and to find the start blocks of the further sessions. - The price is 64 KiB extra space consumption. If -partition_offset + The price is 64 KiB extra space consumption. If -partition_offset is non-zero, then it is 128 KiB plus twice the partition setup. - --no-emul-toc Do not write a second superblock with the first session into random-access files. This is the default. - --sort-weight weight_number iso_rr_path - Attribute a LBA weight number to regular files. If iso_rr_path - leads to a directory then all regular files underneath will get - the weight_number. + Attribute a LBA weight number to regular files. If iso_rr_path + leads to a directory then all regular files underneath will get the + weight_number. The weight_number may range from -2147483648 to 2147483647. The higher it is, the lower will be the block address of the file data in the emerging ISO image. Currently the El Torito boot catalog - has a hardcoded weight of 1 billion. Normally it should occupy - the block with the lowest possible address. Data files get added - or loaded with initial weight 0. Boot image files have a default + has a hardcoded weight of 1 billion. Normally it should occupy the + block with the lowest possible address. Data files get added or + loaded with initial weight 0. Boot image files have a default weight of 2. - --sort-weight-list disk_path Read pairs of weight number and iso_rr_path from a file of the - local filesystem. Apply each pair like with --sort-weight. + local filesystem. Apply each pair like with --sort-weight. Only the last --sort-weight-list or --sort-weight-patterns of a xorrisofs run gets into effect. The weight number is read from the start of the line. The @@ -407,8 +381,8 @@ File: xorrisofs.info, Node: SetProduct, Next: SetCompl, Prev: SetInsert, Up: Notes for the case that this feature is used within a sequence of generic xorriso commands (not an issue with a pure mkisofs emulation run): - The addressed files must already be in the ISO image model when - you execute + The addressed files must already be in the ISO image model when you + execute -as mkisofs --sort-weight-list disk_path -- Several such commands may be used to apply more than one weight file. @@ -416,35 +390,30 @@ File: xorrisofs.info, Node: SetProduct, Next: SetCompl, Prev: SetInsert, Up: 1 and 2 exp 28 = 268,435,456, depending on their block address. This shall keep them roughly in the same order if the write method of modifying is applied. - --sort-weight-patterns disk_path Like --sort-weight-list , but expanding the iso_rr_paths as shell parser patterns and applying --sort-weight to each matching file. - -dir-mode mode Set the access permissions for all directories in the image to the given mode which is either an octal number beginning with "0" or a - comma separated list of statements of the form - [ugoa]*[+-=][rwxst]* . E.g. ug=rx,a-rwx - + comma separated list of statements of the form [ugoa]*[+-=][rwxst]* + . E.g. ug=rx,a-rwx -file-mode mode Like -dir-mode but for all regular data files in the image. - -pad - Add 300 KiB to the end of the produced ISO image. This circumvents - possible read errors from ISO images which have been written to CD - media in TAO mode. The additional bytes are claimed as part of - the ISO image if not -emul-toc is given. - Option -pad is the default. + Add 300 KiB to the end of the produced ISO image. This circumvents + possible read errors from ISO images which have been written to CD + media in TAO mode. The additional bytes are claimed as part of the + ISO image if not -emul-toc is given. + Option -pad is the default. -no-pad Disable padding of 300 KiB to the end of the produced ISO image. This is safe if the image is not meant to be written on CD or if it gets written to CD as only track in write mode SAO. - --old-empty - Use the old way of of giving block addresses in the range of - [0,31] to files with no own data content. The new way is to have a + Use the old way of of giving block addresses in the range of [0,31] + to files with no own data content. The new way is to have a dedicated block to which all such files will point.  @@ -456,73 +425,65 @@ File: xorrisofs.info, Node: SetCompl, Next: SetExtras, Prev: SetProduct, Up: -iso-level number Specify the ISO 9660 version which defines the limitations of file - naming and data file size. The naming restrictions do not apply to + naming and data file size. The naming restrictions do not apply to the Rock Ridge names but only to the low-level ISO 9660 names. There are three conformance levels: Level 1 allows ISO names of the form 8.3 and file size up to 4 GiB - 1. Level 2 allows ISO names with up to 32 characters and file size up to 4 GiB - 1. - Level 3 allows ISO names with up to 32 characters and file size - of up to 400 GiB - 200 KiB. (This size limitation is set by the - xorriso implementation and not by ISO 9660 which would allow - nearly 8 TiB.) + Level 3 allows ISO names with up to 32 characters and file size of + up to 400 GiB - 200 KiB. (This size limitation is set by the + xorriso implementation and not by ISO 9660 which would allow nearly + 8 TiB.) Pseudo-level 4 enables production of an additional ISO 9660:1999 directory tree. - -disallow_dir_id_ext Do not follow a bad habit of mkisofs which allows dots in the ISO - names of directories. On the other hand, some bootable GNU/Linux + names of directories. On the other hand, some bootable GNU/Linux images depend on this bad habit. - -U + This option allows ISO file names without dot and up to 37 characters, ISO file paths longer than 255 characters, and all - ASCII characters in file names. Further it omits the semicolon and + ASCII characters in file names. Further it omits the semicolon and the version numbers at the end of ISO names. This all violates ISO 9660 specs. - -untranslated-filenames Alias of -U. - -untranslated_name_len number Allow ISO file names up to the given number of characters without - any character conversion. The maximum number is 96. If a file + any character conversion. The maximum number is 96. If a file name has more characters, then image production will fail deliberately. This violates ISO 9660 specs. - -allow-lowercase Allow lowercase character in ISO file names. This violates ISO 9660 specs. - -relaxed-filenames Allow nearly all 7-bit characters in ISO file names. Not allowed - are 0x0 and '/'. If not option -allow-lowercase is given, then + are 0x0 and '/'. If not option -allow-lowercase is given, then lowercase letters get converted to uppercase. This violates ISO 9660 specs. - -d + Do not add trailing dot to ISO file names without dot. This violates ISO 9660 specs. - -omit-period Alias of -d. - -l - Allow up to 31 characters in ISO file names. + Allow up to 31 characters in ISO file names. -full-iso9660-filenames Alias of -l. - -max-iso9660-filenames Allow up to 37 characters in ISO file names. This violates ISO 9660 specs. - -N - Omit the semicolon and the version numbers at the end of ISO names. - This violates ISO 9660 specs. + Omit the semicolon and the version numbers at the end of ISO names. + + This violates ISO 9660 specs. -omit-version-number Alias of -N. @@ -534,127 +495,116 @@ File: xorrisofs.info, Node: SetExtras, Next: SetHide, Prev: SetCompl, Up: Op -R - With mkisofs this option enables Rock Ridge extensions. `xorrisofs' - produces them by default. It is strongly discouraged to disable - them by option --norock. + With mkisofs this option enables Rock Ridge extensions. + 'xorrisofs' produces them by default. It is strongly discouraged + to disable them by option --norock. -rock - Alias of -R. + Alias of -R. -r + Set Rock Ridge user and group id of all files in the ISO image to - 0. Grant r-permissions to all. Deny all w-permissions. If any + 0. Grant r-permissions to all. Deny all w-permissions. If any x-permission is set, grant x-permission to all. Remove s-bit and t-bit. - -rational-rock Alias of -r. - --norock - This option disables the production of Rock Ridge extensions for - the ISO 9660 file objects. The multi-session capabilities of - `xorrisofs' depend much on the naming fidelity of Rock Ridge. So - it is strongly discouraged to disable it by this option. + This option disables the production of Rock Ridge extensions for + the ISO 9660 file objects. The multi-session capabilities of + 'xorrisofs' depend much on the naming fidelity of Rock Ridge. So + it is strongly discouraged to disable it by this option. -D The standard ECMA-119 demands that no path in the image shall have - more than 8 name components or 255 characters. Therefore it would + more than 8 name components or 255 characters. Therefore it would be necessary to move deeper directory trees to a higher directory. - Rock Ridge offers an opportunity to let these relocated - directories appear at their orginal deep position, but this - feature might not be implemented properly by operating systems - which mount the image. + Rock Ridge offers an opportunity to let these relocated directories + appear at their orginal deep position, but this feature might not + be implemented properly by operating systems which mount the image. + Option -D disables this deep directory relocation, and thus violates ISO 9660 specs. - xorrisofs has -D set by default. If given explicitely then it + xorrisofs has -D set by default. If given explicitely then it overrides the options -rr_reloc_dir and -hide-rr-moved. - -disable-deep-relocation Alias of -D. - -rr_reloc_dir name Enable the relocation of deep directories and thus avoid ECMA-119 file paths of more than 8 name components or 255 characters. Directories which lead to such file paths will get moved to a - directory in the root directory of the image. Its name gets set by + directory in the root directory of the image. Its name gets set by this option. It is permissible to use the root directory itself. The overall directory tree will appear originally deep when - interpreted as Rock Ridge tree. It will appear as re-arranged if + interpreted as Rock Ridge tree. It will appear as re-arranged if only ECMA-119 information is considered. If the given relocation target directory does not already exist when image production begins, then it will get created and marked - for Rock Ridge as relocation artefact. At least on GNU/Linux it + for Rock Ridge as relocation artefact. At least on GNU/Linux it will not be displayed in mounted Rock Ridge images. - The name must not contain a '/' character after its first - character and it must not be longer than 255 bytes. + The name must not contain a '/' character after its first character + and it must not be longer than 255 bytes. This option has no effect if option -D is present. - -hide-rr-moved Alias of -rr_reloc_dir "/.rr_moved" - --for_backup Enable options which improve backup fidelity: --acl, --xattr, --md5, --hardlinks. - --acl - Enable recording and loading of ACLs from GNU/Linux or FreeBSD - (see man getfacl, man acl). They will not be in effect with - mounted ISO images. But xorriso can restore them on the same - systems when extracting files from the ISO image. + Enable recording and loading of ACLs from GNU/Linux or FreeBSD (see + man getfacl, man acl). They will not be in effect with mounted ISO + images. But xorriso can restore them on the same systems when + extracting files from the ISO image. --xattr + Enable recording and loading of GNU/Linux or FreeBSD extended attributes in user namespace (see man getfattr, man attr, resp. man getextattr, man 9 extattr). They will not be in effect with - mounted ISO images. But xorriso can restore them on the same + mounted ISO images. But xorriso can restore them on the same systems when extracting files from the ISO image. - --md5 - Enable recording of MD5 checksums for the overall ISO image and - for each single data file in the image. xorriso can check the - content of an ISO image with these sums and raise alert on - mismatch. See man xorriso, options -check_media, check_md5_r. - xorriso can print recorded MD5 checksums. E.g. by: - -find / -exec get_md5 + Enable recording of MD5 checksums for the overall ISO image and for + each single data file in the image. xorriso can check the content + of an ISO image with these sums and raise alert on mismatch. See + man xorriso, options -check_media, check_md5_r. xorriso can print + recorded MD5 checksums. E.g. by: + -find / -exec get_md5 --hardlinks Enable loading and recording of hardlink relations. Search for families of iso_rr files which stem from the same disk file, have identical content filtering and have identical properties. The members of each family get the same inode number in the ISO image. Whether these numbers are respected at mount time depends on the - operating system. xorriso can create hardlink families when + operating system. xorriso can create hardlink families when extracting files from the ISO image. - --scdbackup_tag disk_path record_name - Append a scdbackup checksum record to the image. This works only + Append a scdbackup checksum record to the image. This works only if the parameter next_writeable_address of option -C is 0. If disk_path is not an empty string, then append a scdbackup checksum - record to the end of this file. record_name is a word that gets + record to the end of this file. record_name is a word that gets part of tag and record. Program scdbackup_verify will recognize and verify tag resp. record. - -J + Enable the production of an additional Joliet directory tree along with the ISO 9660 Rock Ridge tree. - -joliet Alias of -J. - -joliet-long Allow 103 characters in Joliet file names rather than 64 as is - prescribed by the specification. Allow Joliet paths longer than + prescribed by the specification. Allow Joliet paths longer than the prescribed limit of 240 characters. - Oversized names get truncated. Without this option, oversized + Oversized names get truncated. Without this option, oversized paths get excluded from the Joliet tree. - -joliet-utf16 Encode Joliet file names in UTF-16BE rather than UCS-2. The difference is with characters which are not present in UCS-2 and get encoded in UTF-16 by 2 words of 16 bit each. Both words then stem from a reserved subset of UCS-2. - -hfsplus Enable the production of an additional HFS+ filesystem inside the ISO 9660 image and mark it by Apple Partition Map (APM) entries in @@ -666,56 +616,49 @@ File: xorrisofs.info, Node: SetExtras, Next: SetHide, Prev: SetCompl, Up: Op machine code without negative effects. So if an MBR gets combined with this feature, then its first 8 bytes should contain no essential commands. - The next blocks of 2 KiB in the System Area will be occupied by - APM entries. The first one covers the part of the ISO image - before the HFS+ filesystem metadata. The second one marks the - range from HFS+ metadata to the end of file content data. If more - ISO image data follow, then a third partition entry gets produced. - Other features of xorriso might cause the need for more APM - entries. + The next blocks of 2 KiB in the System Area will be occupied by APM + entries. The first one covers the part of the ISO image before the + HFS+ filesystem metadata. The second one marks the range from HFS+ + metadata to the end of file content data. If more ISO image data + follow, then a third partition entry gets produced. Other features + of xorriso might cause the need for more APM entries. Be aware that HFS+ is case-insensitive although it can record file - names with upper-case and lower-case letters. Therefore, file + names with upper-case and lower-case letters. Therefore, file names from the iso_rr name tree may collide in the HFS+ name tree. In this case they get changed by adding underscore characters and - counting numbers. In case of very long names, it might be + counting numbers. In case of very long names, it might be necessary to map them to "MANGLED_...". - -hfsplus-serial-no Set a string of 16 digits "0" to "9" and letters "a" to "f", which will be used as unique serial number of an emerging HFS+ filesystem. - -hfsplus-block-size number Set the allocation block size to be used when producing HFS+ - filesystems. Permissible are 512, 2048, or 0. The latter lets the + filesystems. Permissible are 512, 2048, or 0. The latter lets the program decide. - -apm-block-size number Set the block size to be used when describing partitions by an - Apple Partition Map. Permissible are 512, 2048, or 0. The latter + Apple Partition Map. Permissible are 512, 2048, or 0. The latter lets the program decide. Note that size 512 is not compatible with production of GPT, and that size 2048 will not be mountable -t hfsplus at least by older Linux kernels. - -hfsplus-file-creator-type creator type iso_rr_path Set the HFS+ creator and type attributes of a file in the emerging image. These are two codes of 4 characters each. - -hfs-bless-by blessing iso_rr_path - Issue a HFS+ blessing. They are roles which can be attributed to + Issue a HFS+ blessing. They are roles which can be attributed to up to four directories and a data file: "ppc_bootdir", "intel_bootfile", "show_folder", "os9_folder", "osx_folder". They may be abbreviated as "p", "i", "s", "9", and "x". Each such role can be attributed to at most one file object. - "intel_bootfile" is the one that would apply to a data file. All - others apply to directories. No file object can bear more than - one blessing. - + "intel_bootfile" is the one that would apply to a data file. All + others apply to directories. No file object can bear more than one + blessing. -hfs-bless disk_path - Issue HFS+ blessing "ppc_bootdir" to the directory which stems - from the directory disk_path in the local filesystem tree. + Issue HFS+ blessing "ppc_bootdir" to the directory which stems from + the directory disk_path in the local filesystem tree. This works only if there is at least one data file underneath the directory. disk_path can become ambigous if files from different local filesystem sub-trees are put into the same sub-tree of the @@ -733,27 +676,22 @@ File: xorrisofs.info, Node: SetHide, Next: ImageId, Prev: SetExtras, Up: Opt Make files invisible in the directory tree of ISO 9660 and Rock Ridge, if their disk_path matches the given shell parser pattern. The data content of such hidden files will be included in the - resulting image, even if they do not show up in any directory. - But you will need own means to find nameless data in the image. + resulting image, even if they do not show up in any directory. But + you will need own means to find nameless data in the image. This command does not apply to the boot catalog. - -hide-list disk_path Perform -hide using each line out of file disk_path as argument disk_path_pattern. - -hide-joliet disk_path_pattern Like option -hide but making files invisible in the directory tree of Joliet, if their disk_path matches the given shell parser pattern. - -hide-joliet-list disk_path Perform -hide-joliet using each line out of file disk_path as argument disk_path_pattern. - -hide-hfsplus disk_path_pattern Like option -hide but making files invisible in the directory tree of HFS+, if their disk_path matches the given shell parser pattern. - -hide-hfsplus-list disk_path Perform -hide-hfsplus using each line out of file disk_path as argument disk_path_pattern. @@ -765,98 +703,85 @@ File: xorrisofs.info, Node: ImageId, Next: Bootable, Prev: SetHide, Up: Opti ======================== The following strings and file addresses get stored in the Primary -Volume Descriptor of the ISO9660 image. The file addresses are ISO 9660 -paths. These files should have iso_rr_paths which consist only of the +Volume Descriptor of the ISO9660 image. The file addresses are ISO 9660 +paths. These files should have iso_rr_paths which consist only of the characters [A-Z0-9_] and exactly one dot which separates at most 8 characters from at most 3 characters. -V text - Set the Volume Id of the ISO image. xorriso accepts any text up - to 32 characters, but according to rarely obeyed specs stricter - rules apply: - Conformant are ASCII characters out of [A-Z0-9_]. Like: "IMAGE_23" - Joliet allows 16 UCS-2 characters. Like: "Windows name" - Be aware that the volume id might get used automatically as name - of the mount point when the medium is inserted into a playful - computer system. + Set the Volume Id of the ISO image. xorriso accepts any text up to + 32 characters, but according to rarely obeyed specs stricter rules + apply: + Conformant are ASCII characters out of [A-Z0-9_]. Like: "IMAGE_23" + Joliet allows 16 UCS-2 characters. Like: "Windows name" + Be aware that the volume id might get used automatically as name of + the mount point when the medium is inserted into a playful computer + system. -volid text Alias of -V. - -volset text Set the Volume Set Id of the ISO image. Permissible are up to 128 characters. - -P text - Set the Publisher Id of the ISO image. This may identify the + Set the Publisher Id of the ISO image. This may identify the person or organisation who specified what shall be recorded. Permissible are up to 128 characters. - -publisher text Alias of -P. - -A text Set the Application Id of the ISO image. This may identify the specification of how the data are recorded. Permissible are up to 128 characters. The special text "@xorriso@" gets converted to the id string of - xorriso which is normally written as Preparer Id. It is a wrong + xorriso which is normally written as Preparer Id. It is a wrong tradition to write the program id as Application Id. - -appid text Alias of -A. - -sysid text - Set the System Id of the ISO image. This may identify the system + Set the System Id of the ISO image. This may identify the system which can recognize and act upon the content of the System Area in image blocks 0 to 15. Permissible are up to 32 characters. - -p text - Set the Preparer Id of the ISO image. This may identify the person + Set the Preparer Id of the ISO image. This may identify the person or other entity which controls the preparation of the data which - shall be recorded. Normally this should be the id of xorriso and - not of the person or program which operates xorriso. Please avoid + shall be recorded. Normally this should be the id of xorriso and + not of the person or program which operates xorriso. Please avoid to change it. Permissible are up to 128 characters. The special text "@xorriso@" gets converted to the id string of xorriso which is default at program startup. - -preparer text Alias of -p. - -abstract iso_path - Set the address of the Abstract File of the ISO image. This should + Set the address of the Abstract File of the ISO image. This should be the ISO 9660 path of a file in the image which contains an abstract statement about the image content. Permissible are up to 37 characters. - -biblio iso_path - Set the address of the Biblio File of the ISO image. This should + Set the address of the Biblio File of the ISO image. This should be the ISO 9660 path of a file in the image which contains bibliographic records. Permissible are up to 37 characters. - -copyright iso_path - Set the address of the Copyright File of the ISO image. This should - be the ISO 9660 path of a file in the image which contains a + Set the address of the Copyright File of the ISO image. This + should be the ISO 9660 path of a file in the image which contains a copyright statement. Permissible are up to 37 characters. - --modification-date=YYYYMMDDhhmmsscc - Set a timestring that overrides ISO image creation and - modification timestamps literally. It must consist of 16 decimal - digits which form YYYYMMDDhhmmsscc, with YYYY between 1970 and - 2999. Time zone is GMT. It is supposed to match this GRUB line: + Set a timestring that overrides ISO image creation and modification + timestamps literally. It must consist of 16 decimal digits which + form YYYYMMDDhhmmsscc, with YYYY between 1970 and 2999. Time zone + is GMT. It is supposed to match this GRUB line: search --fs-uuid --set YYYY-MM-DD-hh-mm-ss-cc - E.g. 2010040711405800 is 7 Apr 2010 11:40:58 (+0 centiseconds). - + E.g. 2010040711405800 is 7 Apr 2010 11:40:58 (+0 centiseconds). --application_use character|0xXY|disk_path Specify the content of the Application Use field which can take at most 512 bytes. If the parameter of this command is empty, then the field is filled - with 512 0-bytes. If it is a single character, then it gets + with 512 0-bytes. If it is a single character, then it gets repeated 512 times. If it begins by "0x" followed by two hex digits [0-9a-fA-F], then the digits are read as byte value which gets repeated 512 times. Any other parameter text is used as disk_path to open a data file - and to read up to 512 bytes from it. If the file is smaller than + and to read up to 512 bytes from it. If the file is smaller than 512 bytes, then the remaining bytes in the field get set to binary 0. @@ -867,114 +792,99 @@ File: xorrisofs.info, Node: Bootable, Next: SystemArea, Prev: ImageId, Up: O ================================= The precondition for a bootable ISO image is to have in the ISO image -the files of a boot loader. The boot facilities of computers get -directed to such files, which usually execute further program files -from the ISO image. `xorrisofs' can produce several kinds of boot -block or boot record, which become part of the ISO image, and get -interpreted by the according boot facility. +the files of a boot loader. The boot facilities of computers get +directed to such files, which usually execute further program files from +the ISO image. 'xorrisofs' can produce several kinds of boot block or +boot record, which become part of the ISO image, and get interpreted by +the according boot facility. -An *El Torito* boot record points the bootstrapping facility to a boot -catalog with one or more boot images, which are binary program files -stored in the ISO image. The content of the boot image files is not in -the scope of El Torito. + An *El Torito* boot record points the bootstrapping facility to a +boot catalog with one or more boot images, which are binary program +files stored in the ISO image. The content of the boot image files is +not in the scope of El Torito. xorriso composes the boot catalog according to the boot image files given and structured by options -b, -e, -el-torito-alt-boot, and ---efi-boot. Often it contains only one entry. -El Torito gets interpreted by boot facilities PC-BIOS and EFI. Most +--efi-boot. Often it contains only one entry. +El Torito gets interpreted by boot facilities PC-BIOS and EFI. Most bootable GNU/Linux CDs are equipped with ISOLINUX or GRUB boot images for PC-BIOS. -`xorrisofs' supports the example options out of the ISOLINUX wiki, the +'xorrisofs' supports the example options out of the ISOLINUX wiki, the options used in GRUB script grub-mkrescue, and the example in the FreeBSD AvgLiveCD wiki. -For CD booting via boot facilities other than PC-BIOS and EFI, and for -booting from USB sticks or hard disks, see the next section about the -Sytem Area. + For CD booting via boot facilities other than PC-BIOS and EFI, and +for booting from USB sticks or hard disks, see the next section about +the Sytem Area. -b iso_rr_path Specify the boot image file which shall be mentioned in the current - entry of the El Torito boot catalog. It will be marked as suitable + entry of the El Torito boot catalog. It will be marked as suitable for PC-BIOS. With boot images from ISOLINUX and GRUB this option should be accompanied by options -c , -no-emul-boot , -boot-load-size 4 , -boot-info-table. - -eltorito-boot iso_rr_path Alias of -b. - -eltorito-alt-boot Finalize the current El Torito boot catalog entry and begin a new one. A boot image file and all its necessary options shall be specified before option -eltorito-alt-boot. All further El Torito - boot options apply to the new catalog entry. Up to 32 catalog + boot options apply to the new catalog entry. Up to 32 catalog entries are possible. - -e iso_rr_path Specify the boot image file which shall be mentioned in the current - entry of the El Torito boot catalog. It will be marked as suitable + entry of the El Torito boot catalog. It will be marked as suitable for EFI. - Normally no other El Torito options should be used with the - catalog entry that points to an EFI image. Consider to use - --efi-boot rather than -e. - + Option -e should be followed by option -no-emul-boot and no other + El Torito options before an eventual -eltorito-alt-boot. --efi-boot iso_rr_path Perform -eltorito-alt-boot, option -e with the given iso_rr_path, - and again -eltorito-alt-boot. This gesture is used for achieving - EFI-bootability of the GRUB2 rescue CD. - + -no-emul-boot, and again -eltorito-alt-boot. This gesture is used + for achieving EFI-bootability of the GRUB2 rescue CD. -boot-load-size number Set the number of 512-byte blocks to be loaded at boot time from the boot image in the current catalog entry. Non-emulating BIOS bootimages usually need a load size of 4. EFI boot images usually get set the number of blocks occupied by the boot image file. El Torito cannot represent load sizes higher than 65535. - -hard-disk-boot Mark the boot image in the current catalog entry as emulated hard disk. (Not suitable for any known boot loader.) - -no-emul-boot Mark the boot image in the current catalog entry as not emulating - floppy or hard disk. (This is to be used with all known boot + floppy or hard disk. (This is to be used with all known boot loaders.) If neither -hard-disk-boot nor -no-emul-boot is given, then the - boot image will be marked as emulating a floppy. (Not suitable - for any known boot loader.) - + boot image will be marked as emulating a floppy. (Not suitable for + any known boot loader.) -eltorito-id text|56_hexdigits Define the ID string of the boot catalog section where the boot - image will be listed. If the value consists of 56 characters + image will be listed. If the value consists of 56 characters [0-9A-Fa-f] then it is converted into 28 bytes, else the first 28 characters become the ID string. The ID string of the first boot - image becomes the overall catalog ID. It is limited to 24 - characters. Other id_strings become section IDs. - + image becomes the overall catalog ID. It is limited to 24 + characters. Other id_strings become section IDs. -eltorito-selcrit hexdigits Define the Selection Criteria of the boot image. Up to 20 bytes get read from the given characters [0-9A-Fa-f]. They get attributed to the boot image entry in the catalog. - -boot-info-table - Overwrite bytes 8 to 63 in the current boot image. The information + Overwrite bytes 8 to 63 in the current boot image. The information will be supplied by xorriso in the course of image production: Block address of the Primary Volume Descriptor, block address of the boot image file, size of the boot image file. - --grub2-boot-info Overwrite bytes 2548 to 2555 in the current boot image by the address of that boot image. The address is written as 64 bit - little-endian number. It is the 2KB block address of the boot + little-endian number. It is the 2KB block address of the boot image content, multiplied by 4, and then incremented by 5. - -c iso_rr_path Set the address of the El Torito boot catalog file within the image. This file address is not significant for the booting - PC-BIOS or EFI, but it may later be read by other programs in - order to learn about the available boot images. - + PC-BIOS or EFI, but it may later be read by other programs in order + to learn about the available boot images. -eltorito-catalog iso_rr_path Alias of -c. - --boot-catalog-hide Prevent the El Torito boot catalog from appearing as file in the directory trees of the image. @@ -985,9 +895,9 @@ File: xorrisofs.info, Node: SystemArea, Next: Charset, Prev: Bootable, Up: O 5.9 System Area, MBR, GPT, APM, other boot blocks ================================================= -The first 16 blocks of an ISO image are the System Area. It is -reserved for system dependent boot software. This may be the boot -facilities and partition tables of various hardware architectures. +The first 16 blocks of an ISO image are the System Area. It is reserved +for system dependent boot software. This may be the boot facilities and +partition tables of various hardware architectures. A *MBR* (Master Boot Record) contains boot code and a partition table. It is read by PC-BIOS when booting from USB stick or hard disk, and by PowerPC CHRP or PReP when booting. An MBR partiton with type 0xee @@ -997,9 +907,9 @@ It is read by EFI when booting from USB stick or hard disk, and may be used for finding and mounting a HFS+ partition inside the ISO image. An *APM* (Apple Partition Map) marks the HFS+ partition. It is read by Macs for booting and for mounting. -MBR, GPT and APM are combinable. APM occupies the first 8 bytes of MBR -boot code. All three do not hamper El Torito booting from CDROM. -`xorrisofs' supports further boot facilities: MIPS Big Endian (SGI), +MBR, GPT and APM are combinable. APM occupies the first 8 bytes of MBR +boot code. All three do not hamper El Torito booting from CDROM. +'xorrisofs' supports further boot facilities: MIPS Big Endian (SGI), MIPS Little Endian (DEC), SUN SPARC, HP-PA, DEC Alpha. Those are mutually not combinable and also not combinable with MBR, GPT, or APM. @@ -1012,20 +922,20 @@ the content: -G, -generic-boot, --embedded-boot, --grub2-mbr, The description string consists of the following components, separated by colon ':' "--interval:"Flags":"Interval":"Zeroizers":"Source -The component "--interval" states that this is not a plain disk path -but rather a interval reader description string. +The component "--interval" states that this is not a plain disk path but +rather a interval reader description string. The component Flags modifies the further interpretation: "local_fs" demands to read from a file depicted by the path in Source. -"imported_iso" demands to read from the -indev. This works only if --outdev is not the same as -indev. The Source component is ignored. -The component Interval consists of two byte address numbers separated -by a "-" character. E.g. "0-429" means to read bytes 0 to 429. +"imported_iso" demands to read from the -indev. This works only if +-outdev is not the same as -indev. The Source component is ignored. +The component Interval consists of two byte address numbers separated by +a "-" character. E.g. "0-429" means to read bytes 0 to 429. The component Zeroizers consists of zero or more comma separated -strings. They define which part of the read data to zeroize. Byte +strings. They define which part of the read data to zeroize. Byte number 0 means the byte read from the Interval start address. Each string may be one of: -"zero_mbrpt" demands to zeroize the MBR partition table if bytes 510 -and 511 bear the MBR signature 0x55 0xaa. +"zero_mbrpt" demands to zeroize the MBR partition table if bytes 510 and +511 bear the MBR signature 0x55 0xaa. "zero_gpt" demands to check for a GPT header in bytes 512 to 1023, to zeroize it and its partition table blocks. "zero_apm" demands to check for an APM block 0 and to zeroize its @@ -1035,246 +945,214 @@ with number Start_byte and ending after End_byte. The component Source is the file path with flag "local_fs", and ignored with flag "imported_iso". Byte numbers may be scaled by a suffix out of {k,m,g,t,s,d} meaning -multiplication by {1024, 1024k, 1024m, 1024g, 2048, 512}. A scaled value -end number depicts the last byte of the scaled range. -E.g. "0d-0d" is "0-511". +multiplication by {1024, 1024k, 1024m, 1024g, 2048, 512}. A scaled +value end number depicts the last byte of the scaled range. +E.g. "0d-0d" is "0-511". Examples: "local_fs:0-32767:zero_mbrpt,zero_gpt,440-443:/tmp/template.iso" "imported_iso:45056d-47103d::" -G disk_path - Copy at most 32768 bytes from the given disk file to the very - start of the ISO image. + Copy at most 32768 bytes from the given disk file to the very start + of the ISO image. Other than a El Torito boot image, the file disk_path needs not to - be added to the ISO image. It will not show up as file in the + be added to the ISO image. It will not show up as file in the directory trees. - In multi-session situations, the special disk_path "." prevents + In multi-session situations, the special disk_path "." prevents reading of a disk file but nevertheless causes the adjustments in the existing MBR, which were ordered by other options. - -generic-boot disk_path Alias of -G. - --embedded-boot disk_path Alias of -G. - --grub2-mbr disk_path Install disk_path in the System Area and treat it as modern GRUB2 - MBR. The content start address of the first boot image is - converted to a count of 512 byte blocks, and an offset of 4 is - added. The result is written as 64 bit little-endian number to - byte address 0x1b0. - + MBR. The content start address of the first boot image is converted + to a count of 512 byte blocks, and an offset of 4 is added. The + result is written as 64 bit little-endian number to byte address + 0x1b0. -isohybrid-mbr disk_path Install disk_path as ISOLINUX isohybrid MBR which makes the boot image given by option -b bootable from USB sticks and hard disks - via PC-BIOS. This preparation is normally done by ISOLINUX - program isohybrid on the already produced ISO image. + via PC-BIOS. This preparation is normally done by ISOLINUX program + isohybrid on the already produced ISO image. The disk path should lead to one of the Syslinux files isohdp[fp]x*.bin . The MBR gets patched according to isohybrid - needs. The first partition describes the range of the ISO image. + needs. The first partition describes the range of the ISO image. Its start is at block 0 by default, but may be set to 64 disk blocks by option -partition_offset 16. - For the meaning of special disk_path "." see option -G. - + For the meaning of special disk_path "." see option -G. -isohybrid-gpt-basdat Mark the current El Torito boot image (see options -b and -e) in - GPT as partition of type Basic Data. This works only with + GPT as partition of type Basic Data. This works only with -isohybrid-mbr and has the same impact on the system area as - -efi-boot-part. It cannot be combined with -efi-boot-part or + -efi-boot-part. It cannot be combined with -efi-boot-part or -hfsplus. The first three boot images which are marked by GPT will also show - up as partition entries of type 0xef in MBR. The MBR partition - for PC-BIOS gets type 0x00 rather than 0x17 in this case. Often - the further MBR entries are the ones which actually get used by - EFI. - + up as partition entries of type 0xef in MBR. The MBR partition for + PC-BIOS gets type 0x00 rather than 0x17 in this case. Often the + further MBR entries are the ones which actually get used by EFI. -isohybrid-gpt-hfsplus Mark the current El Torito boot image (see options -b and -e) in GPT as partition of type HFS+. Impact and restrictions are like with -isohybrid-gpt-basdat. - -isohybrid-apm-hfsplus Mark the current El Torito boot image (see options -b and -e) in - Apple Partition Map as partition of type HFS+. This works only + Apple Partition Map as partition of type HFS+. This works only with -isohybrid-mbr and has a similar impact on the system area as - -hfsplus. It cannot be combined with -efi-boot-part or -hfsplus. - The ISOLINUX isohybrid MBR file must begin by a known pattern of - 32 bytes of x86 machine code which essentially does nothing. It - will get overwritten by 32 bytes of APM header mock-up. - + -hfsplus. It cannot be combined with -efi-boot-part or -hfsplus. + The ISOLINUX isohybrid MBR file must begin by a known pattern of 32 + bytes of x86 machine code which essentially does nothing. It will + get overwritten by 32 bytes of APM header mock-up. --protective-msdos-label Patch the System Area by a simple PC-DOS partition table where partition 1 claims the range of the ISO image but leaves the first block unclaimed. - -partition_offset 2kb_block_adr Cause a partition table with a single partition that begins at the - given block address. This is counted in 2048 byte blocks, not in - 512 byte blocks. If the block address is non-zero then it must be - at least 16. Values larger than 16 are hardly of use. A non-zero + given block address. This is counted in 2048 byte blocks, not in + 512 byte blocks. If the block address is non-zero then it must be + at least 16. Values larger than 16 are hardly of use. A non-zero partition offset causes two superblocks to be generated and two - sets of directory trees. The image is then mountable from its + sets of directory trees. The image is then mountable from its absolute start as well as from the partition start. The offset value of an ISO image gets preserved when a new session is added to a loaded image. So the value defined here is only in effect if a new ISO image gets written. - -partition_hd_cyl number Set the number of heads per cylinder for the MBR partition table. - 0 chooses a default value. Maximum is 255. - + 0 chooses a default value. Maximum is 255. -partition_sec_hd number Set the number of sectors per head for the MBR partition table. 0 - chooses a default value. Maximum is 63. + chooses a default value. Maximum is 63. The product partition_sec_hd * partition_hd_cyl * 512 is the cylinder size. It should be divisible by 2048 in order to allow exact alignment. With appended partitions and -appended_part_as_gpt there is no limit for the number of - cylinders. Else there may be at most 1024 of them. If the + cylinders. Else there may be at most 1024 of them. If the cylinder size is too small to stay below the limit, then appropriate values of partition_hd_cyl are chosen with - partition_sec_hd 32 or 63. If the image is larger than + partition_sec_hd 32 or 63. If the image is larger than 8,422,686,720 bytes, then the cylinder size constraints cannot be - fulfilled for MBR. They seem not overly important anyway. Flat + fulfilled for MBR. They seem not overly important anyway. Flat block addresses in partition tables are good for 1 TiB. - -partition_cyl_align mode - Control image size alignment to an integer number of cylinders. - It is prescribed by isohybrid specs and it seems to please program + Control image size alignment to an integer number of cylinders. It + is prescribed by isohybrid specs and it seems to please program fdisk. Cylinder size must be divisible by 2048. Images larger than 8,323,596,288 bytes cannot be aligned in MBR partition table. - Mode "auto" is default. Alignment by padding happens only if + Mode "auto" is default. Alignment by padding happens only if option -isohybrid-mbr is given. Mode "on" causes alignment by padding with option --protective-msdos-label too. Mode "all" is like "on" but also pads up partitions from -append_partition to an aligned size. Mode "off" disables alignment unconditionally. - -append_partition partition_number type_code disk_path Cause a prepared filesystem image to be appended to the ISO image and to be described by a partition table entry in a boot block at - the start of the emerging ISO image. The partition entry will bear + the start of the emerging ISO image. The partition entry will bear the size of the submitted file rounded up to the next multiple of 2048 bytes or to the next multiple of the cylinder size. - Beware of subsequent multi-session runs. The appended partition + Beware of subsequent multi-session runs. The appended partition will get overwritten. - partition_number may be 1 to 4. Number 1 will put the whole ISO - image into the unclaimed space before partition 1. So together + partition_number may be 1 to 4. Number 1 will put the whole ISO + image into the unclaimed space before partition 1. So together with most xorriso MBR or GPT features, number 2 would be the most natural choice. The type_code may be "FAT12", "FAT16", "Linux", or a hexadecimal - number between 0x00 and 0xff. Not all those numbers will yield - usable results. For a list of codes search the Internet for - "Partition Types" or run fdisk command "L". This code matters - only with MBR, not with GPT. + number between 0x00 and 0xff. Not all those numbers will yield + usable results. For a list of codes search the Internet for + "Partition Types" or run fdisk command "L". This code matters only + with MBR, not with GPT. If some other command causes the production of GPT, then the appended partitions will be mentioned there too, even if not -appended_part_as_gpt is given. - -appended_part_as_gpt Marks partitions from -append_partition in GPT rather than in MBR. In this case the MBR shows a single partition of type 0xee which covers the whole output data. By default, appended partitions get marked in GPT only if GPT is produced because of other options. - -efi-boot-part disk_path Copy a file from disk into the emerging ISO image and mark it by a - GPT entry as EFI System Partition. EFI boot firmware is supposed + GPT entry as EFI System Partition. EFI boot firmware is supposed to use a FAT filesystem image in such a partition for booting from USB stick or hard disk. - Instead of a disk_path, the word --efi-boot-image may be given. - It exposes in GPT the content of the first El Torito EFI boot - image as EFI system partition. EFI boot images are introduced by - options -e or --efi-boot. The affected EFI boot image cannot show - up in HFS+ because it is stored outside the HFS+ partition. - + Instead of a disk_path, the word --efi-boot-image may be given. It + exposes in GPT the content of the first El Torito EFI boot image as + EFI system partition. EFI boot images are introduced by options -e + or --efi-boot. The affected EFI boot image cannot show up in HFS+ + because it is stored outside the HFS+ partition. -chrp-boot-part Mark the block range of the whole emerging ISO image as MBR - partition of type 0x96. This is not compatible with any other - feature that produces MBR partition entries. It makes GPT + partition of type 0x96. This is not compatible with any other + feature that produces MBR partition entries. It makes GPT unrecognizable. CHRP is often used in conjunction with HFS. It is not yet tested whether HFS+ filesystems produced with option -hfsplus would boot on any CHRP capable machine which does not boot pure ISO 9660 as well. - -chrp-boot Alias of -chrp-boot-part. - -prep-boot-part disk_path Copy a file from disk into the emerging ISO image and mark it by a - MBR partition entry of type 0x41. PReP boot firmware is supposed + MBR partition entry of type 0x41. PReP boot firmware is supposed to read the content of the partition as single ELF executable file. This option is compatible with other MBR partitions and with GPT. - -mips-boot iso_rr_path Declare a data file in the image to be a MIPS Big Endian boot file - and cause production of a MIPS Big Endian Volume Header. This is + and cause production of a MIPS Big Endian Volume Header. This is mutually exclusive with production of other boot blocks like MBR. It will overwrite the first 512 bytes of any data provided by -G. Up to 15 boot files can be declared by multiple -mips-boot options. - -mipsel-boot iso_rr_path Declare a data file in the image to be the MIPS Little Endian boot - file. This is mutually exclusive with other boot blocks. It will - overwrite the first 512 bytes of any data provided by -G. Only a + file. This is mutually exclusive with other boot blocks. It will + overwrite the first 512 bytes of any data provided by -G. Only a single boot file can be declared by -mipsel-boot. - -B disk_path[,disk_path ...] - Cause one or more data files on disk to be written after the end - of the ISO image. A SUN Disk Label will be written into the first - 512 bytes of the ISO image which lists this image as partition 1 - and the given disk_paths as partition 2 up to 8. + Cause one or more data files on disk to be written after the end of + the ISO image. A SUN Disk Label will be written into the first 512 + bytes of the ISO image which lists this image as partition 1 and + the given disk_paths as partition 2 up to 8. The disk files should contain suitable boot images for SUN SPARC systems. - The pseudo disk_path "..." causes that all empty partition entries - become copies of the last non-empty entry. If no other disk_path - is given before "..." then all partitions describe the ISO image. + The pseudo disk_path "..." causes that all empty partition entries + become copies of the last non-empty entry. If no other disk_path + is given before "..." then all partitions describe the ISO image. In this case, the boot loader code has to be imported by option -G. - -sparc-boot disk_path[,disk_path ...] Alias of -B. - -sparc-label text Set the ASCII label text of a SUN Disk Label. - --grub2-sparc-core iso_rr_path Cause the content address and size of the given data file in the - image to be written after the SUN Disk Label. Both numbers are + image to be written after the SUN Disk Label. Both numbers are counted in bytes. The address is written as 64 bit big-endian number to byte 0x228. The size is written as 32 bit big-endian number to byte 0x230. - -hppa-cmdline text Set the PALO command line for HP-PA. Up to 1023 characters are - permitted by default. With -hppa-hdrversion 4 the limit is 127. - Note that the first five -hppa options are mandatory, if any of - the -hppa options is given. Only option -hppa-hdrversion is - allowed to be missing. - + permitted by default. With -hppa-hdrversion 4 the limit is 127. + Note that the first five -hppa options are mandatory, if any of the + -hppa options is given. Only option -hppa-hdrversion is allowed to + be missing. -hppa-bootloader iso_rr_path Designate the given path as HP-PA bootloader file. - -hppa-kernel-32 iso_rr_path Designate the given path as HP-PA 32 bit kernel file. - -hppa-kernel-64 iso_rr_path Designate the given path as HP-PA 64 bit kernel file. - -hppa-ramdisk iso_rr_path Designate the given path as HP-PA RAM disk file. - -hppa-hdrversion number Choose between PALO header version 5 (default) and version 4. For the appropriate value see in PALO source code: PALOHDRVERSION. - -alpha-boot iso_rr_path Declare a data file in the image to be the DEC Alpha SRM Secondary - Bootstrap Loader and cause production of a boot sector which - points to it. This is mutually exclusive with production of other - boot blocks like MBR. + Bootstrap Loader and cause production of a boot sector which points + to it. This is mutually exclusive with production of other boot + blocks like MBR.  File: xorrisofs.info, Node: Charset, Next: Jigdo, Prev: SystemArea, Up: Options @@ -1297,7 +1175,7 @@ ISO image gets loaded. The sets can be defined by options inserting them into the ISO image. -output-charset character_set_name - Set the character set from which to convert names of loaded ISO + Set the character set from which to convert names of loaded ISO images and to which to convert names when writing ISO images.  @@ -1308,20 +1186,20 @@ File: xorrisofs.info, Node: Jigdo, Next: Miscellaneous, Prev: Charset, Up: O From man genisoimage: "Jigdo is a tool to help in the distribution of large files like CD and DVD images; see http://atterer.net/jigdo/ for -more details. Debian CDs and DVD ISO images are published on the web in +more details. Debian CDs and DVD ISO images are published on the web in jigdo format to allow end users to download them more efficiently." If the use of libjte was enabled at compile time of xorriso, then -`xorrisofs' can produce a .jigdo and a .template file together with a -single-session ISO image. If not, then Jigdo options will cause a +'xorrisofs' can produce a .jigdo and a .template file together with a +single-session ISO image. If not, then Jigdo options will cause a FAILURE event, which normally leads to program abort. One may determine the ability for Jigdo by: -$ xorrisofs -version 2>&1 | grep '^libjte' && echo YES + $ xorrisofs -version 2>&1 | grep '^libjte' && echo YES -The .jigdo file contains checksums and symbolic file addresses. The + The .jigdo file contains checksums and symbolic file addresses. The .template file contains the compressed ISO image with reference tags instead of the content bytes of the listed files. -Input for this process are the normal arguments for a `xorrisofs' +Input for this process are the normal arguments for a 'xorrisofs' session with no image loaded, and a .md5 file which lists those data files which may be listed in the .jigdo file and externally referenced in the .template file. Each designated file is represented in the .md5 @@ -1329,10 +1207,10 @@ file by a single text line: MD5 as 32 hex digits, 2 blanks, size as 12 decimal digits or blanks, 2 blanks, symbolic file address The file address in an .md5 line has to bear the same basename as the -disk_path of the file which it shall match. The directory path of the +disk_path of the file which it shall match. The directory path of the file address is decisive for To=From mapping, not for file recognition. After To=From mapping, the file address gets written into the .jigdo -file. Jigdo restore tools will convert these addresses into really +file. Jigdo restore tools will convert these addresses into really reachable data source addresses from which they can read. If the list of jigdo parameters is not empty, then padding will be counted as part of the ISO image. @@ -1340,52 +1218,43 @@ counted as part of the ISO image. -jigdo-jigdo disk_path Set the disk_path for the .jigdo file with the checksums and download addresses for filling the holes in .template. - -jigdo-template disk_path Set the disk_path for the .template file with the holed and compressed ISO image copy. - -jigdo-min-file-size size Set the minimum size for a data file to be listed in the .jigdo file and being a hole in the .template file. size may be a plain number counting bytes, or a number with appended letter "k", "m", "g" to count KiB (1024 bytes), MiB (1024 KiB), or GiB (1024 MiB). - -jigdo-force-md5 disk_path_pattern adds a regular expression pattern which will get compared with the absolute disk_path of any data file that was not found in the .md5 - list. A match causes a MISHAP event, which normally does not abort + list. A match causes a MISHAP event, which normally does not abort the program run but finally causes a non-zero exit value of the program. - -jigdo-exclude disk_path_pattern Add a regular expression pattern which will get compared with the - absolute disk_path of any data file. A match causes the file to + absolute disk_path of any data file. A match causes the file to stay in .template in any case. - -jigdo-map To=From Add a string pair of the form To=From to the parameter list. If a data file gets listed in the .jigdo file, then it is referred by - the file address from its line in the .md5 file. This file address - gets checked whether it begins with the From string. If so, then + the file address from its line in the .md5 file. This file address + gets checked whether it begins with the From string. If so, then this string will be replaced by the To string and a ':' character, - before it goes into the .jigdo file. The From string should end by + before it goes into the .jigdo file. The From string should end by a '/' character. - -md5-list disk_path Set the disk_path where to find the .md5 input file. - -jigdo-template-compress "gzip"|"bzip2" - Choose one of "bzip2" or "gzip" for the compression of the - template file. The jigdo file is put out uncompressed. - + Choose one of "bzip2" or "gzip" for the compression of the template + file. The jigdo file is put out uncompressed. -checksum_algorithm_iso list_of_names Choose one or more of "md5", "sha1", "sha256", "sha512" for the - auxiliary "# Image Hex" checksums in the .jigdo file. The - list_of_names may e.g. look like "md5,sha1,sha512". Value "all" + auxiliary "# Image Hex" checksums in the .jigdo file. The + list_of_names may e.g. look like "md5,sha1,sha512". Value "all" chooses all available algorithms. Note that MD5 stays always enabled. - -checksum_algorithm_template list_of_names Choose the algorithms for the "# Template Hex" checksums in the .jigdo file. The rules for list_of_names are the same as with @@ -1400,42 +1269,39 @@ File: xorrisofs.info, Node: Miscellaneous, Next: ExSimple, Prev: Jigdo, Up: -print-size Print to stdandard output the foreseeable number of 2048 byte - blocks in the emerging ISO image. Do not produce this image. + blocks in the emerging ISO image. Do not produce this image. The result depends on several settings. - If option -emul-toc is given, then padding (see -pad) is not - counted as part of the image size. In this case either use -no-pad + If option -emul-toc is given, then padding (see -pad) is not + counted as part of the image size. In this case either use -no-pad or add 150 (= 300 KiB) to the resulting number. If mkisofs emulation ends after option -print-size, then the - properties of the most recently specified boot image file cannot - be edited by subsequent xorriso commands. - + properties of the most recently specified boot image file cannot be + edited by subsequent xorriso commands. --no_rc Only if used as first argument this option prevents reading and - interpretation of startup files. See section FILES below. - + interpretation of startup files. See section FILES below. -help - List supported options to stderr. Original mkisofs options bear - their original mkisofs description texts. + List supported options to stderr. Original mkisofs options bear + their original mkisofs description texts. -quiet + Suppress most messages of the program run, except those which indicate problems or errors. - -gui + Increase the frequency of pacifier messages while writing an ISO image. - -log-file disk_path + Truncate file disk_path to 0 size and redirect to it all messages - which would normally appear on stderr. -log-file with empty text + which would normally appear on stderr. -log-file with empty text as disk_path re-enables output to stderr. - -v - Enable the output of informational program messages. + Enable the output of informational program messages. -verbose Alias of -v. - -version Print to standard output a text that begins with "mkisofs 2.01-Emulation Copyright (C)" @@ -1455,7 +1321,7 @@ File: xorrisofs.info, Node: Examples, Next: Files, Prev: Options, Up: Top * ExGrowisofs:: Let xorriso work underneath growisofs * ExIncBackup:: Incremental backup of a few directory trees * ExIncBckAcc:: Incremental backup with accumulated trees -* ExBootable:: Create bootable images for PC-BIOS +* ExBootable:: Create bootable images for PC-BIOS and EFI  File: xorrisofs.info, Node: ExSimple, Next: ExGraft, Prev: Miscellaneous, Up: Examples @@ -1464,11 +1330,11 @@ File: xorrisofs.info, Node: ExSimple, Next: ExGraft, Prev: Miscellaneous, Up ================================= A prepared file tree in directory ./for_iso gets copied into the root -directory of the ISO image. File permissions get set to read-only for +directory of the ISO image. File permissions get set to read-only for everybody. Joliet attributes for Microsoft systems get added. The resulting image gets written as data file ./image.iso on disk. -$ xorrisofs -r -J -o ./image.iso ./for_iso + $ xorrisofs -r -J -o ./image.iso ./for_iso  File: xorrisofs.info, Node: ExGraft, Next: ExMkisofs, Prev: ExSimple, Up: Examples @@ -1477,48 +1343,51 @@ File: xorrisofs.info, Node: ExGraft, Next: ExMkisofs, Prev: ExSimple, Up: Ex ======================================== Without option -graft-points each given disk file is copied into the -root directory of the ISO image, maintaining its name. If a directory +root directory of the ISO image, maintaining its name. If a directory is given, then its files and sub-directories are copied into the root directory, maintaining their names. -$ xorrisofs ... /home/me/datafile /tmp/directory + $ xorrisofs ... /home/me/datafile /tmp/directory -yields in the ISO image root directory: + yields in the ISO image root directory: -/datafile + /datafile /file_1_from_directory ... /file_N_from_directory -With option -graft-points it is possible to put files and directories to -arbitrary paths in the ISO image. + With option -graft-points it is possible to put files and directories +to arbitrary paths in the ISO image. -$ xorrisofs ... -graft-points /home/me/datafile /dir=/tmp/directory + $ xorrisofs ... -graft-points /home/me/datafile /dir=/tmp/directory -yields in the ISO image root directory: + yields in the ISO image root directory: -/datafile + /datafile /dir -Eventually needed parent directories in the image will be created + Eventually needed parent directories in the image will be created automatically: -/datafiles/file1=/home/me/datafile + /datafiles/file1=/home/me/datafile -yields in the ISO image: + yields in the ISO image: -/datafiles/file1 -The attributes of directory /datafiles get copied from /home/me on disk. + /datafiles/file1 -Normally one should avoid = and \ characters in the ISO part of a + The attributes of directory /datafiles get copied from /home/me on +disk. + + Normally one should avoid = and \ characters in the ISO part of a pathspec. But if it must be, one may escape them: -/with_\=_and_\\/file=/tmp/directory/file -yields in the ISO image: + /with_\=_and_\\/file=/tmp/directory/file -/with_=_and_\/file + yields in the ISO image: + + /with_=_and_\/file  File: xorrisofs.info, Node: ExMkisofs, Next: ExGrowisofs, Prev: ExGraft, Up: Examples @@ -1527,30 +1396,30 @@ File: xorrisofs.info, Node: ExMkisofs, Next: ExGrowisofs, Prev: ExGraft, Up: ============================== This example works for multi-session media only: CD-R[W], DVD-R[W], -DVD+R, BD-R. Add cdrskin option --grow_overwriteable_iso to all -as +DVD+R, BD-R. Add cdrskin option --grow_overwriteable_iso to all -as cdrecord runs in order to enable multi-session emulation on overwriteable media. The first session is written like this: -$ xorrisofs -graft-points \ + $ xorrisofs -graft-points \ /tree1=prepared_for_iso/tree1 \ | xorriso -as cdrecord -v dev=/dev/sr0 blank=fast -multi -eject - -Follow-up sessions are written like this: + Follow-up sessions are written like this: -$ dd if=/dev/sr0 count=1 >/dev/null 2>&1 + $ dd if=/dev/sr0 count=1 >/dev/null 2>&1 $ m=$(xorriso -as cdrecord dev=/dev/sr0 -msinfo) $ xorrisofs -M /dev/sr0 -C $m -graft-points \ /tree2=prepared_for_iso/tree2 \ | xorriso -as cdrecord -v dev=/dev/sr0 -waiti -multi -eject - -Always eject the drive tray between sessions. The old sessions get read -via /dev/sr0. Its device driver might not be aware of the changed + Always eject the drive tray between sessions. The old sessions get +read via /dev/sr0. Its device driver might not be aware of the changed content before it loads the medium again. In this case the previous session would not be loaded and the new session would contain only the newly added files. -For the same reason do not let xorriso -as cdrecord load the medium, -but rather do this manually or by a program that reads from /dev/sr0. +For the same reason do not let xorriso -as cdrecord load the medium, but +rather do this manually or by a program that reads from /dev/sr0.  File: xorrisofs.info, Node: ExGrowisofs, Next: ExIncBackup, Prev: ExMkisofs, Up: Examples @@ -1561,28 +1430,28 @@ File: xorrisofs.info, Node: ExGrowisofs, Next: ExIncBackup, Prev: ExMkisofs, growisofs expects an ISO formatter program which understands options -C and -M. A variable is defined to override the hardcoded default name. -$ export MKISOFS="xorrisofs" + $ export MKISOFS="xorrisofs" $ growisofs -Z /dev/dvd /some/files $ growisofs -M /dev/dvd /more/files -If no "xorrisofs" is available on your system, then you will have to + If no "xorrisofs" is available on your system, then you will have to create a link pointing to the xorriso binary and tell growisofs to use -it. E.g. by: +it. E.g. by: -$ ln -s $(which xorriso) "$HOME/xorrisofs" + $ ln -s $(which xorriso) "$HOME/xorrisofs" $ export MKISOFS="$HOME/xorrisofs" -One may quit mkisofs emulation by argument "--" and make use of all -xorriso commands. growisofs dislikes options which start with "-o" but + One may quit mkisofs emulation by argument "--" and make use of all +xorriso commands. growisofs dislikes options which start with "-o" but -outdev must be set to "-". So use "outdev" instead: -$ growisofs -Z /dev/dvd --for_backup -- \ + $ growisofs -Z /dev/dvd --for_backup -- \ outdev - -update_r /my/files /files $ growisofs -M /dev/dvd --for_backup -- \ outdev - -update_r /my/files /files Note that --for_backup is given in the mkisofs emulation. To preserve -the recorded extra data it must already be in effect, when the -emulation loads the image. +the recorded extra data it must already be in effect, when the emulation +loads the image.  File: xorrisofs.info, Node: ExIncBackup, Next: ExIncBckAcc, Prev: ExGrowisofs, Up: Examples @@ -1599,14 +1468,14 @@ expected that inode numbers in the disk filesystem are persistent over cycles of mounting and booting. Files with names matching *.o or *.swp get excluded explicitly. -To be used several times on the same medium, whenever an update of the -two disk trees to the medium is desired. Begin with a blank medium and -update it until he run fails gracefully due to lack of remaining space -on the old one. + To be used several times on the same medium, whenever an update of +the two disk trees to the medium is desired. Begin with a blank medium +and update it until he run fails gracefully due to lack of remaining +space on the old one. Do not let xorriso -as cdrecord load the medium, but rather do this manually or by a program that reads from /dev/sr0. -$ dd if=/dev/sr0 count=1 >/dev/null 2>&1 + $ dd if=/dev/sr0 count=1 >/dev/null 2>&1 $ msinfo=$(xorriso -as cdrecord dev=/dev/sr0 -msinfo) $ load_opts= $ test -n "$msinfo" && load_opts="-M /dev/sr0 -C $msinfo" @@ -1617,46 +1486,46 @@ $ xorrisofs $load_opts -o - --for_backup -m '*.o' -m '*.swp' \ /personal_mail=/home/thomas/personal_mail \ | xorriso -as cdrecord dev=/dev/sr0 -v -multi -waiti -eject - -This makes sense if the full backup leaves substantial remaining + This makes sense if the full backup leaves substantial remaining capacity on media and if the expected changes are much smaller than the full backup. -*Better do not use your youngest backup for -old-root*. Have at least -two media which you use alternatingly. So only older backups get -endangered by the new write operation, while the newest backup is -stored safely on a different medium. + *Better do not use your youngest backup for -old-root*. Have at +least two media which you use alternatingly. So only older backups get +endangered by the new write operation, while the newest backup is stored +safely on a different medium. Always have a blank medium ready to perform a full backup in case the -update attempt fails due to insufficient remaining capacity. This +update attempt fails due to insufficient remaining capacity. This failure will not spoil the old medium, of course. -If inode numbers on disk are not persistent, then use option + If inode numbers on disk are not persistent, then use option --old-root-no-ino . In this case an update run will compare recorded MD5 sums against the current file content on hard disk. -With *mount* option *-o "sbsector="* on GNU/Linux resp. *-s* on FreeBSD -or NetBSD it is possible to access the session trees which represent -the older backup versions. With CD media, GNU/Linux mount accepts -session numbers directly by its option "session=". + With *mount* option *-o "sbsector="* on GNU/Linux resp. *-s* on +FreeBSD or NetBSD it is possible to access the session trees which +represent the older backup versions. With CD media, GNU/Linux mount +accepts session numbers directly by its option "session=". Multi-session media and most overwriteable media written by xorriso can tell the sbsectors of their sessions by xorriso option -toc: -$ xorriso -dev /dev/sr0 -toc + $ xorriso -dev /dev/sr0 -toc -xorriso can print the matching mount command for a session number: + xorriso can print the matching mount command for a session number: -$ xorriso -mount_cmd /dev/sr0 session 12 /mnt + $ xorriso -mount_cmd /dev/sr0 session 12 /mnt -or for a volume id that matches a search expression: + or for a volume id that matches a search expression: -$ xorriso -mount_cmd /dev/sr0 volid '*2008_12_05*' /mnt + $ xorriso -mount_cmd /dev/sr0 volid '*2008_12_05*' /mnt -Both yield on standard output something like: + Both yield on standard output something like: mount -t iso9660 -o nodev,noexec,nosuid,ro,sbsector=1460256 '/dev/sr0' '/mnt' -The superuser may let xorriso execute the mount command directly: + The superuser may let xorriso execute the mount command directly: -# osirrox -mount /dev/sr0 "volid" '*2008_12_05*' /mnt + # osirrox -mount /dev/sr0 "volid" '*2008_12_05*' /mnt  File: xorrisofs.info, Node: ExIncBckAcc, Next: ExBootable, Prev: ExIncBackup, Up: Examples @@ -1672,7 +1541,7 @@ gets compared with the appropriate trees on disk. This demands to know the previously used session directory name. With the first session: -$ xorrisofs -root /session1 \ + $ xorrisofs -root /session1 \ -o - --for_backup -m '*.o' -m '*.swp' \ -V PROJ_MAIL_"$(date '+%Y_%m_%d_%H%M%S')" -graft-points \ /projects=/home/thomas/projects \ @@ -1680,12 +1549,12 @@ $ xorrisofs -root /session1 \ | xorriso -as cdrecord dev=/dev/sr0 -v blank=as_needed \ -multi -waiti -eject - -With the second session, option -old-root refers to /session1 and the + With the second session, option -old-root refers to /session1 and the new -root is /session2. Do not let xorriso -as cdrecord load the medium, but rather do this manually or by a program that reads from /dev/sr0. -$ dd if=/dev/sr0 count=1 >/dev/null 2>&1 + $ dd if=/dev/sr0 count=1 >/dev/null 2>&1 $ msinfo=$(xorriso -as cdrecord dev=/dev/sr0 -msinfo) $ load_opts= $ test -n "$msinfo" && load_opts="-M /dev/sr0 -C $msinfo" @@ -1696,62 +1565,106 @@ $ xorrisofs $load_opts -root /session2 -old-root /session1 \ /personal_mail=/home/thomas/personal_mail \ | xorriso -as cdrecord dev=/dev/sr0 -v -multi -waiti -eject - -With the third session, option -old-root refers to /session2. The new --root is /session3. And so on. + With the third session, option -old-root refers to /session2. The +new -root is /session3. And so on.  File: xorrisofs.info, Node: ExBootable, Prev: ExIncBckAcc, Up: Examples -6.7 Create bootable images for PC-BIOS -====================================== +6.7 Create bootable images for PC-BIOS and EFI +============================================== +The SYSLINUX/ISOLINUX boot loader suite is popular for booting PC-BIOS. The ISOLINUX wiki prescribes to create on disk a directory ./CD_root and -to copy all desired files underneath that directory. Especially file +to copy all desired files underneath that directory. Especially file isolinux.bin shall be copied to ./CD_root/isolinux/isolinux.bin . This is the boot image file. -The prescribed mkisofs options can be used unchanged with `xorrisofs': +The prescribed mkisofs options can be used unchanged with 'xorrisofs': -$ xorrisofs -o output.iso \ + $ xorrisofs -o output.iso \ -b isolinux/isolinux.bin -c isolinux/boot.cat \ -no-emul-boot -boot-load-size 4 -boot-info-table \ ./CD_root -Put it on CD by a burn program. E.g.: + Put it on CD by a burn program. E.g.: -$ xorriso -as cdrecord -v dev=/dev/sr0 blank=as_needed output.iso + $ xorriso -as cdrecord -v dev=/dev/sr0 blank=as_needed output.iso -The image from above example will boot from CD, DVD or BD, but not from -USB stick or other hard-disk-like devices. This can be done by help of -an isohybrid MBR. Syslinux provides matching template files as -isohdp[fp]x*.bin . E.g. /usr/lib/syslinux/isohdpfx.bin . + The image from above example will boot from CD, DVD or BD, but not +from USB stick or other hard-disk-like devices. This can be done by +help of an isohybrid MBR. Syslinux provides matching template files as +isohdp[fp]x*.bin . E.g. /usr/lib/syslinux/isohdpfx.bin . If a few hundred KB of size do not matter, then option -partition_offset can be used to create a partition table where partition 1 starts not at -block 0. This facilitates later manipulations of the USB stick by tools +block 0. This facilitates later manipulations of the USB stick by tools for partitioning and formatting. The image from the following example will be prepared for booting via -MBR and its first parttion will start at hard disk block 64. +MBR and its first partition will start at hard disk block 64. It will also boot from optical media. -$ xorrisofs -o output.iso \ + $ xorrisofs -o output.iso \ -b isolinux/isolinux.bin -c isolinux/boot.cat \ -no-emul-boot -boot-load-size 4 -boot-info-table \ -isohybrid-mbr /usr/lib/syslinux/isohdpfx.bin \ -partition_offset 16 \ ./CD_root -Become superuser and copy the image to the unpartitioned base device -file of the USB stick. On GNU/Linux this is e.g. /dev/sdb, not + Become superuser and copy the image to the unpartitioned base device +file of the USB stick. On GNU/Linux this is e.g. /dev/sdb, not /dev/sdb1. CAUTION: This will overwrite any partitioning on the USB stick and make remaining data unaccessible. So first make sure you got the correct address of the intended device. -E.g. by reading 100 MiB data from it and watching it blinking: +E.g. by reading 100 MiB data from it and watching it blinking: -# dd bs=2K if=/dev/sdb count=50K >/dev/null + # dd bs=2K if=/dev/sdb count=50K >/dev/null + + Now copy the image onto it + + # dd bs=2K if=output.iso of=/dev/sdb + + Now for EFI: +The boot image file has to be the image of an EFI System Partition, i.e. +a FAT filesystem with directory /EFI/BOOT and boot files with EFI +prescribed names: BOOTIA32.EFI for 32 bit x86, BOOTx64.EFI for 64 bit +AMD/x86 (in UEFI-2.4 there is indeed a lower case "x"), BOOTAA64.EFI for +64 bit ARM. The software in the FAT filesystem should be able to find +and inspect the ISO filesystem for boot loader configuration and start +of operating system. GRUB2 program grub-mkimage can produce such a FAT +filesystem with suitable content, which then uses further GRUB2 software +from the ISO filesystem. +EFI boot equipment may be combined with above ISOLINUX isohybrid for +PC-BIOS in a not really UEFI-2.4 compliant way, which obviously works +well. It yields MBR and GPT partition tables, both with nested +partitions. Assumed the EFI System Partition image is ready as +./CD_root/boot/grub/efi.img, add the following options before the +directory address ./CD_root: + + -eltorito-alt-boot -e 'boot/grub/efi.img' -no-emul-boot \ +-isohybrid-gpt-basdat \ + + More compliant with UEFI-2.4 is to decide for either MBR or GPT and +to append a copy of the EFI System Partition in order to avoid overlap +of ISO partition and EFI partition. Here for MBR: + + -eltorito-alt-boot -e 'boot/grub/efi.img' -no-emul-boot \ +-append_partition 2 0xef ./CD_root/boot/grub/efi.img \ + + The resulting ISOs are supposed to boot from optical media and USB +stick. One may omit option -eltorito-alt-boot if no option -b is used +to make the ISO bootable via PC-BIOS. + + For ISOs with pure GRUB2 boot equipment consider to use GRUB2 tool +grub-mkrescue as frontend to xorrisofs. + + If you have a bootable ISO filesystem and want to know its equipment +plus a proposal how to reproduce it, try: + + $ xorriso -hfsplus on -indev IMAGE.iso \ -report_el_torito plain +-report_system_area plain \ -print "" -print "======= Proposal for +xorrisofs options:" \ -report_el_torito as_mkisofs -Now copy the image onto it -# dd bs=2K if=output.iso of=/dev/sdb  File: xorrisofs.info, Node: Files, Next: Seealso, Prev: Examples, Up: Top @@ -1762,63 +1675,58 @@ File: xorrisofs.info, Node: Files, Next: Seealso, Prev: Examples, Up: Top 7.1 Startup Files ================= -If not -no_rc is given as the first argument then `xorrisofs' attempts + +If not -no_rc is given as the first argument then 'xorrisofs' attempts on startup to read and execute lines from the following files: -/etc/default/xorriso + /etc/default/xorriso /etc/opt/xorriso/rc /etc/xorriso/xorriso.conf $HOME/.xorrisorc -The files are read in the sequence given here, but none of them is -required to exist. The lines are not interpreted as `xorrisofs' options -but as generic xorriso commands. See man xorriso. After the xorriso + The files are read in the sequence given here, but none of them is +required to exist. The lines are not interpreted as 'xorrisofs' options +but as generic xorriso commands. See man xorriso. After the xorriso startup files, the program tries one by one to open for reading: -./.mkisofsrc + ./.mkisofsrc $MKISOFSRC $HOME/.mkisofsrc $(dirname $0)/.mkisofsrc -On success it interprets the file content and does not try further + On success it interprets the file content and does not try further files. The last address is used only if start argument 0 has a non-trivial dirname. The reader currently interprets the following NAME=VALUE pairs: -APPI default for -A + APPI default for -A PUBL default for -publisher SYSI default for -sysid VOLI default for -V VOLS default for -volset -Any other lines will be silently ignored. + Any other lines will be silently ignored. +  File: xorrisofs.info, Node: Seealso, Next: Bugreport, Prev: Files, Up: Top 8 See also ********** -For generic `xorriso' command mode +For generic 'xorriso' command mode xorriso(1) - -For the cdrecord emulation of `xorriso' +For the cdrecord emulation of 'xorriso' xorrecord(1) - For mounting xorriso generated ISO 9660 images (-t iso9660) mount(8) - Other programs which produce ISO 9660 images mkisofs(8), genisoimage(8) - Programs which burn sessions to optical media growisofs(1), cdrecord(1), wodim(1), cdrskin(1), xorriso(1) - ACL and xattr getfacl(1), setfacl(1), getfattr(1), setfattr(1) - MD5 checksums md5sum(1) - On FreeBSD some commands differ: getextattr(8), setextattr(8), md5(1) @@ -1828,15 +1736,15 @@ File: xorrisofs.info, Node: Bugreport, Next: Legal, Prev: Seealso, Up: Top 9 Reporting bugs **************** -To report bugs, request help, or suggest enhancements for `xorriso', +To report bugs, request help, or suggest enhancements for 'xorriso', please send electronic mail to the public list . If more privacy is desired, mail to . -Please describe what you expect `xorriso' to do, the program arguments -resp. commands by which you tried to achieve it, the messages of -`xorriso', and the undesirable outcome of your program run. + Please describe what you expect 'xorriso' to do, the program +arguments resp. commands by which you tried to achieve it, the messages +of 'xorriso', and the undesirable outcome of your program run. -Expect to get asked more questions before solutions can be proposed. + Expect to get asked more questions before solutions can be proposed.  File: xorrisofs.info, Node: Legal, Next: CommandIdx, Prev: Bugreport, Up: Top @@ -1854,15 +1762,15 @@ for libburnia-project.org ============== Copyright (c) 2011 - 2015 Thomas Schmitt -Permission is granted to distribute this text freely. It shall only be -modified in sync with the technical properties of xorriso. If you make +Permission is granted to distribute this text freely. It shall only be +modified in sync with the technical properties of xorriso. If you make use of the license to derive modified versions of xorriso then you are entitled to modify this text under that same license. 10.3 Credits ============ -`xorrisofs' is in part based on work by Vreixo Formoso who provides +'xorrisofs' is in part based on work by Vreixo Formoso who provides libisofs together with Mario Danic who also leads the libburnia team. Vladimir Serbinenko contributed the HFS+ filesystem code and related knowledge. @@ -1878,218 +1786,209 @@ File: xorrisofs.info, Node: CommandIdx, Next: ConceptIdx, Prev: Legal, Up: T [index] * Menu: -* --acl Recording of ACLs: SetExtras. (line 71) -* --application_use set Application Use field: ImageId. (line 90) -* --boot-catalog-hide Hide El Torito boot catalog: Bootable. - (line 116) -* --efi-boot El Torito EFI boot image: Bootable. (line 58) -* --embedded-boot Fill System Area e.g. by MBR: SystemArea. (line 77) -* --emul-toc enable table-of-content emulation: SetProduct. (line 37) -* --for_backup Enable backup fidelity: SetExtras. (line 67) -* --grub2-boot-info Patch El Torito boot image: Bootable. (line 101) -* --grub2-mbr Install modern GRUB2 MBR: SystemArea. (line 80) -* --grub2-sparc-core SUN SPARC core file: SystemArea. (line 262) -* --hardlinks Recording of hardlink relations: SetExtras. (line 92) -* --md5 Recording of MD5 checksums: SetExtras. (line 84) -* --modification-date set ISO image timestamps: ImageId. (line 82) -* --no-emul-toc no table-of-content emulation: SetProduct. (line 46) -* --no_rc do not execute startup files: Miscellaneous. (line 19) -* --norock disable Rock Ridge production: SetExtras. (line 25) -* --old-empty old block addresses for empty files: SetProduct. - (line 109) -* --old-root-devno enable disk idevno with -old-root: SetInsert. +* --acl Recording of ACLs: SetExtras. (line 65) +* --application_use set Application Use field: ImageId. (line 77) +* --boot-catalog-hide Hide El Torito boot catalog: Bootable. (line 101) +* --efi-boot El Torito EFI boot image: Bootable. (line 53) +* --embedded-boot Fill System Area e.g. by MBR: SystemArea. (line 75) +* --emul-toc enable table-of-content emulation: SetProduct. (line 33) +* --for_backup Enable backup fidelity: SetExtras. (line 62) +* --grub2-boot-info Patch El Torito boot image: Bootable. (line 89) +* --grub2-mbr Install modern GRUB2 MBR: SystemArea. (line 77) +* --grub2-sparc-core SUN SPARC core file: SystemArea. (line 237) +* --hardlinks Recording of hardlink relations: SetExtras. (line 86) +* --md5 Recording of MD5 checksums: SetExtras. (line 78) +* --modification-date set ISO image timestamps: ImageId. (line 70) +* --no-emul-toc no table-of-content emulation: SetProduct. (line 41) +* --norock disable Rock Ridge production: SetExtras. (line 24) +* --no_rc do not execute startup files: Miscellaneous. (line 18) +* --old-empty old block addresses for empty files: SetProduct. (line 97) -* --old-root-no-ino disable disk ino with -old-root: SetInsert. +* --old-root-devno enable disk idevno with -old-root: SetInsert. (line 84) -* --old-root-no-md5 disable MD5 with -old-root: SetInsert. (line 105) -* --protective-msdos-label Patch System Area partition table: SystemArea. - (line 125) -* --quoted_path_list read pathspecs from disk file: SetInsert. - (line 13) -* --scdbackup_tag Recording of MD5 checksum: SetExtras. (line 101) -* --sort-weight set block address sorting weight: SetProduct. - (line 51) -* --sort-weight-list set block address sorting weight: SetProduct. - (line 63) -* --sort-weight-patterns set block address sorting weight: SetProduct. - (line 84) -* --stdio_sync control forced output to disk files: SetProduct. - (line 25) -* --xattr Recording of xattr: SetExtras. (line 77) -* -A set Application Id: ImageId. (line 38) -* -abstract set Abstract File path: ImageId. (line 66) -* -allow-lowercase lowercase in ISO file names: SetCompl. (line 46) -* -alpha-boot DEC Alpha SRM bootloader: SystemArea. (line 292) -* -append_partition Append MBR or GPT partition after image: SystemArea. - (line 173) -* -appended_part_as_gpt Appended partitions in GPT: SystemArea. - (line 194) -* -appid set Application Id: ImageId. (line 46) -* -b El Torito PC-BIOS boot image: Bootable. (line 32) -* -B SUN SPARC boot images: SystemArea. (line 244) -* -biblio set Biblio File path: ImageId. (line 72) -* -boot-info-table Patch El Torito boot image: Bootable. (line 95) -* -boot-load-size El Torito boot image load size: Bootable. (line 63) -* -c El Torito boot catalog name: Bootable. (line 107) -* -C set load address and write address offset: Loading. (line 28) -* -cdrecord-params set load address and write address offset: Loading. - (line 50) -* -checksum_algorithm_iso choose .jigdo checksums: Jigdo. (line 80) -* -checksum_algorithm_template choose .template checksums: Jigdo. - (line 87) -* -chrp-boot CHRP partition: SystemArea. (line 222) -* -chrp-boot-part CHRP partition: SystemArea. (line 212) -* -copyright set Copyright File path: ImageId. (line 77) -* -D allow deep directory hierachies: SetExtras. (line 31) -* -d omit trailing dot in ISO file names: SetCompl. (line 56) -* -dev set path for loading existing ISO image: Loading. (line 25) -* -dir-mode permissions for all directories: SetProduct. (line 88) -* -disable-deep-relocation allow deep directory hierachies: SetExtras. - (line 44) -* -disallow_dir_id_ext enforce ISO level 1 directory names: SetCompl. - (line 24) -* -e El Torito EFI boot image: Bootable. (line 50) -* -efi-boot-part EFI boot partition: SystemArea. (line 201) -* -eltorito-alt-boot begin next boot catalog entry: Bootable. - (line 43) -* -eltorito-boot El Torito PC-BIOS boot image: Bootable. (line 40) -* -eltorito-catalog El Torito boot catalog name: Bootable. (line 113) -* -eltorito-id El Torito boot section id string: Bootable. (line 82) -* -eltorito-selcrit El Torito boot selection criteria: Bootable. - (line 90) -* -exclude exclude disk files from inserting: SetInsert. (line 42) -* -exclude-list exclude disk files from inserting: SetInsert. - (line 51) -* -f follow symbolic links on disk: SetInsert. (line 24) -* -file-mode permissions for all data files: SetProduct. (line 94) -* -follow-links follow symbolic links on disk: SetInsert. (line 28) -* -full-iso9660-filenames allow 31 characters in ISO file names: SetCompl. - (line 66) -* -G Fill System Area e.g. by MBR: SystemArea. (line 64) -* -generic-boot Fill System Area e.g. by MBR: SystemArea. (line 74) -* -graft-points enable target=source pathspecs: SetInsert. (line 31) -* -gui increase frequency of pacifier messages: Miscellaneous. - (line 31) -* -hard-disk-boot El Torito boot image emulation: Bootable. (line 70) -* -help list supported options: Miscellaneous. (line 23) -* -hfs-bless HFS+ blessing ppc_bootdir: SetExtras. (line 188) -* -hfs-bless-by HFS+ blessing: SetExtras. (line 177) -* -hfsplus enable production of HFS+ partition: SetExtras. (line 130) -* -hfsplus-block-size set APM block size: SetExtras. (line 165) -* -hfsplus-block-size set HFS+ allocation block size: SetExtras. - (line 160) -* -hfsplus-file-creator-type HFS+ creator-type attribute: SetExtras. - (line 173) -* -hfsplus-serial-no set HFS+ serial number: SetExtras. (line 155) -* -hide keep matching files invisible in ISO tree: SetHide. (line 8) -* -hide-hfsplus keep matching files invisible in HFS+ tree: SetHide. - (line 29) -* -hide-hfsplus-list keep matching files invisible in HFS+ tree: SetHide. - (line 33) -* -hide-joliet keep matching files invisible in Joliet tree: SetHide. - (line 20) -* -hide-joliet-list keep matching files invisible in Joliet tree: SetHide. - (line 25) -* -hide-list keep matching files invisible in ISO tree: SetHide. - (line 16) -* -hide-rr-moved set deep directory relocation target: SetExtras. - (line 64) -* -hppa-bootloader HP-PA bootloader file: SystemArea. (line 276) -* -hppa-cmdline HP-PA PALO command line: SystemArea. (line 269) -* -hppa-hdrversion HP-PA PALO header version: SystemArea. (line 288) -* -hppa-kernel_32 HP-PA kernel_32 file: SystemArea. (line 279) -* -hppa-kernel_64 HP-PA kernel_64 file: SystemArea. (line 282) -* -hppa-ramdisk HP-PA ramdisk file: SystemArea. (line 285) -* -input-charset set character set of disk file names: Charset. - (line 17) -* -iso-level define ISO 9660 limitations: SetCompl. (line 7) -* -isohybrid-apm-hfsplus Mark boot image in APM: SystemArea. +* --old-root-no-ino disable disk ino with -old-root: SetInsert. + (line 73) +* --old-root-no-md5 disable MD5 with -old-root: SetInsert. (line 91) +* --protective-msdos-label Patch System Area partition table: SystemArea. (line 116) -* -isohybrid-gpt-basdat Mark boot image in GPT: SystemArea. (line 99) -* -isohybrid-gpt-hfsplus Mark boot image in GPT: SystemArea. - (line 111) -* -isohybrid-mbr Install ISOLINUX isohybrid MBR: SystemArea. - (line 87) -* -J enable production of Joliet directory tree: SetExtras. (line 110) -* -jigdo-exclude add exclusion pattern for .md5: Jigdo. (line 59) -* -jigdo-force-md5 add check pattern for .md5: Jigdo. (line 52) -* -jigdo-jigdo set name of .jigdo file: Jigdo. (line 38) -* -jigdo-map add address translation for .jigdo: Jigdo. (line 64) -* -jigdo-min-file-size set minimum extract size: Jigdo. (line 46) -* -jigdo-template set name of .template file: Jigdo. (line 42) -* -jigdo-template-compress choose compression algorithm: Jigdo. +* --quoted_path_list read pathspecs from disk file: SetInsert. + (line 12) +* --scdbackup_tag Recording of MD5 checksum: SetExtras. (line 94) +* --sort-weight set block address sorting weight: SetProduct. (line 45) +* --sort-weight-list set block address sorting weight: SetProduct. + (line 56) +* --sort-weight-patterns set block address sorting weight: SetProduct. (line 76) -* -joliet enable production of Joliet directory tree: SetExtras. - (line 114) -* -joliet-long allow longer Joliet names: SetExtras. (line 117) -* -joliet-utf16 use UTF-16 with Joliet names: SetExtras. (line 124) -* -l allow 31 characters in ISO file names: SetCompl. (line 63) -* -log-file redirect stderr messages: Miscellaneous. (line 35) -* -m exclude disk files from inserting: SetInsert. (line 35) -* -M set path for loading existing ISO image: Loading. (line 11) -* -max-iso9660-filenames allow 37 characters in ISO file names: SetCompl. - (line 69) -* -md5-list set path of readable .md5: Jigdo. (line 73) -* -mips-boot MIPS Big Endian boot image: SystemArea. (line 231) -* -mipsel-boot MIPS Little Endian boot image: SystemArea. (line 238) -* -N omit version number in ISO file names: SetCompl. (line 73) -* -no-emul-boot El Torito boot image emulation: Bootable. (line 74) -* -no-pad do not add zeros to ISO tree: SetProduct. (line 104) -* -o set output file address: SetProduct. (line 8) -* -old-exclude exclude disk files from inserting: SetInsert. - (line 48) -* -old-root enable incremental insertion: SetInsert. (line 70) -* -omit-period omit trailing dot in ISO file names: SetCompl. +* --stdio_sync control forced output to disk files: SetProduct. + (line 23) +* --xattr Recording of xattr: SetExtras. (line 71) +* -A set Application Id: ImageId. (line 34) +* -abstract set Abstract File path: ImageId. (line 57) +* -allow-lowercase lowercase in ISO file names: SetCompl. (line 42) +* -alpha-boot DEC Alpha SRM bootloader: SystemArea. (line 260) +* -appended_part_as_gpt Appended partitions in GPT: SystemArea. + (line 179) +* -append_partition Append MBR or GPT partition after image: SystemArea. + (line 159) +* -appid set Application Id: ImageId. (line 41) +* -b El Torito PC-BIOS boot image: Bootable. (line 32) +* -B SUN SPARC boot images: SystemArea. (line 222) +* -biblio set Biblio File path: ImageId. (line 62) +* -boot-info-table Patch El Torito boot image: Bootable. (line 84) +* -boot-load-size El Torito boot image load size: Bootable. (line 57) +* -c El Torito boot catalog name: Bootable. (line 94) +* -C set load address and write address offset: Loading. (line 25) +* -cdrecord-params set load address and write address offset: Loading. + (line 46) +* -checksum_algorithm_iso choose .jigdo checksums: Jigdo. (line 72) +* -checksum_algorithm_template choose .template checksums: Jigdo. + (line 78) +* -chrp-boot CHRP partition: SystemArea. (line 204) +* -chrp-boot-part CHRP partition: SystemArea. (line 195) +* -copyright set Copyright File path: ImageId. (line 66) +* -D allow deep directory hierachies: SetExtras. (line 30) +* -d omit trailing dot in ISO file names: SetCompl. (line 50) +* -dev set path for loading existing ISO image: Loading. (line 23) +* -dir-mode permissions for all directories: SetProduct. (line 79) +* -disable-deep-relocation allow deep directory hierachies: SetExtras. + (line 42) +* -disallow_dir_id_ext enforce ISO level 1 directory names: SetCompl. + (line 23) +* -e El Torito EFI boot image: Bootable. (line 47) +* -efi-boot-part EFI boot partition: SystemArea. (line 185) +* -eltorito-alt-boot begin next boot catalog entry: Bootable. (line 41) +* -eltorito-boot El Torito PC-BIOS boot image: Bootable. (line 39) +* -eltorito-catalog El Torito boot catalog name: Bootable. (line 99) +* -eltorito-id El Torito boot section id string: Bootable. (line 73) +* -eltorito-selcrit El Torito boot selection criteria: Bootable. + (line 80) +* -exclude exclude disk files from inserting: SetInsert. (line 37) +* -exclude-list exclude disk files from inserting: SetInsert. (line 44) +* -f follow symbolic links on disk: SetInsert. (line 22) +* -file-mode permissions for all data files: SetProduct. (line 84) +* -follow-links follow symbolic links on disk: SetInsert. (line 26) +* -full-iso9660-filenames allow 31 characters in ISO file names: SetCompl. + (line 59) +* -G Fill System Area e.g. by MBR: SystemArea. (line 64) +* -generic-boot Fill System Area e.g. by MBR: SystemArea. (line 73) +* -graft-points enable target=source pathspecs: SetInsert. (line 28) +* -gui increase frequency of pacifier messages: Miscellaneous. + (line 29) +* -hard-disk-boot El Torito boot image emulation: Bootable. (line 63) +* -help list supported options: Miscellaneous. (line 21) +* -hfs-bless HFS+ blessing ppc_bootdir: SetExtras. (line 170) +* -hfs-bless-by HFS+ blessing: SetExtras. (line 160) +* -hfsplus enable production of HFS+ partition: SetExtras. (line 119) +* -hfsplus-block-size set APM block size: SetExtras. (line 150) +* -hfsplus-block-size set HFS+ allocation block size: SetExtras. + (line 146) +* -hfsplus-file-creator-type HFS+ creator-type attribute: SetExtras. + (line 157) +* -hfsplus-serial-no set HFS+ serial number: SetExtras. (line 142) +* -hide keep matching files invisible in ISO tree: SetHide. (line 8) +* -hide-hfsplus keep matching files invisible in HFS+ tree: SetHide. + (line 25) +* -hide-hfsplus-list keep matching files invisible in HFS+ tree: SetHide. + (line 28) +* -hide-joliet keep matching files invisible in Joliet tree: SetHide. + (line 18) +* -hide-joliet-list keep matching files invisible in Joliet tree: SetHide. + (line 22) +* -hide-list keep matching files invisible in ISO tree: SetHide. + (line 15) +* -hide-rr-moved set deep directory relocation target: SetExtras. (line 60) -* -omit-version-number omit version number in ISO file names: SetCompl. - (line 77) -* -output set output file address: SetProduct. (line 22) -* -output-charset set character set of ISO file names: Charset. - (line 21) -* -p set Preparer Id: ImageId. (line 54) -* -P set Publisher Id: ImageId. (line 30) -* -pad add 300 KiB of zeros to ISO tree: SetProduct. (line 97) -* -partition_cyl_align Image size alignment: SystemArea. (line 161) -* -partition_hd_cyl MBR heads per cylinder: SystemArea. (line 142) -* -partition_offset Make mountable by partition 1: SystemArea. - (line 130) -* -partition_sec_hd MBR sectors per head: SystemArea. (line 146) -* -path-list read pathspecs from disk file: SetInsert. (line 8) -* -prep-boot-part PReP partition: SystemArea. (line 225) -* -preparer set Preparer Id: ImageId. (line 63) -* -prev-session set path for loading existing ISO image: Loading. - (line 22) -* -print-size predict ISO image size: Miscellaneous. (line 8) -* -publisher set Publisher Id: ImageId. (line 35) -* -quiet suppress most messages: Miscellaneous. (line 27) -* -R Rock Ridge (is enabled by default): SetExtras. (line 8) -* -r Rock Ridge with altered owner and permission: SetExtras. - (line 16) -* -rational-rock Rock Ridge with altered owner and permission: SetExtras. - (line 22) -* -relaxed-filenames 7-bit special characters in ISO file names: SetCompl. - (line 50) -* -rock Rock Ridge (is enabled by default): SetExtras. (line 13) -* -root redirect ISO root directory: SetInsert. (line 64) -* -rr_reloc_dir set deep directory relocation target: SetExtras. - (line 47) -* -sparc-boot SUN SPARC boot images: SystemArea. (line 256) -* -sparc-label SUN Disk Label text: SystemArea. (line 259) -* -sysid set System Id: ImageId. (line 49) -* -transparent-compression enable recognition of zisofs files: SetInsert. +* -hppa-bootloader HP-PA bootloader file: SystemArea. (line 249) +* -hppa-cmdline HP-PA PALO command line: SystemArea. (line 243) +* -hppa-hdrversion HP-PA PALO header version: SystemArea. (line 257) +* -hppa-kernel_32 HP-PA kernel_32 file: SystemArea. (line 251) +* -hppa-kernel_64 HP-PA kernel_64 file: SystemArea. (line 253) +* -hppa-ramdisk HP-PA ramdisk file: SystemArea. (line 255) +* -input-charset set character set of disk file names: Charset. + (line 17) +* -iso-level define ISO 9660 limitations: SetCompl. (line 7) +* -iso-level define ISO 9660 limitations <1>: SetCompl. (line 8) +* -isohybrid-apm-hfsplus Mark boot image in APM: SystemArea. (line 108) +* -isohybrid-gpt-basdat Mark boot image in GPT: SystemArea. (line 94) +* -isohybrid-gpt-hfsplus Mark boot image in GPT: SystemArea. (line 104) +* -isohybrid-mbr Install ISOLINUX isohybrid MBR: SystemArea. (line 83) +* -J enable production of Joliet directory tree: SetExtras. (line 102) +* -jigdo-exclude add exclusion pattern for .md5: Jigdo. (line 55) +* -jigdo-force-md5 add check pattern for .md5: Jigdo. (line 49) +* -jigdo-jigdo set name of .jigdo file: Jigdo. (line 38) +* -jigdo-map add address translation for .jigdo: Jigdo. (line 59) +* -jigdo-min-file-size set minimum extract size: Jigdo. (line 44) +* -jigdo-template set name of .template file: Jigdo. (line 41) +* -jigdo-template-compress choose compression algorithm: Jigdo. + (line 69) +* -joliet enable production of Joliet directory tree: SetExtras. + (line 106) +* -joliet-long allow longer Joliet names: SetExtras. (line 108) +* -joliet-utf16 use UTF-16 with Joliet names: SetExtras. (line 114) +* -l allow 31 characters in ISO file names: SetCompl. (line 56) +* -log-file redirect stderr messages: Miscellaneous. (line 33) +* -m exclude disk files from inserting: SetInsert. (line 31) +* -M set path for loading existing ISO image: Loading. (line 11) +* -max-iso9660-filenames allow 37 characters in ISO file names: SetCompl. (line 61) -* -U very relaxed filename rules: SetCompl. (line 29) -* -untranslated-filenames very relaxed filename rules: SetCompl. - (line 36) -* -untranslated_name_len untranslated file names: SetCompl. (line 39) -* -v enable verbous messages: Miscellaneous. (line 40) -* -V set Volume Id: ImageId. (line 13) -* -verbose enable verbous messages: Miscellaneous. (line 43) -* -version report program version: Miscellaneous. (line 46) -* -volid set Volume Id: ImageId. (line 23) -* -volset set Volume Set Id: ImageId. (line 26) -* -x exclude disk files from inserting: SetInsert. (line 45) -* -z enable recognition of zisofs files: SetInsert. (line 55) +* -md5-list set path of readable .md5: Jigdo. (line 67) +* -mips-boot MIPS Big Endian boot image: SystemArea. (line 211) +* -mipsel-boot MIPS Little Endian boot image: SystemArea. (line 217) +* -N omit version number in ISO file names: SetCompl. (line 64) +* -no-emul-boot El Torito boot image emulation: Bootable. (line 66) +* -no-pad do not add zeros to ISO tree: SetProduct. (line 93) +* -o set output file address: SetProduct. (line 8) +* -old-exclude exclude disk files from inserting: SetInsert. (line 42) +* -old-root enable incremental insertion: SetInsert. (line 60) +* -omit-period omit trailing dot in ISO file names: SetCompl. (line 54) +* -omit-version-number omit version number in ISO file names: SetCompl. + (line 69) +* -output set output file address: SetProduct. (line 21) +* -output-charset set character set of ISO file names: Charset. + (line 21) +* -p set Preparer Id: ImageId. (line 47) +* -P set Publisher Id: ImageId. (line 28) +* -pad add 300 KiB of zeros to ISO tree: SetProduct. (line 86) +* -partition_cyl_align Image size alignment: SystemArea. (line 148) +* -partition_hd_cyl MBR heads per cylinder: SystemArea. (line 131) +* -partition_offset Make mountable by partition 1: SystemArea. + (line 120) +* -partition_sec_hd MBR sectors per head: SystemArea. (line 134) +* -path-list read pathspecs from disk file: SetInsert. (line 8) +* -prep-boot-part PReP partition: SystemArea. (line 206) +* -preparer set Preparer Id: ImageId. (line 55) +* -prev-session set path for loading existing ISO image: Loading. + (line 21) +* -print-size predict ISO image size: Miscellaneous. (line 8) +* -publisher set Publisher Id: ImageId. (line 32) +* -quiet suppress most messages: Miscellaneous. (line 25) +* -R Rock Ridge (is enabled by default): SetExtras. (line 8) +* -r Rock Ridge with altered owner and permission: SetExtras. (line 16) +* -rational-rock Rock Ridge with altered owner and permission: SetExtras. + (line 22) +* -relaxed-filenames 7-bit special characters in ISO file names: SetCompl. + (line 45) +* -rock Rock Ridge (is enabled by default): SetExtras. (line 13) +* -root redirect ISO root directory: SetInsert. (line 55) +* -rr_reloc_dir set deep directory relocation target: SetExtras. + (line 44) +* -sparc-boot SUN SPARC boot images: SystemArea. (line 233) +* -sparc-label SUN Disk Label text: SystemArea. (line 235) +* -sysid set System Id: ImageId. (line 43) +* -transparent-compression enable recognition of zisofs files: SetInsert. + (line 53) +* -U very relaxed filename rules: SetCompl. (line 27) +* -untranslated-filenames very relaxed filename rules: SetCompl. + (line 34) +* -untranslated_name_len untranslated file names: SetCompl. (line 36) +* -v enable verbous messages: Miscellaneous. (line 38) +* -V set Volume Id: ImageId. (line 13) +* -verbose enable verbous messages: Miscellaneous. (line 41) +* -version report program version: Miscellaneous. (line 43) +* -volid set Volume Id: ImageId. (line 23) +* -volset set Volume Set Id: ImageId. (line 25) +* -x exclude disk files from inserting: SetInsert. (line 39) +* -z enable recognition of zisofs files: SetInsert. (line 47)  File: xorrisofs.info, Node: ConceptIdx, Prev: CommandIdx, Up: Top @@ -2100,243 +1999,245 @@ File: xorrisofs.info, Node: ConceptIdx, Prev: CommandIdx, Up: Top [index] * Menu: -* Abstract File, set path, -abstract: ImageId. (line 66) -* ACL, record and load, --acl: SetExtras. (line 71) +* Abstract File, set path, -abstract: ImageId. (line 57) +* ACL, record and load, --acl: SetExtras. (line 65) * APM, _definition: SystemArea. (line 16) -* Application Id, set, -A, -appid: ImageId. (line 38) -* Backup, enable fidelity, --for_backup: SetExtras. (line 67) -* Biblio File, set path, -biblio: ImageId. (line 72) +* Application Id, set, -A, -appid: ImageId. (line 34) +* Backup, enable fidelity, --for_backup: SetExtras. (line 62) +* Biblio File, set path, -biblio: ImageId. (line 62) * Block address, set sorting weight, --sort-weight: SetProduct. - (line 51) + (line 45) * Block address, set sorting weight, --sort-weight-list: SetProduct. - (line 63) + (line 56) * Block address, set sorting weight, --sort-weight-patterns: SetProduct. - (line 84) + (line 76) * Bootability, boot catalog hidden, --boot-catalog-hide: Bootable. - (line 116) -* Bootability, boot catalog name, -c, -eltorito-catalog: Bootable. - (line 107) -* Bootability, boot image emulation, -hard-disk-boot: Bootable. - (line 70) -* Bootability, boot image load size, -boot-load-size: Bootable. - (line 63) -* Bootability, boot image patching, --grub2-boot-info: Bootable. (line 101) +* Bootability, boot catalog name, -c, -eltorito-catalog: Bootable. + (line 94) +* Bootability, boot image emulation, -hard-disk-boot: Bootable. + (line 63) +* Bootability, boot image load size, -boot-load-size: Bootable. + (line 57) +* Bootability, boot image patching, --grub2-boot-info: Bootable. + (line 89) * Bootability, boot image patching, -boot-info-table: Bootable. - (line 95) -* Bootability, control, --grub2-sparc-core: SystemArea. (line 262) -* Bootability, control, --efi-boot: Bootable. (line 58) -* Bootability, control, -alpha-boot: SystemArea. (line 292) + (line 84) +* Bootability, control, --grub2-sparc-core: SystemArea. (line 237) +* Bootability, control, --efi-boot: Bootable. (line 53) +* Bootability, control, -alpha-boot: SystemArea. (line 260) * Bootability, control, -b, -eltorito-boot: Bootable. (line 32) -* Bootability, control, -B, -sparc-boot: SystemArea. (line 244) -* Bootability, control, -e: Bootable. (line 50) -* Bootability, control, -hppa-bootloader: SystemArea. (line 276) -* Bootability, control, -hppa-cmdline: SystemArea. (line 269) -* Bootability, control, -hppa-hdrversion: SystemArea. (line 288) -* Bootability, control, -hppa-kernel_32: SystemArea. (line 279) -* Bootability, control, -hppa-kernel_64: SystemArea. (line 282) -* Bootability, control, -hppa-ramdisk: SystemArea. (line 285) -* Bootability, control, -mips-boot: SystemArea. (line 231) -* Bootability, control, -mipsel-boot: SystemArea. (line 238) +* Bootability, control, -B, -sparc-boot: SystemArea. (line 222) +* Bootability, control, -e: Bootable. (line 47) +* Bootability, control, -hppa-bootloader: SystemArea. (line 249) +* Bootability, control, -hppa-cmdline: SystemArea. (line 243) +* Bootability, control, -hppa-hdrversion: SystemArea. (line 257) +* Bootability, control, -hppa-kernel_32: SystemArea. (line 251) +* Bootability, control, -hppa-kernel_64: SystemArea. (line 253) +* Bootability, control, -hppa-ramdisk: SystemArea. (line 255) +* Bootability, control, -mips-boot: SystemArea. (line 211) +* Bootability, control, -mipsel-boot: SystemArea. (line 217) * Bootability, El Torito section id string, -eltorito-id: Bootable. - (line 82) + (line 73) * Bootability, El Torito selection criteria, -eltorito-selcrit: Bootable. - (line 90) + (line 80) * Bootability, fill System Area e.g. by MBR, -G, --embedded-boot, -generic-boot: SystemArea. (line 64) -* Bootability, for CHRP, -chrp-boot-part: SystemArea. (line 212) -* Bootability, for EFI, -efi-boot-part: SystemArea. (line 201) -* Bootability, for PReP, -prep-boot-part: SystemArea. (line 225) +* Bootability, for CHRP, -chrp-boot-part: SystemArea. (line 195) +* Bootability, for EFI, -efi-boot-part: SystemArea. (line 185) +* Bootability, for PReP, -prep-boot-part: SystemArea. (line 206) * Bootability, install ISOLINUX isohybrid MBR, -isohybrid-mbr: SystemArea. - (line 87) -* Bootability, install modern GRUB2 MBR, --grub2-mbr: SystemArea. - (line 80) + (line 83) +* Bootability, install modern GRUB2 MBR, --grub2-mbr: SystemArea. + (line 77) * Bootability, mark boot image in APM, -isohybrid-apm-hfsplus: SystemArea. - (line 116) + (line 108) * Bootability, mark boot image in GPT, -isohybrid-gpt-basdat: SystemArea. - (line 99) + (line 94) * Bootability, mark boot image in GPT, -isohybrid-gpt-hfsplus: SystemArea. - (line 111) -* Bootability, next entry, -eltorito-alt-boot: Bootable. (line 43) + (line 104) +* Bootability, next entry, -eltorito-alt-boot: Bootable. (line 41) * Bootability, no boot image emulation, -no-emul-boot: Bootable. - (line 74) + (line 66) * Bootability, patch System Area partition table, --protective-msdos-label: SystemArea. - (line 125) -* Bootability, SUN Disk Label text, -sparc-label: SystemArea. (line 259) + (line 116) +* Bootability, SUN Disk Label text, -sparc-label: SystemArea. (line 235) * Bugs, reporting: Bugreport. (line 6) * Character Set, for disk file names, -input-charset: Charset. (line 17) * Character Set, for ISO file names, -output-charset: Charset. (line 21) * Character sets, _definition: Charset. (line 6) -* Copyright File, set path, -copyright: ImageId. (line 77) +* Copyright File, set path, -copyright: ImageId. (line 66) * Deep directories, allow, -D, -disable-deep-relocation: SetExtras. - (line 31) + (line 30) * Deep directories, relocation target, -hide-rr-moved: SetExtras. - (line 64) + (line 60) * Deep directories, relocation target, -rr_reloc_dir: SetExtras. - (line 47) -* Disk files, exclude, -hide-list: SetInsert. (line 51) + (line 44) +* Disk files, exclude, -hide-list: SetInsert. (line 44) * Disk files, exclude, -m, -exclude, -x, -old-exclude: SetInsert. - (line 35) -* disk_path, _definition: Insert. (line 8) + (line 31) +* disk_path, _definition: Insert. (line 7) * ECMA-119, _definition: Standards. (line 6) * El Torito, _definition: Bootable. (line 13) * Examples: Examples. (line 6) -* Forced output, control, --stdio_sync: SetProduct. (line 25) -* GPT, _definition: SystemArea. (line 13) +* Forced output, control, --stdio_sync: SetProduct. (line 23) * GPT, mark appended partitions, -appended_part_as_gpt: SystemArea. - (line 194) -* HFS+, _definition: Standards. (line 32) -* HFS+, enables production: SetExtras. (line 130) -* HFS+, issue blessing ppc_bootdir, -hfs-bless: SetExtras. (line 188) -* HFS+, issue blessing, -hfs-bless-by: SetExtras. (line 177) -* HFS+, set allocation block size: SetExtras. (line 160) -* HFS+, set APM block size: SetExtras. (line 165) + (line 179) +* GPT, _definition: SystemArea. (line 13) +* HFS+, enables production: SetExtras. (line 119) +* HFS+, issue blessing ppc_bootdir, -hfs-bless: SetExtras. (line 170) +* HFS+, issue blessing, -hfs-bless-by: SetExtras. (line 160) +* HFS+, set allocation block size: SetExtras. (line 146) +* HFS+, set APM block size: SetExtras. (line 150) * HFS+, set creator and type of file, -hfsplus-file-creator-type: SetExtras. - (line 173) -* HFS+, set serial number: SetExtras. (line 155) -* Hiding, from HFS+, -hide-hfsplus: SetHide. (line 29) -* Hiding, from HFS+, -hide-hfsplus-list: SetHide. (line 33) + (line 157) +* HFS+, set serial number: SetExtras. (line 142) +* HFS+, _definition: Standards. (line 32) +* Hiding, from HFS+, -hide-hfsplus: SetHide. (line 25) +* Hiding, from HFS+, -hide-hfsplus-list: SetHide. (line 28) * Hiding, from ISO and Rock Ridge, -hide: SetHide. (line 8) -* Hiding, from ISO and Rock Ridge, -hide-list: SetHide. (line 16) -* Hiding, from Joliet, -hide-joliet: SetHide. (line 20) -* Hiding, from Joliet, -hide-joliet-list: SetHide. (line 25) -* Image size, alignment, -partition_cyl_align: SystemArea. (line 161) +* Hiding, from ISO and Rock Ridge, -hide-list: SetHide. (line 15) +* Hiding, from Joliet, -hide-joliet: SetHide. (line 18) +* Hiding, from Joliet, -hide-joliet-list: SetHide. (line 22) +* Image size, alignment, -partition_cyl_align: SystemArea. (line 148) * Incremental insertion, disable disk ino, --old-root-no-ino: SetInsert. - (line 84) + (line 73) * Incremental insertion, disable MD5, --old-root-no-md5: SetInsert. - (line 105) + (line 91) * Incremental insertion, enable disk devno, --old-root-devno: SetInsert. - (line 97) -* Incremental insertion, enable, -old-root: SetInsert. (line 70) + (line 84) +* Incremental insertion, enable, -old-root: SetInsert. (line 60) * Interval reader for system area and partitions: SystemArea. (line 24) * ISO 9660, _definition: Standards. (line 6) * ISO 9660:1999, _definition: Standards. (line 26) * ISO file names, 7-bit special characters, -relaxed-filenames: SetCompl. - (line 50) + (line 45) * ISO file names, allow 31 characters, -l, -full-iso9660-filenames: SetCompl. - (line 63) -* ISO file names, allow 37 characters, -max-iso9660-filenames: SetCompl. - (line 69) -* ISO file names, allow lowercase, -allow-lowercase: SetCompl. - (line 46) -* ISO file names, omit trailing dot, -d, -omit-period: SetCompl. (line 56) +* ISO file names, allow 37 characters, -max-iso9660-filenames: SetCompl. + (line 61) +* ISO file names, allow lowercase, -allow-lowercase: SetCompl. + (line 42) +* ISO file names, omit trailing dot, -d, -omit-period: SetCompl. + (line 50) * ISO file names, omit version number, -N, -omit-version-number: SetCompl. - (line 73) + (line 64) * ISO file names, untranslated, -untranslated_name_len: SetCompl. - (line 39) + (line 36) * ISO file names, very relaxed rules, -U, -untranslated-filenames: SetCompl. - (line 29) + (line 27) * ISO image size, predict, -print-size: Miscellaneous. (line 8) * ISO image, set Application Use field, --application_use: ImageId. - (line 90) -* ISO image, set timestamps, --modification-date=: ImageId. (line 82) + (line 77) +* ISO image, set timestamps, --modification-date=: ImageId. (line 70) * ISO level 1, enforce directory names, -disallow_dir_id_ext: SetCompl. - (line 24) + (line 23) * ISO level, specify, -iso-level: SetCompl. (line 7) -* ISO root directory, redirect, -root: SetInsert. (line 64) -* iso_rr_path, _definition: Insert. (line 9) -* Jigdo Template Extraction, -checksum_algorithm_iso: Jigdo. (line 80) +* ISO level, specify, -iso-level <1>: SetCompl. (line 8) +* ISO root directory, redirect, -root: SetInsert. (line 55) +* iso_rr_path, _definition: Insert. (line 8) +* Jigdo Template Extraction, -checksum_algorithm_iso: Jigdo. (line 72) * Jigdo Template Extraction, -checksum_algorithm_template: Jigdo. - (line 87) -* Jigdo Template Extraction, -jigdo-exclude: Jigdo. (line 59) -* Jigdo Template Extraction, -jigdo-force-md5: Jigdo. (line 52) + (line 78) +* Jigdo Template Extraction, -jigdo-exclude: Jigdo. (line 55) +* Jigdo Template Extraction, -jigdo-force-md5: Jigdo. (line 49) * Jigdo Template Extraction, -jigdo-jigdo: Jigdo. (line 38) -* Jigdo Template Extraction, -jigdo-map: Jigdo. (line 64) -* Jigdo Template Extraction, -jigdo-min-file-size: Jigdo. (line 46) -* Jigdo Template Extraction, -jigdo-template: Jigdo. (line 42) -* Jigdo Template Extraction, -jigdo-template-compress: Jigdo. (line 76) -* Jigdo Template Extraction, -md5-list: Jigdo. (line 73) +* Jigdo Template Extraction, -jigdo-map: Jigdo. (line 59) +* Jigdo Template Extraction, -jigdo-min-file-size: Jigdo. (line 44) +* Jigdo Template Extraction, -jigdo-template: Jigdo. (line 41) +* Jigdo Template Extraction, -jigdo-template-compress: Jigdo. (line 69) +* Jigdo Template Extraction, -md5-list: Jigdo. (line 67) * Jigdo Template Extraction, _definition: Jigdo. (line 6) +* Joliet, allows longer names, -joliet-long: SetExtras. (line 108) +* Joliet, enable, -J, -joliet: SetExtras. (line 102) * Joliet, _definition: Standards. (line 21) -* Joliet, allows longer names, -joliet-long: SetExtras. (line 117) -* Joliet, enable, -J, -joliet: SetExtras. (line 110) -* Links, follow on disk, -f, -follow-links: SetInsert. (line 24) -* Links, record and load hard links, --hardlinks: SetExtras. (line 92) +* Links, follow on disk, -f, -follow-links: SetInsert. (line 22) +* Links, record and load hard links, --hardlinks: SetExtras. (line 86) +* MBR, GPT, append partition, -append_partition: SystemArea. (line 159) +* MBR, sectors per head, -partition_sec_hd: SystemArea. (line 131) +* MBR, sectors per head, -partition_sec_hd <1>: SystemArea. (line 134) * MBR, _definition: SystemArea. (line 9) -* MBR, GPT, append partition, -append_partition: SystemArea. (line 173) -* MBR, sectors per head, -partition_sec_hd: SystemArea. (line 142) -* MD5, record and load, --md5: SetExtras. (line 84) -* Message output, increase frequency, -gui: Miscellaneous. (line 31) -* Message output, redirect stderr, -log-file: Miscellaneous. (line 35) -* Message output, suppress, -quiet: Miscellaneous. (line 27) +* MD5, record and load, --md5: SetExtras. (line 78) +* Message output, increase frequency, -gui: Miscellaneous. (line 29) +* Message output, redirect stderr, -log-file: Miscellaneous. (line 33) +* Message output, suppress, -quiet: Miscellaneous. (line 25) * Mountability, by non-trivial partition 1, -partition_offset: SystemArea. - (line 130) -* Options, list, -help: Miscellaneous. (line 23) + (line 120) +* Options, list, -help: Miscellaneous. (line 21) * Output file, set address, -o, -output: SetProduct. (line 8) -* Padding, 300 KiB, -pad: SetProduct. (line 97) -* Padding, disable, --old-empty: SetProduct. (line 109) -* Padding, disable, -no-pad: SetProduct. (line 104) -* pathspec, _definition: Insert. (line 12) -* pathspec, enable target=source, -graft-points: SetInsert. (line 31) -* pathspec, read list of, --quoted_path_list: SetInsert. (line 13) +* Padding, 300 KiB, -pad: SetProduct. (line 86) +* Padding, disable, --old-empty: SetProduct. (line 97) +* Padding, disable, -no-pad: SetProduct. (line 93) +* pathspec, enable target=source, -graft-points: SetInsert. (line 28) +* pathspec, read list of, --quoted_path_list: SetInsert. (line 12) * pathspec, read list of, -path-list: SetInsert. (line 8) -* Permissions, for all data files, -file-mode: SetProduct. (line 94) -* Permissions, for all directories, -dir-mode: SetProduct. (line 88) -* Preparer Id, set, -p: ImageId. (line 54) +* pathspec, _definition: Insert. (line 11) +* Permissions, for all data files, -file-mode: SetProduct. (line 84) +* Permissions, for all directories, -dir-mode: SetProduct. (line 79) +* Preparer Id, set, -p: ImageId. (line 47) * Problems, reporting: Bugreport. (line 6) -* Program version, report, -version: Miscellaneous. (line 46) -* Publisher Id, set, -P, -publisher: ImageId. (line 30) +* Program version, report, -version: Miscellaneous. (line 43) +* Publisher Id, set, -P, -publisher: ImageId. (line 28) * Rock Ridge, (enabled by default), -R, -rock: SetExtras. (line 8) -* Rock Ridge, _definition: Standards. (line 14) * Rock Ridge, altered owner and permission, -r, -rational-rock: SetExtras. (line 16) -* Rock Ridge, disable production, --norock: SetExtras. (line 25) -* scdbackup, record checksum tag, --scdbackup_tag: SetExtras. (line 101) +* Rock Ridge, disable production, --norock: SetExtras. (line 24) +* Rock Ridge, _definition: Standards. (line 14) +* scdbackup, record checksum tag, --scdbackup_tag: SetExtras. (line 94) * Session, select path, -M, -prev-session, -dev: Loading. (line 11) * Session, set load and write address, -C, -cdrecord-params: Loading. - (line 28) -* Startup files, suppress, --no_rc: Miscellaneous. (line 19) + (line 25) +* Startup files, suppress, --no_rc: Miscellaneous. (line 18) * System Area, _definition: SystemArea. (line 6) -* System Id, set, -sysid: ImageId. (line 49) -* Table-of-content, emulation off, --no-emul-toc: SetProduct. (line 46) -* Table-of-content, emulation, --emul-toc: SetProduct. (line 37) -* UTF-16, for Joliet paths, -joliet-utf16: SetExtras. (line 124) -* Verbosity, high, -v, -verbose: Miscellaneous. (line 40) +* System Id, set, -sysid: ImageId. (line 43) +* Table-of-content, emulation off, --no-emul-toc: SetProduct. (line 41) +* Table-of-content, emulation, --emul-toc: SetProduct. (line 33) +* UTF-16, for Joliet paths, -joliet-utf16: SetExtras. (line 114) +* Verbosity, high, -v, -verbose: Miscellaneous. (line 38) * Volume Id, set, -V, -volid: ImageId. (line 13) -* Volume Set Id, set, -volset: ImageId. (line 26) -* xattr, record and load, --xattr: SetExtras. (line 77) +* Volume Set Id, set, -volset: ImageId. (line 25) +* xattr, record and load, --xattr: SetExtras. (line 71) * xorriso, mkisofs emulation: Xorriso. (line 6) * xorriso, options: Options. (line 6) * zisofs file, enable recognition, -z, -transparent-compression: SetInsert. - (line 55) + (line 47)  Tag Table: -Node: Top397 -Node: Overview1103 -Node: Standards1541 -Node: Insert3732 -Node: Xorriso5570 -Node: Options6709 -Node: Loading7436 -Node: SetInsert9732 -Node: SetProduct14148 -Node: SetCompl19321 -Node: SetExtras21917 -Node: SetHide30591 -Node: ImageId31899 -Node: Bootable36067 -Node: SystemArea41247 -Node: Charset55811 -Node: Jigdo56837 -Node: Miscellaneous61104 -Node: Examples62748 -Node: ExSimple63234 -Node: ExGraft63713 -Node: ExMkisofs64960 -Node: ExGrowisofs66213 -Node: ExIncBackup67385 -Node: ExIncBckAcc70503 -Node: ExBootable72179 -Node: Files74271 -Node: Seealso75345 -Node: Bugreport76001 -Node: Legal76582 -Node: CommandIdx77477 -Node: ConceptIdx92909 +Node: Top391 +Node: Overview1095 +Node: Standards1537 +Node: Insert3734 +Node: Xorriso5579 +Node: Options6725 +Node: Loading7452 +Node: SetInsert9752 +Node: SetProduct14161 +Node: SetCompl19331 +Node: SetExtras21923 +Node: SetHide30601 +Node: ImageId31905 +Node: Bootable36076 +Node: SystemArea41243 +Node: Charset55815 +Node: Jigdo56840 +Node: Miscellaneous61117 +Node: Examples62762 +Node: ExSimple63256 +Node: ExGraft63739 +Node: ExMkisofs65039 +Node: ExGrowisofs66305 +Node: ExIncBackup67495 +Node: ExIncBckAcc70660 +Node: ExBootable72349 +Node: Files76531 +Node: Seealso77626 +Node: Bugreport78275 +Node: Legal78863 +Node: CommandIdx79760 +Node: ConceptIdx94555  End Tag Table diff --git a/xorriso/xorrisofs.texi b/xorriso/xorrisofs.texi index af9b06f6..1511d001 100644 --- a/xorriso/xorrisofs.texi +++ b/xorriso/xorrisofs.texi @@ -50,7 +50,7 @@ @c man .\" First parameter, NAME, should be all caps @c man .\" Second parameter, SECTION, should be 1-8, maybe w/ subsection @c man .\" other parameters are allowed: see man(7), man(1) -@c man .TH XORRISOFS 1 "Version 1.4.1, May 17, 2015" +@c man .TH XORRISOFS 1 "Version 1.4.1, Jun 30, 2015" @c man .\" Please adjust this date whenever revising the manpage. @c man .\" @c man .\" Some roff macros, for reference: @@ -1272,15 +1272,14 @@ entry. Up to 32 catalog entries are possible. Specify the boot image file which shall be mentioned in the current entry of the El Torito boot catalog. It will be marked as suitable for EFI. @* -Normally no other El Torito options should be used with the catalog entry -that points to an EFI image. -Consider to use @minus{}@minus{}efi-boot rather than -e. +Option -e should be followed by option -no-emul-boot and no other El Torito +options before an eventual -eltorito-alt-boot. @c man .TP @item @minus{}@minus{}efi-boot iso_rr_path @kindex @minus{}@minus{}efi-boot El Torito EFI boot image @cindex Bootability, control, @minus{}@minus{}efi-boot Perform -eltorito-alt-boot, option -e with the given -iso_rr_path, and again -eltorito-alt-boot. This gesture is +iso_rr_path, -no-emul-boot, and again -eltorito-alt-boot. This gesture is used for achieving EFI-bootability of the GRUB2 rescue CD. @c man .TP @item -boot-load-size number @@ -2012,7 +2011,7 @@ and to standard error the version information of xorriso. @c man .br @c man Incremental backup with accumulated trees @c man .br -@c man Create bootable images for PC-BIOS +@c man Create bootable images for PC-BIOS and EFI @c man .br @cindex Examples @menu @@ -2022,7 +2021,7 @@ and to standard error the version information of xorriso. * ExGrowisofs:: Let xorriso work underneath growisofs * ExIncBackup:: Incremental backup of a few directory trees * ExIncBckAcc:: Incremental backup with accumulated trees -* ExBootable:: Create bootable images for PC-BIOS +* ExBootable:: Create bootable images for PC-BIOS and EFI @end menu @c man .SS @c man .B A simple image production run @@ -2354,9 +2353,10 @@ but rather do this manually or by a program that reads from /dev/sr0. With the third session, option -old-root refers to /session2. The new -root is /session3. And so on. @c man .SS -@c man .B Create bootable images for PC-BIOS +@c man .B Create bootable images for PC-BIOS and EFI @node ExBootable, , ExIncBckAcc, Examples -@section Create bootable images for PC-BIOS +@section Create bootable images for PC-BIOS and EFI +The SYSLINUX/ISOLINUX boot loader suite is popular for booting PC-BIOS. The ISOLINUX wiki prescribes to create on disk a directory ./CD_root and to copy all desired files underneath that directory. Especially file isolinux.bin shall be copied to ./CD_root/isolinux/isolinux.bin . @@ -2392,7 +2392,7 @@ at block 0. This facilitates later manipulations of the USB stick by tools for partitioning and formatting. @* The image from the following example will be prepared for booting via MBR -and its first parttion will start at hard disk block 64. +and its first partition will start at hard disk block 64. @* It will also boot from optical media. @* @@ -2430,6 +2430,63 @@ Now copy the image onto it # dd bs=2K if=output.iso of=/dev/sdb @* @sp 1 +@c man .sp 1 +Now for EFI: +@* +The boot image file has to be the image of an EFI System Partition, +i.e. a FAT filesystem with directory /EFI/BOOT and boot files with +EFI prescribed names: BOOTIA32.EFI for 32 bit x86, +BOOTx64.EFI for 64 bit AMD/x86 (in UEFI-2.4 there is indeed a lower case "x"), +BOOTAA64.EFI for 64 bit ARM. The software in the FAT filesystem should be +able to find and inspect the ISO filesystem for boot loader configuration and +start of operating system. GRUB2 program grub-mkimage can produce such a +FAT filesystem with suitable content, which then uses further GRUB2 +software from the ISO filesystem. +@* +EFI boot equipment may be combined with above ISOLINUX isohybrid for PC-BIOS +in a not really UEFI-2.4 compliant way, which obviously works well. It yields +MBR and GPT partition tables, both with nested partitions. +Assumed the EFI System Partition image is ready as ./CD_root/boot/grub/efi.img, +add the following options before the directory address ./CD_root: +@* +@sp 1 + -eltorito-alt-boot -e 'boot/grub/efi.img' -no-emul-boot \ +@* + -isohybrid-gpt-basdat \ +@* +@sp 1 +More compliant with UEFI-2.4 is to decide for either MBR or GPT and to +append a copy of the EFI System Partition in order to avoid overlap of +ISO partition and EFI partition. Here for MBR: +@* +@sp 1 + -eltorito-alt-boot -e 'boot/grub/efi.img' -no-emul-boot \ + -append_partition 2 0xef ./CD_root/boot/grub/efi.img \ +@* +@sp 1 +The resulting ISOs are supposed to boot from optical media and USB stick. +One may omit option -eltorito-alt-boot if no option -b is used to make +the ISO bootable via PC-BIOS. +@* +@sp 1 +@c man .sp 1 +For ISOs with pure GRUB2 boot equipment consider to use GRUB2 tool +grub-mkrescue as frontend to xorrisofs. +@* +@sp 1 +@c man .sp 1 +If you have a bootable ISO filesystem and want to know its equipment plus +a proposal how to reproduce it, try: +@* +@sp 1 + $ xorriso -hfsplus on -indev IMAGE.iso \ + -report_el_torito plain -report_system_area plain \ + -print "" -print "======= Proposal for xorrisofs options:" \ + -report_el_torito as_mkisofs +@* +@sp 1 +@* +@sp 1 @c man .SH FILES @node Files, Seealso, Examples, Top @chapter Files