From 54ad5d37d08593ed545ac85c831d3e4d26b998f1 Mon Sep 17 00:00:00 2001 From: Thomas Schmitt Date: Fri, 17 Jun 2011 14:39:24 +0000 Subject: [PATCH] Avoided the use of the term 'eventual' for the meaning 'if applicable'. --- ChangeLog | 5 +- README | 2 +- doc/faq.wiki | 2 +- doc/partition_offset.wiki | 6 +- xorriso/README_gnu_xorriso | 6 +- xorriso/xorriso.1 | 207 ++++++------ xorriso/xorriso.h | 9 +- xorriso/xorriso.info | 615 ++++++++++++++++++------------------ xorriso/xorriso.texi | 209 ++++++------ xorriso/xorriso_eng.html | 18 +- xorriso/xorriso_timestamp.h | 2 +- xorriso/xorrisofs.1 | 25 +- xorriso/xorrisofs.info | 117 ++++--- xorriso/xorrisofs.texi | 25 +- 14 files changed, 627 insertions(+), 621 deletions(-) diff --git a/ChangeLog b/ChangeLog index 1ea2ea94..08828b45 100644 --- a/ChangeLog +++ b/ChangeLog @@ -2,8 +2,11 @@ SVN trunk (to become libisoburn-1.1.0.pl00.tar.gz) =============================================================================== * Bug fix: -mount_opts shared worked only with -osirrox o_excl_off * Bug fix: xorriso command -add_plainly "any" did not add all files to the image -* New option -signal_handling * Bug fix: The attempt to blank already blank DVD-RW was not gracefully blocked +* Bug fix (libisofs): -as mkisofs -isohybrid-mbr without -no-pad + was not cylinder aligned +* New option -signal_handling +* New option -close_damaged libisoburn-1.0.8.pl00.tar.gz Thu Apr 14 2011 diff --git a/README b/README index 17c05f66..d6afec45 100644 --- a/README +++ b/README @@ -163,7 +163,7 @@ your desired drive, then consider to kill it. If you cannot get rid of the automounter that easily, try whether it helps to always load the drive tray manually before starting a write run of xorriso. Wait until the drive light is off. -Better try to unmount an eventually mounted media before a write run. +Better try to unmount a mounted media before a write run. Besides true optical drives, libisoburn can also address disk files as input or diff --git a/doc/faq.wiki b/doc/faq.wiki index 565c7449..ffc7c91b 100644 --- a/doc/faq.wiki +++ b/doc/faq.wiki @@ -128,7 +128,7 @@ address 16*2048 and to let start partition 1 at this address. The second superblock leads to a second directory tree which takes into account the address difference between partition 1 and the base device. So the image gets mountable via both devices and reserves 32 kB for boot manager software -where it eventually can manipulate and augment the MBR. +where it may manipulate and augment the MBR. (See [http://libburnia-project.org/wiki/PartitionOffset Partition Offset Wiki] for examples.) diff --git a/doc/partition_offset.wiki b/doc/partition_offset.wiki index e5b45bc0..4e64005d 100644 --- a/doc/partition_offset.wiki +++ b/doc/partition_offset.wiki @@ -10,7 +10,7 @@ via the partition device file. E.g. on GNU/Linux: /dev/sdb and /dev/sdb1. This is achieved by two distinct sets of meta-data which refer to the same file content. -The dual-mount feature supports Rock Ridge and eventually Joliet too. +The dual-mount feature supports Rock Ridge and Joliet too. It is capable of multi-session. Currently only offset 32 kB seems to make sense. Smaller offsets are prohibited @@ -176,8 +176,8 @@ E.g. by 402 kB to 2 MB. Open questions: - Shall the partition of an isohybrid image be marked bootable ? -Currently xorriso keeps the 0x80 mark of an eventually imported MBR -resp. the 0x80 mark which xorriso eventually sets by its own MBR +Currently xorriso keeps the 0x80 mark of an imported MBR +resp. the 0x80 mark which xorriso sets by its own MBR preparations. - If not to be marked bootable: What equipment would the partition need to justify having the mark ? diff --git a/xorriso/README_gnu_xorriso b/xorriso/README_gnu_xorriso index 69556c68..3ccc601a 100644 --- a/xorriso/README_gnu_xorriso +++ b/xorriso/README_gnu_xorriso @@ -166,7 +166,7 @@ your desired drive, then consider to kill it. If you cannot get rid of the automounter that easily, try whether it helps to always load the drive tray manually before starting a write run of xorriso. Wait until the drive light is off. -Better try to unmount an eventually mounted media before a write run. +Better try to unmount a mounted media before a write run. Besides true optical drives, xorriso can also address disk files as input or @@ -237,7 +237,7 @@ any file but rather tell the MD5 of a certain range of data blocks. The superblock checksum tag is written after the ECMA-119 volume descriptors. The tree checksum tag is written after the ECMA-119 directory entries. The session checksum tag is written after all payload including the checksum -array. (Then follows eventual padding.) +array. (Then follows padding.) The tags are single lines of printable text, padded by 0 bytes. They have the following format: @@ -254,7 +254,7 @@ Tag_id distinguishes the following tag types A relocated superblock may appear at LBA 0 of an image which was produced for being stored in a disk file or on overwriteable media (e.g. DVD+RW, BD-RE). -xorriso records the first session at LBA 32. An eventual follow-up session +xorriso records the first session at LBA 32. A follow-up session begins at the next block address which is divisible by 32 and higher than the address of the previous session's end tag. Normally no session starts after the address given by relocated superblock parameter session_start=. diff --git a/xorriso/xorriso.1 b/xorriso/xorriso.1 index dfbcf166..02f8b1e7 100644 --- a/xorriso/xorriso.1 +++ b/xorriso/xorriso.1 @@ -144,13 +144,13 @@ filesystems. one and the modifications. See paragraph Creating, Growing, Modifying, Blind Growing below. .PP -\fBxorriso\fR adopts the concept of multi\-session by loading an eventual -image directory tree, allowing to manipulate it by several actions, and to -write the new image to the target media. +\fBxorriso\fR adopts the concept of multi\-session by loading an +image directory tree if present, +by allowing to manipulate it by several actions, +and by writing the new image to the target media. .br The first session of a \fBxorriso\fR run begins by the definition of -the input -drive with the eventual ISO image or by the definition of an output drive. +the input drive with the ISO image or by the definition of an output drive. The session ends by command \-commit which triggers writing. A \-commit is done automatically when the program ends regularly. .PP @@ -198,7 +198,7 @@ With used CD\-RW and DVD\-RW it can be achieved by action \-blank "as_needed". Overwriteable media are considered blank if they are new or if they have been marked as blank by \fBxorriso\fR. Action \-blank "as_needed" can be used to do this marking on overwriteable -media, or to apply eventual mandatory formatting to new media. +media, or to apply mandatory formatting to new media if necessary. .br \fBAppendable\fR media accept further sessions. Either they are MMC multi\-session media in appendable state, or they are overwriteable media @@ -237,7 +237,7 @@ and output drive determines which write method will be used. They have quite different capabilities and constraints. .PP The method of \fBgrowing\fR adds new data to the existing media. These -data comprise of eventual new file content and they override the existing +data comprise of new file content and they override the existing ISO 9660 + Rock Ridge directory tree. It is possible to hide files from previous sessions but they still exist on media and with many types of optical media it is quite easy to recover them by mounting older sessions. @@ -413,7 +413,7 @@ It uses this extension if enabled by option \fB\-acl\fR. .br AAIP enhanced images are supposed to be mountable normally, but one cannot -expect that the mounted filesystem will show and respect the eventual ACLs. +expect that the mounted filesystem will show and respect the ACLs. For now, only \fBxorriso\fR is able to retrieve those ACLs. It can bring them into effect when files get restored to an ACL enabled file system or it can @@ -421,8 +421,8 @@ print them in a format suitable for tool setfacl. .br Files with ACL show as group permissions the setting of entry "mask::" if that entry exists. Nevertheless the non\-listed group members get handled -according to entry "group::". \fBxorriso\fR brings "group::" into effect -before eventually removing the ACL from a file. +according to entry "group::". When removing ACL from a file, +\fBxorriso\fR brings "group::" into effect. .PP \fBxattr\fR (aka EA) are pairs of name and value which can be attached to file objects. AAIP is @@ -464,14 +464,14 @@ appears among the arguments of such a command. .PP \fBPattern expansion\fR converts a list of pattern words into a list of existing file addresses. -Eventual unmatched pattern words appear themselves in that result list, though. +Unmatched pattern words appear themselves in that result list, though. .br Pattern matching supports the usual shell parser wildcards '*' '?' '[xyz]' and respects '/' as separator which may only be matched literally. .br It is a property of some particular commands and not a general feature. It gets controlled by commands \-iso_rr_pattern and \-disk_pattern. -Commands which eventually use pattern expansion all have variable argument +Commands which may use pattern expansion all have variable argument lists which are marked in this man page by "[***]" rather than "[...]". .br Some other commands perform pattern matching unconditionally. @@ -501,10 +501,10 @@ as in $'...' of bash. .br It is not enabled by default. See option \-backslash_codes. .PP -When the program begins then it first looks for argument \-no_rc. If this is +When the program starts then it first looks for argument \-no_rc. If this is not present then it looks for its startup files and -eventually reads their content as command input lines. Then it interprets -the program arguments as commands and parameters and finally it enters +reads their content as command input lines. Then it interprets +the program arguments as commands and parameters. Finally it enters dialog mode if command \-dialog "on" was executed up to then. .PP The program ends either by command \-end, or by the end of program arguments @@ -562,16 +562,20 @@ inner dashes are interpreted as underscores. .TP .B Aquiring source and target drive: .PP -Before aquiring a drive one will eventually enable options which influence -the behavior of image loading. See next option group. +The effect of aquiring a drive may depend on several options in the +next paragraph "Influencing the behavior of image loading". +If desired, their enabling commands have to be performed before the +commands which aquire the drive. .TP \fB\-dev\fR address -Set input and output drive to the same address and load an eventual ISO image. +Set input and output drive to the same address and load an ISO image if it +is present. If there is no ISO image then create a blank one. Set the image expansion method to growing. .br This is only allowed as long as no changes are pending in the currently -loaded ISO image. Eventually one has to perform \-commit or \-rollback first. +loaded ISO image. If changes are pending, then one has to perform \-commit +or \-rollback first. .br Special address string "\-" means standard output, to which several restrictions apply. See above paragraph "Libburn drives". @@ -580,7 +584,8 @@ An empty address string "" gives up the current device without aquiring a new one. .TP \fB\-indev\fR address -Set input drive and load an eventual ISO image. If the new input drive differs +Set input drive and load an ISO image if present. +If the new input drive differs from \-outdev then switch from growing to modifying or to blind growing. It depends on the setting of \-grow_blindly which of both gets activated. The same rules and restrictions apply as with \-dev. @@ -651,11 +656,11 @@ setting is valid for \-rollback until next \-dev or \-indev, where it will be reset to "auto". .TP \fB\-displacement\fR [-]lba -Compensate an eventual displacement of the image versus the start address +Compensate a displacement of the image versus the start address for which the image was prepared. This affects only loading of ISO images and reading of their files. The multi\-session method of growing is not allowed as long as \-displacement is non\-zero. I.e. \-indev and \-outdev must be -different. Eventually the displacement is reset to 0 before the drive +different. The displacement gets reset to 0 before the drive gets re\-aquired after writing. .br Examples: @@ -690,7 +695,7 @@ If a drive path matches no list then it is considered "harmless". By default these are all paths which do not begin with directory "/dev". .br A path matches a list if one of its parent paths or itself matches a list -entry. An eventual address prefix "stdio:" or "mmc:" will be ignored when +entry. Address prefix "stdio:" or "mmc:" will be ignored when testing for matches. .br By pseudo\-class "clear_list" and pseudo\-patterns "banned", "caution", @@ -716,16 +721,15 @@ input media and does not discard an already loaded image. .TP \fB\-in_charset\fR character_set_name Set the character set from which to convert file names when loading an -image. This has eventually to be done before specifying \-dev , \-indev or -\-rollback. See paragraph "Character sets" for more explanations. +image. See paragraph "Character sets" for more explanations. When loading the written image after \-commit the setting of \-out_charset will be copied to \-in_charset. .TP \fB\-auto_charset\fR "on"|"off" Enable or disable recording and interpretation of the output character -set name in an xattr attribute of the image root directory. If enabled then -an eventual recorded character set name gets used as input character set -when reading an image. +set name in an xattr attribute of the image root directory. If enabled and +if a recorded character set name is found, then this name will be used as +namoe of the input character set when reading an image. .br Note that the default output charset is the local character set of the terminal where \fBxorriso\fR runs. Before attributing this local @@ -740,7 +744,8 @@ In default mode "off", iso_rr files lose their inode numbers at image load time. Each iso_rr file object which has no inode number at image generation time will get a new unique inode number if \-compliance is set to new_rr. .br -Mode "on" preserves eventual inode numbers from the loaded image. +Mode "on" preserves inode numbers from the loaded image if such numbers +were recorded. When committing a session it searches for families of iso_rr files which stem from the same disk file, have identical content filtering and have identical properties. The family members all get the same inode number. @@ -784,12 +789,12 @@ See also options \-getfattr, \-setfattr and above paragraph about xattr. .TP \fB\-md5\fR "on"|"all"|"off"|"load_check_off" Enable or disable processing of MD5 checksums for the overall session and for -each single data file. If enabled then images get loaded only if eventual -checksums tags of superblock and directory tree match properly. The MD5 +each single data file. If enabled then images with checksum tags get loaded +only if the tags of superblock and directory tree match properly. The MD5 checksums of data files and whole session get loaded from the image if there are any. .br -With options \-compare and \-update the eventually recorded MD5 of a file +With options \-compare and \-update the recorded MD5 of a file will be used to avoid content reading from the image. Only the disk file content will be read and compared with that MD5. This can save much time if \-disk_dev_ino "on" is not suitable. @@ -822,7 +827,7 @@ Currently this is a shortcut for: \-hardlinks on \-acl on \-xattr on \-md5 on. .TP \fB\-disk_dev_ino\fR "on"|"ino_only"|"off" Enable or disable processing of recorded file identification numbers -(dev_t and ino_t). They are eventually stored as xattr and allow +(dev_t and ino_t). If enabled they are stored as xattr and allow to substantially accelerate file comparison. The root node gets a global start timestamp. If during comparison a file with younger timestamps is found in the ISO image, then it is suspected to have inconsistent content. @@ -847,7 +852,7 @@ too. Read\-only drives do not tell the actual media type but show any media as ROM (e.g. as DVD\-ROM). The session history of MMC multi\-session media might be truncated to first and last session or even be completely false. -(The eventual emulated history of overwriteable media is not affected by this.) +(The emulated history of overwriteable media is not affected by this.) .br To have in case of failure a chance of getting the session history and especially the address of the last session, there is a scan for ISO 9660 @@ -923,8 +928,9 @@ If other file types collide then the setting of command decides. .br Renaming of files has similar collision handling, but directories can only -be replaced, not merged. Note that \-mv inserts the source objects into an -eventual existing target directory rather than attempting to replace it. +be replaced, not merged. Note that if the target directory exists, then \-mv +inserts the source objects into this directory rather than attempting +to replace it. .PP The commands in this section alter the ISO image and not the local filesystem. .TP @@ -947,7 +953,7 @@ Insert the given files or directory trees from filesystem into the ISO image. .br If \-pathspecs is set to "on" then pattern expansion is always disabled and -character '=' has a special meaning. It eventually separates the ISO image path +character '=' has a special meaning. It separates the ISO image path from the disk path: .br iso_rr_path=disk_path @@ -960,15 +966,16 @@ If no '=' is given then the word is used as both, iso_rr_path and disk path. If in this case the word does not begin with '/' then \-cdx is prepended to the disk_path and \-cd is prepended to the iso_rr_path. .br -If \-pathspecs is set to "off" then eventual \-disk_pattern expansion applies. -The resulting words are used as both, iso_rr_path and disk path. Eventually -\-cdx gets prepended to disk_path and \-cd to iso_rr_path. +If \-pathspecs is set to "off" then \-disk_pattern expansion applies, if enabled. +The resulting words are used as both, iso_rr_path and disk path. Relative +path words get prepended the setting of \-cdx to disk_path and the setting +of \-cd to iso_rr_path. .TP \fB\-add_plainly\fR mode If set to mode "unknown" then any command word that does not begin with "\-" and is not recognized as known command will be subject to a virtual \-add command. I.e. it will be used as pathspec or as disk_path and added to the image. -Eventually \-disk_pattern expansion applies to disk_paths. +If enabled, \-disk_pattern expansion applies to disk_paths. .br Mode "dashed" is similar to "unknown" but also adds unrecognized command words even if they begin with "\-". @@ -1087,8 +1094,8 @@ other file causes a FAILURE event. \fB\-clone\fR iso_rr_path_original iso_rr_path_copy Create a copy of the ISO file object iso_rr_path_original with the new address iso_rr_path_copy. If the original is a directory then copy all -files and directories underneath. An eventual boot catalog file gets -not copied but is silently ignored. +files and directories underneath. If iso_rr_path_original is a boot catalog +file, then it gets not copied but is silently ignored. .br The copied ISO file objects have the same attributes. Copied data files refer to the same content source as their originals. @@ -1099,7 +1106,7 @@ already exists in the ISO tree. .TP \fB\-cp_clone\fR iso_rr_path_original [***] iso_rr_path_dest Create copies of one or more ISO file objects as with command \-clone. -Eventually merge directories with existing ones, but do not overwrite +In case of collision merge directories with existing ones, but do not overwrite existing ISO file objects. .br The rules for generating the copy addresses are the same as with @@ -1124,8 +1131,8 @@ up to 2g \-1 \-\-. Newer ones are good up to 4g \-1 \-\-. You need quite a new Linux kernel to read correctly the final bytes of a file >= 4g if its size is not aligned to 2048 byte blocks. .br -\fBxorriso\fR's own data read capabilities are not affected by eventual -operating system size limits. They apply to mounting only. Nevertheless, +\fBxorriso\fR's own data read capabilities are not affected by +operating system size limits. Such limits apply to mounting only. Nevertheless, the target filesystem of an \-extract must be able to take the file size. .TP \fB\-not_mgt\fR code[:code[...]] @@ -1172,7 +1179,7 @@ get reported with \-compare and deleted from the image with \-update. \fB\-not_paths\fR disk_path [***] Add the given paths to the list of excluded absolute disk paths. If a given path is relative, then the current \-cdx is prepended to form an absolute path. -Eventual pattern matching happens at definition time and not when exclusion +Pattern matching, if enabled, happens at definition time and not when exclusion checks are made. .br (Do not forget to end the list of disk_paths by "\-\-") @@ -1255,7 +1262,7 @@ like with program mkisofs \-graft\-points. It also disables \-disk_pattern expansion for command \-add. .br "off" disables pathspecs of the form target=source -and eventually enables \-disk_pattern expansion. +and re\-enables \-disk_pattern expansion. .TP \fB\-overwrite\fR "on"|"nondir"|"off" Allow or disallow to overwrite existing files in the @@ -1387,8 +1394,8 @@ For octal numbers see man 2 stat. Like \-chmod but affecting all files below eventual directories. .TP \fB\-setfacl\fR acl_text iso_rr_path [***] -Attach the given ACL to the given iso_rr_paths after deleting their eventually -existing ACLs. +Attach the given ACL to the given iso_rr_paths. If the files already have +ACLs, then those get deleted before the new ones get into effect. If acl_text is empty, or contains the text "clear" or the text "\-\-remove\-all", then the existing ACLs will be removed and no new ones will be @@ -1510,7 +1517,7 @@ Like \-alter_date but affecting all files below eventual directories. \fB\-hide\fR hide_state iso_rr_path [***] Prevent the names of the given files from showing up in the directory trees of ISO 9660 and/or Joliet when the image gets written. -The eventual data content of such hidden files will be included in the +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. .br @@ -1556,7 +1563,7 @@ Can be true only for data files which stem not from the loaded image. \fB\-type\fR type_letter : Matches files of the given type: "block", "char", "dir", "pipe", "file", "link", "socket", "eltorito", -"Xotic" which eventually matches what is not matched by the other types. +and "Xotic" which matches what is not matched by the other types. .br Only the first letter is interpreted. E.g.: \-find / \-type d .br @@ -1639,7 +1646,7 @@ Normal precedence is: \-not, \-or , \-and. \fB\-else\fR ... \fB\-endif\fR : Enclose one or more sub expressions. If the \-if expression matches, then the \-then expression is evaluated as the result of the whole expression -up to \-endif. Else the next \-elseif expression is evaluated and eventually +up to \-endif. Else the next \-elseif expression is evaluated and if it matches, its \-then expression. Finally in case of no match, the \-else expression is evaluated. There may be more than one \-elseif. Neither \-else nor \-elseif are mandatory. @@ -1715,7 +1722,7 @@ removes an eventual marking from action "update_merge". .br \fBreport_damage\fR classifies files whether they hit a data block that is -marked as damaged. The result is printed together with the eventual address +marked as damaged. The result is printed together with the address of the first damaged byte, the maximum span of damages, file size, and the path of the file. .br @@ -1730,25 +1737,25 @@ different extent number in column "xt". prints access permissions in ACL text form to the result channel. .br \fBsetfacl\fR -attaches ACLs after removing eventually exiting ones. The new +attaches ACLs after removing existing ones. The new ACL is given in text form as defined with option \-setfacl. .br E.g.: \-exec setfacl u:lisa:rw,u::rw,g::r,o::\-,m::rw \-\- .br \fBgetfattr\fR -prints eventual xattr name\-value pairs from user namespace +prints xattr name\-value pairs from user namespace to the result channel. .br \fBget_any_xattr\fR -prints eventual xattr name\-value pairs from any namespace +prints xattr name\-value pairs from any namespace except ACL to the result channel. This is mostly for debugging of namespace "isofs". .br \fBget_md5\fR -prints eventual recorded MD5 sum together with file path. +prints the MD5 sum, if recorded, together with file path. .br \fBcheck_md5\fR -compares eventual recorded MD5 sum with the file content +compares the MD5 sum, if recorded, with the file content and reports if mismatch. .br E.g.: \-find / \-not \-pending_data \-exec check_md5 FAILURE \-\- @@ -1845,7 +1852,7 @@ Options are: "suffix=..." sets a file name suffix. If it is not empty then it will be appended to the file name or removed from it. .br - "remove_suffix" will remove an eventual file name suffix + "remove_suffix" will remove a file name suffix rather than appending it. .br "if_nonempty" will leave 0\-sized files unfiltered. @@ -1903,7 +1910,7 @@ with files from the loaded ISO image if the write method of growing is in effect (i.e \-indev and \-outdev are identical). .br The reserved filter name "\-\-remove\-all\-filters" revokes -filtering. This will revoke eventual suffix renamings as well. +filtering. This will revoke suffix renamings as well. Use "\-\-remove\-all\-filters+" to prevent any suffix renaming. .TP @@ -1919,8 +1926,8 @@ Discard the manipulated ISO image and reload it from \-indev. (Use \-rollback_end if immediate program end is desired.) .TP \fB\-commit\fR -Perform the write operation. Afterwards eventually make the -\-outdev the new \-dev and load the image from there. +Perform the write operation. Afterwards, if \-outdev is readable, make it +the new \-dev and load the image from there. Switch to growing mode. (A subsequent \-outdev will activate modification mode or blind growing.) \-commit is performed automatically at end of program if there @@ -1954,7 +1961,7 @@ Note: It is not possible yet to effectively eject disk files. \fB\-commit_eject\fR "in"|"out"|"all"|"none" Combined \-commit and \-eject. When writing has finished do not make \-outdev the new \-dev, and load no ISO image. Rather eject -\-indev and/or \-outdev. Eventually give up any non\-ejected drive. +\-indev and/or \-outdev. Give up any non\-ejected drive. .TP \fB\-blank\fR mode Make media ready for writing from scratch (if not \-dummy is activated). @@ -2401,7 +2408,7 @@ because they appear to inadverted readers as one single session. But with multi\-session media CD\-R[W], DVD\-R[W], DVD+R, it implies that the whole bootable system has to reside already in the first session and that the last session still has to bear all files which the booted system expects -after eventually mounting the ISO image. +after mounting the ISO image. .br If a boot image from ISOLINUX or GRUB is known to be present on media then it is advised to patch it @@ -2422,7 +2429,7 @@ and announced by an MBR partition table entry. .br "discard"|"keep"|"patch"|"show_status"|bootspec|"next" .br -Define the handling of an eventual set of El Torito boot images which +Define the handling of a set of El Torito boot images which has been read from an existing ISO image or define how to make a prepared boot image file set bootable. Such file sets get produced by ISOLINUX or GRUB. .br @@ -2461,8 +2468,8 @@ For ISOLINUX : \-boot_image "isolinux" "patch" and their designated fate. .br -A \fBbootspec\fR is a word of the form name=value and is used to describe -the parameters of a boot image by an El Torito record and eventually a MBR. +A \fBbootspec\fR is a word of the form name=valuei. It is used to describe +the parameters of a boot image by an El Torito record or a MBR. The names "dir", "bin_path", "efi_path" lead to El Torito bootable images. Name "system_area" activates a given file as MBR. .br @@ -2530,8 +2537,7 @@ They get attributed to the boot image entry in the catalog. .br \fBnext\fR ends the definition of a boot image and starts a new one. Any following \-bootimage bootspecs will affect the new image. -The first "next" discards eventually loaded boot images and their -catalog. +The first "next" discards loaded boot images and their catalog. .br \fBdiscard\fR gives up an existing boot catalog and its boot images. .br @@ -2570,7 +2576,7 @@ and sizes as if it had been processed by "partition_table=on". If so, then those parameters get updated when the new System Area is written. .br Special "system_area=/dev/zero" causes 32k of NUL\-bytes. -Use this to discard an MBR which eventually was loaded with the ISO image. +Use this to discard an MBR which was loaded with the ISO image. .br \fBpartition_offset=\fR2kb_block_adr causes a partition table with a single partition that begins at the given block address. This is counted in 2048 byte @@ -2610,23 +2616,20 @@ Mode "off" disables alignment for any type. MIPS Big Endian boot file and causes 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 eventually provided by -system_area=. +It will overwrite the first 512 bytes of any data provided by system_area=. Up to 15 boot files can be declared by mips_path=. .br \fBmipsel_path=\fRiso_rr_path declares 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 eventually -provided by system_area=. +It will overwrite the first 512 bytes of any data provided by system_area=. Only a single boot file can be declared by mipsel_path=. .br \fBsparc_label=\fRtext causes the production of a SUN Disk Label with the given text as ASCII label. This boot block format allows to append images for partitions 2 to 8. Partition 1 will always be the ISO image. See option \-append_partition. -The first 512 bytes of any data eventually provided -by system_area= will be overwritten. +The first 512 bytes of any data provided by system_area= will be overwritten. .br \fBmips_discard\fR and \fBsparc_discard\fR revoke any boot file declarations made by mips_path= or mipsel_path=. They also disable production @@ -2694,14 +2697,14 @@ 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 file address is decisive for To=From mapping, not for file recognition. -After eventual To=From mapping, the file address gets written into the .jigdo +After To=From mapping, the file address gets written into the .jigdo file. Jigdo restore tools will convert these addresses into really reachable data source addresses from which they can read. .br If the list of jigdo parameters is not empty, then \fBxorriso\fR will refuse to write to non\-blank targets, it will disable multi\-session emulation, and -eventual padding will be counted as part of the ISO image. +padding will be counted as part of the ISO image. .br .TP \fB\-jigdo\fR parameter_name value @@ -2917,11 +2920,11 @@ signals (e.g. from program "kill" or from keys Ctrl+C) or on signals caused by severe program errors. .br Mode "on" is the default. It uses the signal handler of libburn which produces -ugly messages but puts much effort in releasing eventually used optical drives +ugly messages but puts much effort in releasing optical drives before \fBxorriso\fR ends. .br Mode "off" as first \-signal_handling among the start arguments prevents all -own signal precautions of \fBxorriso\fR. Eventually inherited signal +own signal precautions of \fBxorriso\fR. Inherited signal handler settings stay as they are. .br It works like "sig_dfl" if given after other signal handling was already @@ -3039,7 +3042,7 @@ their libburn standard device files. .br This is only possible when no ISO image changes are pending. After this option was executed, there is no drive current -and no image loaded. Eventually one has to aquire a drive again. +and no image loaded. .br In order to be visible, a device has to offer rw\-permissions with its libburn standard device file. Thus it might be only the @@ -3063,7 +3066,7 @@ with only one or two sessions on it. The last of these sessions is supposed to be the most recent real session then. .br Some read\-only drives and media show no usable session history at all. -Eventually option \-rom_toc_scan might help. +Option \-rom_toc_scan might help. .TP \fB\-mount_cmd\fR drive entity id path Emit an appropriate command line for mounting the ISO session @@ -3304,9 +3307,10 @@ composed from disk_path by replacing disk_prefix by iso_rr_prefix. \fB\-show_stream\fR iso_rr_path [***] Display the content stream chain of data files in the ISO image. The chain consists of the iso_rr_name and one or more streams, separated by " < " marks. -A stream consists of one or more texts eventually in ''\-quotation marks, -eventually separated by ":" characters. The first text describes the stream -type, the following ones describe its individual properties. +A stream description consists of one or more texts, separated by ":" +characters. +The first text tells the stream type, the following ones, if ever, describe its +individual properties. Frequently used types are: .br disk:'disk_path' for local filesystem objects. @@ -3342,7 +3346,7 @@ sessions. These checksums are reachable only via indev and a loaded image. They work independently of the media type and can detect transmission errors. .TP \fB\-check_media\fR [option [option ...]] -- -Try to read data blocks from the indev drive, eventually copy them to a +Try to read data blocks from the indev drive, optionally copy them to a disk file, and finally report about the encountered quality. Several options may be used to modify the default behavior. .br @@ -3360,12 +3364,12 @@ allowed to be unreadable (e.g. gaps between tracks). Alternatively it is possible to report damaged files rather than blocks. .br If \-md5 is "on" then the default mode what=tracks looks out for libisofs -checksum tags for the ISO session data and eventually checks them +checksum tags for the ISO session data and checks them against the checksums computed from the data stream. .TP \fB\-check_media_defaults\fR [option [option ...]] -- Preset options for runs of \-check_media, \-extract_cut and best_effort -file extraction. Eventual options given with \-check_media will override the +file extraction. Options given with \-check_media will override the preset options. \-extract_cut will override some options automatically. .br An option consists of a keyword, a "=" character, and a value. Options @@ -3448,13 +3452,13 @@ recorded MD5 checksums. Severity "ALL" disables this event. tries to read the file given by disk_path as sector bitmap and to store such a map file after the scan run. The bitmap tells which blocks have been read successfully in previous runs. -It allows to do several scans on the same media, eventually with intermediate +It allows to do several scans on the same media, even with intermediate eject, in order to collect readable blocks whenever the drive is lucky enough to produce them. The stored file contains a human readable TOC of tracks and their start block addresses, followed by binary bitmap data. .br \fBmap_with_volid="on"\fR -examines tracks whether they are ISO images and eventually +examines tracks whether they are ISO images and prints their volume ids into the human readable TOC of sector_map=. .br \fBpatch_lba0="on"\fR @@ -3669,7 +3673,7 @@ of mkisofs emulation in the context of a \fBxorriso\fR run. .br Other than with the "cdrecord" personality there is no automatic \-commit at the end of a "mkisofs" option list. Verbosity settings \-v (= "UPDATE") and -\-quiet (= "SORRY") persist. The output file, eventually chosen with \-o, +\-quiet (= "SORRY") persist. The output file persists until things happen like \-commit, \-rollback, \-dev, or end of \fBxorriso\fR. \-pacifier gets set to "mkisofs" if files are added to the image. @@ -3694,7 +3698,7 @@ standard output. \-print\-size inhibits automatic image production at program end. This ban is lifted only if the pending image changes get discarded. .br -Eventual padding is counted as part of the ISO image if not option \-\-emul\-toc +Padding is counted as part of the ISO image if not option \-\-emul\-toc is given. .br If no \-iso\-level is given, then level 1 is chosen when the first file or @@ -3793,7 +3797,7 @@ The scope is only a single data track per session to be written to blank, overwriteable, or appendable media. The media gets closed if closing is applicable and not option \-multi is present. .br -An eventually acquired input drive is given up. +If an input drive was aquired, then it is given up. This is only allowed if no image changes are pending. .br dev= must be given as \fBxorriso\fR device address. Addresses like 0,0,0 @@ -3816,7 +3820,7 @@ are aliases for "cdrecord". If \fBxorriso\fR is started with one of the leafnames "xorrecord", "cdrskin", "cdrecord", or "wodim", then it automatically prepends \-as "cdrskin" to the command line arguments. I.e. all arguments will be interpreted cdrecord -style until "\-\-" is encountered and an eventual commit happens. +style until "\-\-" is encountered. From then on, options are interpreted as \fBxorriso\fR options. .br \-\-no_rc as first argument of such a program start @@ -3870,8 +3874,7 @@ Program scdbackup_verify will recognize and verify tag resp. record. \fB\-no_rc\fR .br Only if used as first command line argument this option -prevents reading and interpretation of eventual startup -files. See section FILES below. +prevents reading and interpretation of startup files. See section FILES below. .TP \fB\-options_from_file\fR fileaddress Read quoted input from fileaddress and execute it like dialog lines. @@ -4018,7 +4021,7 @@ Only "\-scsi_log" with dash "\-" is recognized that way. .TP \fB\-end\fR .br -End program after writing eventually pending changes. +End program after writing pending changes. .TP \fB\-rollback_end\fR Discard pending changes. End program immediately. @@ -4026,7 +4029,7 @@ Discard pending changes. End program immediately. \fB#\fR any text Only in dialog or file execution mode, and only as first non\-whitespace in line: -Do not execute the line but eventually store it in history. +Do not execute the line but store it in readline history. .TP .B Support for frontend programs via stdin and stdout: .TP @@ -4279,7 +4282,7 @@ set ISO\-8859\-1 but that the readers expected UTF\-8. Now a new session with the same files gets added with converted file names. In order to avoid any weaknesses of the local character set, this command pretends that it uses already the final target set UTF\-8. -Therefore strange file names may appear in eventual messages which +Therefore strange file names may appear in messages, which will be made terminal\-safe by option \-backslash_codes. .br $ xorriso \-in_charset ISO\-8859\-1 \-local_charset UTF\-8 \\ @@ -4539,7 +4542,7 @@ $ xorriso \-outdev /dev/sr0 \-toc .br Then load the desired session and copy the file trees to disk. Enable restoring of ACL, xattr and hard links. -Avoid to eventually create /home/thomas/restored without rwx\-permission. +Avoid to create /home/thomas/restored without rwx\-permission. .br $ xorriso \-for_backup \\ .br @@ -4570,7 +4573,7 @@ $ xorriso \-abort_on NEVER \-indev /dev/sr0 \\ .br data_to="$HOME"/dvd_copy sector_map="$HOME"/dvd_copy.map \-\- .br -This can be repeated several times, eventually with \-eject or with other +This can be repeated several times, if necessary with \-eject or with other \-indev drives. See the human readable part of "$HOME"/dvd_copy.map for addresses which can be used on "$HOME"/dvd_copy with mount option \-o sbsector= resp. \-s. diff --git a/xorriso/xorriso.h b/xorriso/xorriso.h index ab635e41..1721152e 100644 --- a/xorriso/xorriso.h +++ b/xorriso/xorriso.h @@ -231,7 +231,7 @@ int Xorriso_destroy(struct XorrisO **xorriso, int flag); /* --------------------- Command Interpreters ------------------- */ -/* This special interpreter is eventually called between Xorriso_new() and +/* This special interpreter may be called between Xorriso_new() and Xorriso_startup_libraries(). It interprets certain commands which shall get into effect before the libraries get initialized: -abort_on , -report_about , -return_with , -list_delimiter , @@ -273,7 +273,7 @@ int Xorriso_prescan_args(struct XorrisO *xorriso, int argc, char **argv, int Xorriso_read_rc(struct XorrisO *xorriso, int flag); -/* Check whether program arguments shall be backslash decoded and eventually +/* Check whether program arguments shall be backslash decoded. If so, then replace *argv by a new argument vector. The old one will not be freed by this call. If it is dynamic memory then you need to keep a copy of the pointer and free it yourself after this call. @@ -333,7 +333,8 @@ int Xorriso_interpreter(struct XorrisO *xorriso, int Xorriso_execute_option(struct XorrisO *xorriso, char *line, int flag); -/* Enter xorriso command line dialog mode, eventually using libreadline. +/* Enter xorriso command line dialog mode, using libreadline if configured + at build time and not disabled at run time. This call returns immediately if not option -dialog "on" was performed before. @param xorriso The context object in which to perform the commands. @@ -848,7 +849,7 @@ int Xorriso_option_external_filter(struct XorrisO *xorriso, /* Options -extract , -extract_single */ /* @param flag bit0=do not report the restored item bit1=do not reset pacifier, no final pacifier message - bit5= -extract_single: eventually do not insert directory tree + bit5= -extract_single: do not insert directory tree */ int Xorriso_option_extract(struct XorrisO *xorriso, char *disk_path, char *iso_path, int flag); diff --git a/xorriso/xorriso.info b/xorriso/xorriso.info index 259abf60..bd7b0723 100644 --- a/xorriso/xorriso.info +++ b/xorriso/xorriso.info @@ -121,11 +121,11 @@ ISO 9660 filesystems. and the modifications. See paragraph Creating, Growing, Modifying, Blind Growing below. - `xorriso' adopts the concept of multi-session by loading an eventual -image directory tree, allowing to manipulate it by several actions, and -to write the new image to the target media. The first session of a -`xorriso' run begins by the definition of the input drive with the -eventual ISO image or by the definition of an output drive. The + `xorriso' adopts the concept of multi-session by loading an image +directory tree if present, by allowing to manipulate it by several +actions, and by writing the new image to the target media. The first +session of a `xorriso' run begins by the definition of the input drive +with the ISO image or by the definition of an output drive. The session ends by command -commit which triggers writing. A -commit is done automatically when the program ends regularly. @@ -175,8 +175,8 @@ Blank is the state of newly purchased optical media. With used CD-RW and DVD-RW it can be achieved by action -blank "as_needed". Overwriteable media are considered blank if they are new or if they have been marked as blank by `xorriso'. Action -blank "as_needed" can be -used to do this marking on overwriteable media, or to apply eventual -mandatory formatting to new media. +used to do this marking on overwriteable media, or to apply mandatory +formatting to new media if necessary. *Appendable* media accept further sessions. Either they are MMC multi-session media in appendable state, or they are overwriteable media @@ -215,11 +215,11 @@ constellation of input and output drive determines which write method will be used. They have quite different capabilities and constraints. The method of *growing* adds new data to the existing media. These -data comprise of eventual new file content and they override the -existing ISO 9660 + Rock Ridge directory tree. It is possible to hide -files from previous sessions but they still exist on media and with -many types of optical media it is quite easy to recover them by -mounting older sessions. +data comprise of new file content and they override the existing ISO +9660 + Rock Ridge directory tree. It is possible to hide files from +previous sessions but they still exist on media and with many types of +optical media it is quite easy to recover them by mounting older +sessions. Growing is achieved by option -dev. The write method of *modifying* produces compact filesystem images @@ -362,13 +362,13 @@ So libisofs has introduced a standard conformant extension named AAIP for that purpose. It uses this extension if enabled by option *-acl*. AAIP enhanced images are supposed to be mountable normally, but one cannot expect that the mounted filesystem will show and respect the -eventual ACLs. For now, only `xorriso' is able to retrieve those ACLs. -It can bring them into effect when files get restored to an ACL enabled -file system or it can print them in a format suitable for tool setfacl. +ACLs. For now, only `xorriso' is able to retrieve those ACLs. It can +bring them into effect when files get restored to an ACL enabled file +system or it can print them in a format suitable for tool setfacl. Files with ACL show as group permissions the setting of entry "mask::" if that entry exists. Nevertheless the non-listed group members get -handled according to entry "group::". `xorriso' brings "group::" into -effect before eventually removing the ACL from a file. +handled according to entry "group::". When removing ACL from a file, +`xorriso' brings "group::" into effect. *xattr* (aka EA) are pairs of name and value which can be attached to file objects. AAIP is able to represent them and `xorriso' allows to @@ -404,16 +404,15 @@ parameters of a command with a fixed list length. It is handled as normal text if it appears among the arguments of such a command. *Pattern expansion* converts a list of pattern words into a list of -existing file addresses. Eventual unmatched pattern words appear -themselves in that result list, though. +existing file addresses. Unmatched pattern words appear themselves in +that result list, though. Pattern matching supports the usual shell parser wildcards '*' '?' '[xyz]' and respects '/' as separator which may only be matched literally. It is a property of some particular commands and not a general feature. It gets controlled by commands -iso_rr_pattern and -disk_pattern. -Commands which eventually use pattern expansion all have variable -argument lists which are marked in this man page by "[***]" rather than -"[...]". +Commands which may use pattern expansion all have variable argument +lists which are marked in this man page by "[***]" rather than "[...]". Some other commands perform pattern matching unconditionally. Command and parameter words are either read from program arguments, @@ -437,11 +436,11 @@ allow optional *Backslash Interpretation* which can represent all ASCII characters except NUL (0) by backslash codes as in $'...' of bash. It is not enabled by default. See option -backslash_codes. - When the program begins then it first looks for argument -no_rc. If -this is not present then it looks for its startup files and eventually -reads their content as command input lines. Then it interprets the -program arguments as commands and parameters and finally it enters -dialog mode if command -dialog "on" was executed up to then. + When the program starts then it first looks for argument -no_rc. If +this is not present then it looks for its startup files and reads their +content as command input lines. Then it interprets the program +arguments as commands and parameters. Finally it enters dialog mode if +command -dialog "on" was executed up to then. The program ends either by command -end, or by the end of program arguments if not dialog was enabled up to that moment, or by a problem @@ -524,27 +523,29 @@ File: xorriso.info, Node: AqDrive, Next: Loading, Prev: Options, Up: Options 9.1 Aquiring source and target drive ==================================== -Before aquiring a drive one will eventually enable options which -influence the behavior of image loading. See next option group. +The effect of aquiring a drive may depend on several options in the +next paragraph "Influencing the behavior of image loading". If +desired, their enabling commands have to be performed before the +commands which aquire the drive. -dev address - Set input and output drive to the same address and load an - eventual ISO image. If there is no ISO image then create a blank - one. Set the image expansion method to growing. + Set input and output drive to the same address and load an ISO + image if it is present. If there is no ISO image then create a + blank one. Set the image expansion method to growing. This is only allowed as long as no changes are pending in the - currently loaded ISO image. Eventually one has to perform -commit - or -rollback first. + currently loaded ISO image. If changes are pending, then one has + to perform -commit or -rollback first. Special address string "-" means standard output, to which several restrictions apply. See above paragraph "Libburn drives". An empty address string "" gives up the current device without aquiring a new one. -indev address - Set input drive and load an eventual ISO image. If the new input - drive differs from -outdev then switch from growing to modifying - or to blind growing. It depends on the setting of -grow_blindly - which of both gets activated. The same rules and restrictions - apply as with -dev. + Set input drive and load an ISO image if present. If the new + input drive differs from -outdev then switch from growing to + modifying or to blind growing. It depends on the setting of + -grow_blindly which of both gets activated. The same rules and + restrictions apply as with -dev. -outdev address Set output drive and if it differs from the input drive then @@ -611,13 +612,12 @@ activate them only after image loading. until next -dev or -indev, where it will be reset to "auto". -displacement [-]lba - Compensate an eventual displacement of the image versus the start - address for which the image was prepared. This affects only - loading of ISO images and reading of their files. The - multi-session method of growing is not allowed as long as - -displacement is non-zero. I.e. -indev and -outdev must be - different. Eventually the displacement is reset to 0 before the - drive gets re-aquired after writing. + Compensate a displacement of the image versus the start address + for which the image was prepared. This affects only loading of ISO + images and reading of their files. The multi-session method of + growing is not allowed as long as -displacement is non-zero. I.e. + -indev and -outdev must be different. The displacement gets reset + to 0 before the drive gets re-aquired after writing. Examples: If a track of a CD starts at block 123456 and gets copied to a disk file where it begins at block 0, then this copy can be loaded @@ -647,8 +647,8 @@ activate them only after image loading. By default these are all paths which do not begin with directory "/dev". A path matches a list if one of its parent paths or itself matches - a list entry. An eventual address prefix "stdio:" or "mmc:" will - be ignored when testing for matches. + a list entry. Address prefix "stdio:" or "mmc:" will be ignored + when testing for matches. By pseudo-class "clear_list" and pseudo-patterns "banned", "caution", "harmless", or "all", the lists may be made empty. E.g.: -drive_class clear_list banned @@ -669,16 +669,16 @@ activate them only after image loading. -in_charset character_set_name Set the character set from which to convert file names when - loading an image. This has eventually to be done before specifying - -dev , -indev or -rollback. See paragraph "Character sets" for - more explanations. When loading the written image after -commit - the setting of -out_charset will be copied to -in_charset. + loading an image. See paragraph "Character sets" for more + explanations. When loading the written image after -commit the + setting of -out_charset will be copied to -in_charset. -auto_charset "on"|"off" Enable or disable recording and interpretation of the output character set name in an xattr attribute of the image root - directory. If enabled then an eventual recorded character set name - gets used as input character set when reading an image. + directory. If enabled and if a recorded character set name is + found, then this name will be used as namoe of the input character + set when reading an image. Note that the default output charset is the local character set of the terminal where `xorriso' runs. Before attributing this local character set to the produced ISO image, check whether the @@ -691,12 +691,13 @@ activate them only after image loading. image load time. Each iso_rr file object which has no inode number at image generation time will get a new unique inode number if -compliance is set to new_rr. - Mode "on" preserves eventual inode numbers from the loaded image. - When committing a session it searches for families of iso_rr files - which stem from the same disk file, have identical content - filtering and have identical properties. The family members all - get the same inode number. Whether these numbers are respected at - mount time depends on the operating system. + Mode "on" preserves inode numbers from the loaded image if such + numbers were recorded. When committing a session it searches for + families of iso_rr files which stem from the same disk file, have + identical content filtering and have identical properties. The + family members all get the same inode number. Whether these + numbers are respected at mount time depends on the operating + system. Commands -update and -update_r track splits and fusions of hard links in filesystems which have stable device and inode numbers. This can cause automatic last minute changes before the session @@ -732,14 +733,14 @@ activate them only after image loading. -md5 "on"|"all"|"off"|"load_check_off" Enable or disable processing of MD5 checksums for the overall - session and for each single data file. If enabled then images get - loaded only if eventual checksums tags of superblock and directory - tree match properly. The MD5 checksums of data files and whole - session get loaded from the image if there are any. - With options -compare and -update the eventually recorded MD5 of a - file will be used to avoid content reading from the image. Only - the disk file content will be read and compared with that MD5. - This can save much time if -disk_dev_ino "on" is not suitable. + session and for each single data file. If enabled then images with + checksum tags get loaded only if the tags of superblock and + directory tree match properly. The MD5 checksums of data files and + whole session get loaded from the image if there are any. + With options -compare and -update the recorded MD5 of a file will + be used to avoid content reading from the image. Only the disk file + content will be read and compared with that MD5. This can save + much time if -disk_dev_ino "on" is not suitable. At image generation time they are computed for each file which gets its data written into the new session. The checksums of files which have their data in older sessions get copied into the new @@ -766,7 +767,7 @@ activate them only after image loading. -disk_dev_ino "on"|"ino_only"|"off" Enable or disable processing of recorded file identification - numbers (dev_t and ino_t). They are eventually stored as xattr and + numbers (dev_t and ino_t). If enabled they are stored as xattr and allow to substantially accelerate file comparison. The root node gets a global start timestamp. If during comparison a file with younger timestamps is found in the ISO image, then it is suspected @@ -789,7 +790,7 @@ activate them only after image loading. Read-only drives do not tell the actual media type but show any media as ROM (e.g. as DVD-ROM). The session history of MMC multi-session media might be truncated to first and last session - or even be completely false. (The eventual emulated history of + or even be completely false. (The emulated history of overwriteable media is not affected by this.) To have in case of failure a chance of getting the session history and especially the address of the last session, there is a scan @@ -862,9 +863,9 @@ If both objects are directories then they get merged by recursively inserting the subobjects from filesystem into ISO image. If other file types collide then the setting of command *-overwrite* decides. Renaming of files has similar collision handling, but directories can -only be replaced, not merged. Note that -mv inserts the source objects -into an eventual existing target directory rather than attempting to -replace it. +only be replaced, not merged. Note that if the target directory exists, +then -mv inserts the source objects into this directory rather than +attempting to replace it. The commands in this section alter the ISO image and not the local filesystem. @@ -884,8 +885,8 @@ filesystem. Insert the given files or directory trees from filesystem into the ISO image. If -pathspecs is set to "on" then pattern expansion is always - disabled and character '=' has a special meaning. It eventually - separates the ISO image path from the disk path: + disabled and character '=' has a special meaning. It separates the + ISO image path from the disk path: iso_rr_path=disk_path The separator '=' can be escaped by '\'. If iso_rr_path does not begin with '/' then -cd is prepended. If disk_path does not begin @@ -894,16 +895,16 @@ filesystem. disk path. If in this case the word does not begin with '/' then -cdx is prepended to the disk_path and -cd is prepended to the iso_rr_path. - If -pathspecs is set to "off" then eventual -disk_pattern - expansion applies. The resulting words are used as both, - iso_rr_path and disk path. Eventually -cdx gets prepended to - disk_path and -cd to iso_rr_path. + If -pathspecs is set to "off" then -disk_pattern expansion + applies, if enabled. The resulting words are used as both, + iso_rr_path and disk path. Relative path words get prepended the + setting of -cdx to disk_path and the setting of -cd to iso_rr_path. -add_plainly mode If set to mode "unknown" then any command word that does not begin with "-" and is not recognized as known command will be subject to a virtual -add command. I.e. it will be used as pathspec or as - disk_path and added to the image. Eventually -disk_pattern + disk_path and added to the image. If enabled, -disk_pattern expansion applies to disk_paths. Mode "dashed" is similar to "unknown" but also adds unrecognized command words even if they begin with "-". @@ -1012,8 +1013,9 @@ filesystem. -clone iso_rr_path_original iso_rr_path_copy Create a copy of the ISO file object iso_rr_path_original with the new address iso_rr_path_copy. If the original is a directory then - copy all files and directories underneath. An eventual boot - catalog file gets not copied but is silently ignored. + copy all files and directories underneath. If iso_rr_path_original + is a boot catalog file, then it gets not copied but is silently + ignored. The copied ISO file objects have the same attributes. Copied data files refer to the same content source as their originals. The copies may then be manipulated independendly of their originals. @@ -1022,8 +1024,8 @@ filesystem. -cp_clone iso_rr_path_original [***] iso_rr_path_dest Create copies of one or more ISO file objects as with command - -clone. Eventually merge directories with existing ones, but do - not overwrite existing ISO file objects. + -clone. In case of collision merge directories with existing + ones, but do not overwrite existing ISO file objects. The rules for generating the copy addresses are the same as with command -cpr (see above) resp. shell command cp -r. Other than with -cpr, relative iso_rr_path_original will get prepended the @@ -1048,8 +1050,8 @@ File: xorriso.info, Node: SetInsert, Next: Manip, Prev: Insert, Up: Options --. You need quite a new Linux kernel to read correctly the final bytes of a file >= 4g if its size is not aligned to 2048 byte blocks. - `xorriso''s own data read capabilities are not affected by eventual - operating system size limits. They apply to mounting only. + `xorriso''s own data read capabilities are not affected by + operating system size limits. Such limits apply to mounting only. Nevertheless, the target filesystem of an -extract must be able to take the file size. @@ -1088,7 +1090,7 @@ File: xorriso.info, Node: SetInsert, Next: Manip, Prev: Insert, Up: Options -not_paths disk_path [***] Add the given paths to the list of excluded absolute disk paths. If a given path is relative, then the current -cdx is prepended to - form an absolute path. Eventual pattern matching happens at + form an absolute path. Pattern matching, if enabled, happens at definition time and not when exclusion checks are made. (Do not forget to end the list of disk_paths by "--") @@ -1154,8 +1156,8 @@ File: xorriso.info, Node: SetInsert, Next: Manip, Prev: Insert, Up: Options "on" enables pathspecs of the form *target=source* like with program mkisofs -graft-points. It also disables -disk_pattern expansion for command -add. - "off" disables pathspecs of the form target=source and eventually - enables -disk_pattern expansion. + "off" disables pathspecs of the form target=source and re-enables + -disk_pattern expansion. -overwrite "on"|"nondir"|"off" Allow or disallow to overwrite existing files in the ISO image by @@ -1273,13 +1275,14 @@ whether they stem from the loaded image or were newly inserted. Like -chmod but affecting all files below eventual directories. -setfacl acl_text iso_rr_path [***] - Attach the given ACL to the given iso_rr_paths after deleting - their eventually existing ACLs. If acl_text is empty, or contains - the text "clear" or the text "--remove-all", then the existing - ACLs will be removed and no new ones will be attached. Any other - content of acl_text will be interpreted as a list of ACL entries. - It may be in the long multi-line format as put out by -getfacl but - may also be abbreviated as follows: + Attach the given ACL to the given iso_rr_paths. If the files + already have ACLs, then those get deleted before the new ones get + into effect. If acl_text is empty, or contains the text "clear" + or the text "--remove-all", then the existing ACLs will be removed + and no new ones will be attached. Any other content of acl_text + will be interpreted as a list of ACL entries. It may be in the + long multi-line format as put out by -getfacl but may also be + abbreviated as follows: ACL entries are separated by comma or newline. If an entry is empty text or begins with "#" then it will be ignored. A valid entry has to begin by a letter out of {ugom} for "user", "group", @@ -1372,10 +1375,10 @@ whether they stem from the loaded image or were newly inserted. -hide hide_state iso_rr_path [***] Prevent the names of the given files from showing up in the directory trees of ISO 9660 and/or Joliet when the image gets - written. The eventual 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. + written. 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. Warning: Data which are hidden from the ISO 9660 tree will not be copied by the write method of modifying. Possible values of hide_state are: "iso_rr" for hiding from ISO @@ -1415,8 +1418,8 @@ File: xorriso.info, Node: CmdFind, Next: Filter, Prev: Manip, Up: Options the loaded image. -type type_letter : Matches files of the given type: "block", "char", "dir", - "pipe", "file", "link", "socket", "eltorito", "Xotic" which - eventually matches what is not matched by the other types. + "pipe", "file", "link", "socket", "eltorito", and "Xotic" + which matches what is not matched by the other types. Only the first letter is interpreted. E.g.: -find / -type d -damaged : Matches files which use data blocks marked as damaged by a @@ -1479,15 +1482,15 @@ File: xorriso.info, Node: CmdFind, Next: Filter, Prev: Manip, Up: Options Enclose a sub expression which gets evaluated first before it is processed by neighboring operators. Normal precedence is: -not, -or , -and. - -if ... -then\ ... -elseif ... -then ... -else ... -endif : + -if ... -then ... -elseif ... -then ... -else ... -endif : Enclose one or more sub expressions. If the -if expression matches, then the -then expression is evaluated as the result of the whole expression up to -endif. Else the next -elseif - expression is evaluated and eventually its -then expression. - Finally in case of no match, the -else expression is - evaluated. There may be more than one -elseif. Neither -else - nor -elseif are mandatory. If -else is missing and would be - hit, then the result is a non-match. + expression is evaluated and if it matches, its -then + expression. Finally in case of no match, the -else expression + is evaluated. There may be more than one -elseif. Neither + -else nor -elseif are mandatory. If -else is missing and + would be hit, then the result is a non-match. -if-expressions are the main use case for above test -decision. @@ -1546,9 +1549,9 @@ File: xorriso.info, Node: CmdFind, Next: Filter, Prev: Manip, Up: Options removes an eventual marking from action "update_merge". report_damage classifies files whether they hit a data block that is marked - as damaged. The result is printed together with the eventual - address of the first damaged byte, the maximum span of - damages, file size, and the path of the file. + as damaged. The result is printed together with the address + of the first damaged byte, the maximum span of damages, file + size, and the path of the file. report_lba prints files which are associated to image data blocks. It tells the logical block address, the block number, the byte @@ -1559,20 +1562,20 @@ File: xorriso.info, Node: CmdFind, Next: Filter, Prev: Manip, Up: Options prints access permissions in ACL text form to the result channel. setfacl - attaches ACLs after removing eventually exiting ones. The new - ACL is given in text form as defined with option -setfacl. + attaches ACLs after removing existing ones. The new ACL is + given in text form as defined with option -setfacl. E.g.: -exec setfacl u:lisa:rw,u::rw,g::r,o::-,m::rw -- getfattr - prints eventual xattr name-value pairs from user namespace to - the result channel. + prints xattr name-value pairs from user namespace to the + result channel. get_any_xattr - prints eventual xattr name-value pairs from any namespace - except ACL to the result channel. This is mostly for - debugging of namespace "isofs". + prints xattr name-value pairs from any namespace except ACL + to the result channel. This is mostly for debugging of + namespace "isofs". get_md5 - prints eventual recorded MD5 sum together with file path. + prints the MD5 sum, if recorded, together with file path. check_md5 - compares eventual recorded MD5 sum with the file content and + compares the MD5 sum, if recorded, with the file content and reports if mismatch. E.g.: -find / -not -pending_data -exec check_md5 FAILURE -- make_md5 @@ -1651,8 +1654,8 @@ there are many small files. "default" means that no other option is intended. "suffix=..." sets a file name suffix. If it is not empty then it will be appended to the file name or removed from it. - "remove_suffix" will remove an eventual file name suffix rather - than appending it. + "remove_suffix" will remove a file name suffix rather than + appending it. "if_nonempty" will leave 0-sized files unfiltered. "if_reduction" will try filtering and revoke it if the content size does not shrink. @@ -1700,7 +1703,7 @@ there are many small files. method of growing is in effect (i.e -indev and -outdev are identical). The reserved filter name "--remove-all-filters" revokes filtering. - This will revoke eventual suffix renamings as well. Use + This will revoke suffix renamings as well. Use "--remove-all-filters+" to prevent any suffix renaming. -set_filter_r name iso_rr_path [***] @@ -1720,8 +1723,8 @@ File: xorriso.info, Node: Writing, Next: SetWrite, Prev: Filter, Up: Options -rollback_end if immediate program end is desired.) -commit - Perform the write operation. Afterwards eventually make the - -outdev the new -dev and load the image from there. Switch to + Perform the write operation. Afterwards, if -outdev is readable, + make it the new -dev and load the image from there. Switch to growing mode. (A subsequent -outdev will activate modification mode or blind growing.) -commit is performed automatically at end of program if there are uncommitted manipulations pending. @@ -1749,7 +1752,7 @@ File: xorriso.info, Node: Writing, Next: SetWrite, Prev: Filter, Up: Options -commit_eject "in"|"out"|"all"|"none" Combined -commit and -eject. When writing has finished do not make -outdev the new -dev, and load no ISO image. Rather eject -indev - and/or -outdev. Eventually give up any non-ejected drive. + and/or -outdev. Give up any non-ejected drive. -blank mode Make media ready for writing from scratch (if not -dummy is @@ -2141,7 +2144,7 @@ media, because they appear to inadverted readers as one single session. But with multi-session media CD-R[W], DVD-R[W], DVD+R, it implies that the whole bootable system has to reside already in the first session and that the last session still has to bear all files which the booted -system expects after eventually mounting the ISO image. +system expects after mounting the ISO image. If a boot image from ISOLINUX or GRUB is known to be present on media then it is advised to patch it when a follow-up session gets written. But one should not rely on the capability to influence the bootability @@ -2156,10 +2159,10 @@ filesystem and announced by an MBR partition table entry. -boot_image "any"|"isolinux"|"grub" "discard"|"keep"|"patch"|"show_status"|bootspec|"next" - Define the handling of an eventual set of El Torito boot images - which has been read from an existing ISO image or define how to - make a prepared boot image file set bootable. Such file sets get - produced by ISOLINUX or GRUB. + Define the handling of a set of El Torito boot images which has + been read from an existing ISO image or define how to make a + prepared boot image file set bootable. Such file sets get produced + by ISOLINUX or GRUB. Each -boot_image command has two arguments: type and setting. More than one -boot_image command may be used to define the handling of one or more boot images. Sequence matters. @@ -2184,11 +2187,10 @@ filesystem and announced by an MBR partition table entry. *show_status* will print what is known about the loaded boot images and their designated fate. - A *bootspec* is a word of the form name=value and is used to - describe the parameters of a boot image by an El Torito record and - eventually a MBR. The names "dir", "bin_path", "efi_path" lead to - El Torito bootable images. Name "system_area" activates a given - file as MBR. + A *bootspec* is a word of the form name=valuei. It is used to + describe the parameters of a boot image by an El Torito record or + a MBR. The names "dir", "bin_path", "efi_path" lead to El Torito + bootable images. Name "system_area" activates a given file as MBR. On all media types this is possible within the first session. In further sessions an existing boot image can get replaced by a new one, but depending on the media type this may have few effect at @@ -2244,8 +2246,7 @@ filesystem and announced by an MBR partition table entry. catalog. *next* ends the definition of a boot image and starts a new one. Any following -bootimage bootspecs will affect the new image. The - first "next" discards eventually loaded boot images and their - catalog. + first "next" discards loaded boot images and their catalog. *discard* gives up an existing boot catalog and its boot images. *keep* keeps or copies boot images unaltered and writes a new catalog. @@ -2275,7 +2276,7 @@ filesystem and announced by an MBR partition table entry. "partition_table=on". If so, then those parameters get updated when the new System Area is written. Special "system_area=/dev/zero" causes 32k of NUL-bytes. Use this - to discard an MBR which eventually was loaded with the ISO image. + to discard an MBR which was loaded with the ISO image. *partition_offset=*2kb_block_adr causes 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 @@ -2310,19 +2311,18 @@ filesystem and announced by an MBR partition table entry. MIPS Big Endian boot file and causes 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 eventually provided by system_area=. Up to 15 - boot files can be declared by mips_path=. + bytes of any data provided by system_area=. Up to 15 boot files + can be declared by mips_path=. *mipsel_path=*iso_rr_path declares 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 eventually provided by system_area=. Only a single boot file - can be declared by mipsel_path=. + data provided by system_area=. Only a single boot file can be + declared by mipsel_path=. *sparc_label=*text causes the production of a SUN Disk Label with the given text as ASCII label. This boot block format allows to append images for partitions 2 to 8. Partition 1 will always be the ISO image. See option -append_partition. The first 512 bytes - of any data eventually provided by system_area= will be - overwritten. + of any data provided by system_area= will be overwritten. *mips_discard* and *sparc_discard* revoke any boot file declarations made by mips_path= or mipsel_path=. They also disable production of SUN Disk Label. This removes the ban on production @@ -2383,13 +2383,12 @@ 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 file address is decisive for To=From mapping, not for file recognition. -After eventual To=From mapping, the file address gets written into the -.jigdo file. Jigdo restore tools will convert these addresses into -really reachable data source addresses from which they can read. +After To=From mapping, the file address gets written into the .jigdo +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 `xorriso' will refuse to write to non-blank targets, it will disable multi-session -emulation, and eventual padding will be counted as part of the ISO -image. +emulation, and padding will be counted as part of the ISO image. -jigdo parameter_name value Clear Jigdo Template Extraction parameter list or add a parameter @@ -2564,10 +2563,10 @@ failed unexpectedly. on signals caused by severe program errors. Mode "on" is the default. It uses the signal handler of libburn which produces ugly messages but puts much effort in releasing - eventually used optical drives before `xorriso' ends. + optical drives before `xorriso' ends. Mode "off" as first -signal_handling among the start arguments - prevents all own signal precautions of `xorriso'. Eventually - inherited signal handler settings stay as they are. + prevents all own signal precautions of `xorriso'. Inherited signal + handler settings stay as they are. It works like "sig_dfl" if given after other signal handling was already established at program start. Mode "sig_dfl" uses the system provided default handling of @@ -2671,7 +2670,7 @@ File: xorriso.info, Node: Inquiry, Next: Navigate, Prev: DialogCtl, Up: Opti libburn standard device files. This is only possible when no ISO image changes are pending. After this option was executed, there is no drive current and no - image loaded. Eventually one has to aquire a drive again. + image loaded. In order to be visible, a device has to offer rw-permissions with its libburn standard device file. Thus it might be only the *superuser* who is able to see all drives. @@ -2688,7 +2687,7 @@ File: xorriso.info, Node: Inquiry, Next: Navigate, Prev: DialogCtl, Up: Opti or DVD-ROM with only one or two sessions on it. The last of these sessions is supposed to be the most recent real session then. Some read-only drives and media show no usable session history at - all. Eventually option -rom_toc_scan might help. + all. Option -rom_toc_scan might help. -mount_cmd drive entity id path Emit an appropriate command line for mounting the ISO session @@ -2911,11 +2910,10 @@ File: xorriso.info, Node: Navigate, Next: Verify, Prev: Inquiry, Up: Options -show_stream iso_rr_path [***] Display the content stream chain of data files in the ISO image. The chain consists of the iso_rr_name and one or more streams, - separated by " < " marks. A stream consists of one or more texts - eventually in "-quotation marks, eventually separated by ":" - characters. The first text describes the stream type, the - following ones describe its individual properties. Frequently - used types are: + separated by " < " marks. A stream description consists of one or + more texts, separated by ":" characters. The first text tells the + stream type, the following ones, if ever, describe its individual + properties. Frequently used types are: disk:'disk_path' for local filesystem objects. image:'iso_rr_path' for ISO image file objects. cout:'disk_path offset count' for -cut_out files. @@ -2947,7 +2945,7 @@ image. They work independently of the media type and can detect transmission errors. -check_media [option [option ...]] -- - Try to read data blocks from the indev drive, eventually copy them + Try to read data blocks from the indev drive, optionally copy them to a disk file, and finally report about the encountered quality. Several options may be used to modify the default behavior. The options given with this command override the default settings @@ -2962,14 +2960,14 @@ transmission errors. Alternatively it is possible to report damaged files rather than blocks. If -md5 is "on" then the default mode what=tracks looks out for - libisofs checksum tags for the ISO session data and eventually - checks them against the checksums computed from the data stream. + libisofs checksum tags for the ISO session data and checks them + against the checksums computed from the data stream. -check_media_defaults [option [option ...]] -- Preset options for runs of -check_media, -extract_cut and - best_effort file extraction. Eventual options given with - -check_media will override the preset options. -extract_cut will - override some options automatically. + best_effort file extraction. Options given with -check_media will + override the preset options. -extract_cut will override some + options automatically. An option consists of a keyword, a "=" character, and a value. Options may override each other. So their sequence matters. The default setting at program start is: @@ -3035,16 +3033,14 @@ transmission errors. tries to read the file given by disk_path as sector bitmap and to store such a map file after the scan run. The bitmap tells which blocks have been read successfully in previous - runs. It allows to do several scans on the same media, - eventually with intermediate eject, in order to collect - readable blocks whenever the drive is lucky enough to produce - them. The stored file contains a human readable TOC of tracks - and their start block addresses, followed by binary bitmap - data. + runs. It allows to do several scans on the same media, even + with intermediate eject, in order to collect readable blocks + whenever the drive is lucky enough to produce them. The + stored file contains a human readable TOC of tracks and their + start block addresses, followed by binary bitmap data. map_with_volid="on" - examines tracks whether they are ISO images and eventually - prints their volume ids into the human readable TOC of - sector_map=. + examines tracks whether they are ISO images and prints their + volume ids into the human readable TOC of sector_map=. patch_lba0="on" transfers within the data_to= file a copy of the currently loaded session head to the start of that file and patches it @@ -3251,10 +3247,10 @@ said programs trigger comparable actions. of mkisofs emulation in the context of a `xorriso' run. Other than with the "cdrecord" personality there is no automatic -commit at the end of a "mkisofs" option list. Verbosity settings - -v (= "UPDATE") and -quiet (= "SORRY") persist. The output file, - eventually chosen with -o, persists until things happen like - -commit, -rollback, -dev, or end of `xorriso'. -pacifier gets set - to "mkisofs" if files are added to the image. + -v (= "UPDATE") and -quiet (= "SORRY") persist. The output file + persists until things happen like -commit, -rollback, -dev, or end + of `xorriso'. -pacifier gets set to "mkisofs" if files are added + to the image. -graft-points is equivalent to -pathspecs on. Note that pathspecs without "=" are interpreted differently than with `xorriso' option -add. Directories get merged with the root directory of the ISO @@ -3271,8 +3267,8 @@ said programs trigger comparable actions. drive to standard output. -print-size inhibits automatic image production at program end. This ban is lifted only if the pending image changes get discarded. - Eventual padding is counted as part of the ISO image if not option - -emul-toc is given. + Padding is counted as part of the ISO image if not option -emul-toc + is given. If no -iso-level is given, then level 1 is chosen when the first file or directory is added to the image. At the same occasion directory names get allowed to violate the standard by -compliance @@ -3342,7 +3338,7 @@ said programs trigger comparable actions. The scope is only a single data track per session to be written to blank, overwriteable, or appendable media. The media gets closed if closing is applicable and not option -multi is present. - An eventually acquired input drive is given up. This is only + If an input drive was aquired, then it is given up. This is only allowed if no image changes are pending. dev= must be given as `xorriso' device address. Addresses like 0,0,0 or ATA:1,1,0 are not supported. @@ -3359,9 +3355,8 @@ said programs trigger comparable actions. If `xorriso' is started with one of the leafnames "xorrecord", "cdrskin", "cdrecord", or "wodim", then it automatically prepends -as "cdrskin" to the command line arguments. I.e. all arguments - will be interpreted cdrecord style until "--" is encountered and - an eventual commit happens. From then on, options are interpreted - as `xorriso' options. + will be interpreted cdrecord style until "--" is encountered. + From then on, options are interpreted as `xorriso' options. --no_rc as first argument of such a program start prevents interpretation of `xorriso' startup files. See section FILES below. @@ -3407,8 +3402,8 @@ File: xorriso.info, Node: Scripting, Next: Frontend, Prev: Emulation, Up: Op -no_rc Only if used as first command line argument this option prevents - reading and interpretation of eventual startup files. See section - FILES below. + reading and interpretation of startup files. See section FILES + below. -options_from_file fileaddress Read quoted input from fileaddress and execute it like dialog @@ -3533,15 +3528,15 @@ File: xorriso.info, Node: Scripting, Next: Frontend, Prev: Emulation, Up: Op "-" is recognized that way. -end - End program after writing eventually pending changes. + End program after writing pending changes. -rollback_end Discard pending changes. End program immediately. # any text Only in dialog or file execution mode, and only as first - non-whitespace in line: Do not execute the line but eventually - store it in history. + non-whitespace in line: Do not execute the line but store it in + readline history.  File: xorriso.info, Node: Frontend, Next: ExDevices, Prev: Scripting, Up: Options @@ -3763,7 +3758,7 @@ character set ISO-8859-1 but that the readers expected UTF-8. Now a new session with the same files gets added with converted file names. In order to avoid any weaknesses of the local character set, this command pretends that it uses already the final target set UTF-8. Therefore -strange file names may appear in eventual messages which will be made +strange file names may appear in messages, which will be made terminal-safe by option -backslash_codes. $ xorriso -in_charset ISO-8859-1 -local_charset UTF-8 \ @@ -4014,7 +4009,7 @@ First check which backup sessions are on the media: $ xorriso -outdev /dev/sr0 -toc Then load the desired session and copy the file trees to disk. Enable -restoring of ACL, xattr and hard links. Avoid to eventually create +restoring of ACL, xattr and hard links. Avoid to create /home/thomas/restored without rwx-permission. $ xorriso -for_backup \ @@ -4041,10 +4036,10 @@ $ xorriso -abort_on NEVER -indev /dev/sr0 \ -check_media time_limit=1800 report=blocks_files \ data_to="$HOME"/dvd_copy sector_map="$HOME"/dvd_copy.map -- -This can be repeated several times, eventually with -eject or with other --indev drives. See the human readable part of "$HOME"/dvd_copy.map for -addresses which can be used on "$HOME"/dvd_copy with mount option -o -sbsector= resp. -s. +This can be repeated several times, if necessary with -eject or with +other -indev drives. See the human readable part of +"$HOME"/dvd_copy.map for addresses which can be used on +"$HOME"/dvd_copy with mount option -o sbsector= resp. -s.  File: xorriso.info, Node: Files, Next: Seealso, Prev: Examples, Up: Top @@ -4177,14 +4172,14 @@ File: xorriso.info, Node: CommandIdx, Next: ConceptIdx, Prev: Legal, Up: Top * -acl controls handling of ACLs: Loading. (line 142) * -add inserts one or more paths: Insert. (line 42) * -add_plainly inserts one or more paths: Insert. (line 61) -* -alter_date sets timestamps in ISO image: Manip. (line 146) -* -alter_date_r sets timestamps in ISO image: Manip. (line 166) +* -alter_date sets timestamps in ISO image: Manip. (line 147) +* -alter_date_r sets timestamps in ISO image: Manip. (line 167) * -append_partition adds arbitrary file after image end: Bootable. - (line 202) + (line 199) * -application_id sets application id: SetWrite. (line 119) * -as emulates mkisofs or cdrecord: Emulation. (line 13) -* -assert_volid rejects undesired images: Loading. (line 84) -* -auto_charset learns character set from image: Loading. (line 99) +* -assert_volid rejects undesired images: Loading. (line 83) +* -auto_charset learns character set from image: Loading. (line 97) * -backslash_codes enables backslash conversion: Scripting. (line 49) * -ban_stdio_write demands real drive: Loading. (line 246) * -biblio_file sets biblio file name: SetWrite. (line 167) @@ -4194,8 +4189,8 @@ File: xorriso.info, Node: CommandIdx, Next: ConceptIdx, Prev: Legal, Up: Top * -cd sets working directory in ISO: Navigate. (line 7) * -cdx sets working directory on disk: Navigate. (line 16) * -charset sets input/output character set: Charset. (line 43) -* -check_md5 verifies file checksum: Verify. (line 146) -* -check_md5_r verifies file tree checksums: Verify. (line 162) +* -check_md5 verifies file checksum: Verify. (line 144) +* -check_md5_r verifies file tree checksums: Verify. (line 160) * -check_media reads media block by block: Verify. (line 21) * -check_media_defaults sets -check_media options: Verify. (line 40) * -chgrp sets group in ISO image: Manip. (line 50) @@ -4215,20 +4210,20 @@ File: xorriso.info, Node: CommandIdx, Next: ConceptIdx, Prev: Legal, Up: Top * -compare_r reports ISO/disk differences: Navigate. (line 152) * -compliance controls standard compliance: SetWrite. (line 14) * -copyright_file sets copyright file name: SetWrite. (line 154) -* -cp_clone copies ISO directory tree: Insert. (line 182) +* -cp_clone copies ISO directory tree: Insert. (line 183) * -cp_rx copies file trees to disk: Restore. (line 104) * -cpax copies files to disk: Restore. (line 100) * -cpr inserts like with cp -r: Insert. (line 152) * -cpx copies files to disk: Restore. (line 88) * -cut_out inserts piece of data file: Insert. (line 126) -* -dev aquires one drive for input and output: AqDrive. (line 10) +* -dev aquires one drive for input and output: AqDrive. (line 12) * -devices gets list of drives: Inquiry. (line 7) * -dialog enables dialog mode: DialogCtl. (line 7) * -disk_dev_ino fast incremental backup: Loading. (line 189) * -disk_pattern controls pattern expansion: Insert. (line 31) * -displacement compensate altered image start address: Loading. (line 35) -* -drive_class controls drive accessability: Loading. (line 54) +* -drive_class controls drive accessability: Loading. (line 53) * -du show directory size in ISO image: Navigate. (line 88) * -dummy controls write simulation: SetWrite. (line 251) * -dus show directory size in ISO image: Navigate. (line 92) @@ -4258,15 +4253,15 @@ File: xorriso.info, Node: CommandIdx, Next: ConceptIdx, Prev: Legal, Up: Top * -getfattr shows xattr in ISO image: Navigate. (line 80) * -getfattr_r shows xattr in ISO image: Navigate. (line 84) * -gid sets global ownership: SetWrite. (line 195) -* -grow_blindly overides next writeable address: AqDrive. (line 44) -* -hardlinks controls handling of hard links: Loading. (line 110) +* -grow_blindly overides next writeable address: AqDrive. (line 46) +* -hardlinks controls handling of hard links: Loading. (line 109) * -help prints help text: Scripting. (line 20) -* -hide excludes file names from directory trees: Manip. (line 170) +* -hide excludes file names from directory trees: Manip. (line 171) * -history brings text into readline history: Scripting. (line 26) -* -in_charset sets input character set: Loading. (line 92) -* -indev aquires a drive for input: AqDrive. (line 22) +* -in_charset sets input character set: Loading. (line 91) +* -indev aquires a drive for input: AqDrive. (line 24) * -iso_rr_pattern controls pattern expansion: Manip. (line 10) -* -jigdo clears JTE or or adds parameter to JTE: Jigdo. (line 34) +* -jigdo clears JTE or or adds parameter to JTE: Jigdo. (line 33) * -joliet enables production of Joliet tree: SetWrite. (line 10) * -list_delimiter replaces '--': Scripting. (line 42) * -list_formats lists available formats: Writing. (line 110) @@ -4300,9 +4295,9 @@ File: xorriso.info, Node: CommandIdx, Next: ConceptIdx, Prev: Legal, Up: Top * -options_from_file reads commands from file: Scripting. (line 12) * -osirrox enables ISO-to-disk copying: Restore. (line 18) * -out_charset sets output character set: SetWrite. (line 185) -* -outdev aquires a drive for output: AqDrive. (line 29) +* -outdev aquires a drive for output: AqDrive. (line 31) * -overwrite enables overwriting in ISO: SetInsert. (line 127) -* -pacifier controls pacifier text form: Emulation. (line 159) +* -pacifier controls pacifier text form: Emulation. (line 158) * -padding sets amount or mode of image padding: SetWrite. (line 268) * -page set terminal geometry: DialogCtl. (line 19) * -paste_in copies file into disk file: Restore. (line 117) @@ -4324,7 +4319,7 @@ File: xorriso.info, Node: CommandIdx, Next: ConceptIdx, Prev: Legal, Up: Top * -quoted_not_list sets exclusions: SetInsert. (line 72) * -quoted_path_list inserts paths from disk file: Insert. (line 80) * -read_mkisofsrc searches and reads .mkisofsrc file: Emulation. - (line 147) + (line 146) * -reassure enables confirmation question: DialogCtl. (line 32) * -report_about controls verbosity: Exception. (line 55) * -return_with controls exit value: Exception. (line 39) @@ -4334,20 +4329,20 @@ File: xorriso.info, Node: CommandIdx, Next: ConceptIdx, Prev: Legal, Up: Top * -rollback discards pending changes: Writing. (line 9) * -rollback_end ends program without writing: Scripting. (line 137) * -rom_toc_scan searches for sessions: Loading. (line 210) -* -scdbackup_tag enables scdbackup checksum tag: Emulation. (line 169) +* -scdbackup_tag enables scdbackup checksum tag: Emulation. (line 168) * -scsi_log reports SCSI commands: Scripting. (line 125) * -session_log logs written sessions: Scripting. (line 116) * -session_string composes session info line: Inquiry. (line 56) * -set_filter applies filter to file: Filter. (line 60) * -set_filter_r applies filter to file tree: Filter. (line 85) * -setfacl sets ACL in ISO image: Manip. (line 73) -* -setfacl_list sets ACL in ISO image: Manip. (line 100) -* -setfacl_r sets ACL in ISO image: Manip. (line 97) -* -setfattr sets xattr in ISO image: Manip. (line 110) -* -setfattr_list sets xattr in ISO image: Manip. (line 126) -* -setfattr_r sets xattr in ISO image: Manip. (line 123) +* -setfacl_list sets ACL in ISO image: Manip. (line 101) +* -setfacl_r sets ACL in ISO image: Manip. (line 98) +* -setfattr sets xattr in ISO image: Manip. (line 111) +* -setfattr_list sets xattr in ISO image: Manip. (line 127) +* -setfattr_r sets xattr in ISO image: Manip. (line 124) * -show_stream shows data source and filters: Navigate. (line 162) -* -show_stream_r shows data source and filters: Navigate. (line 177) +* -show_stream_r shows data source and filters: Navigate. (line 176) * -signal_handling controls handling of system signals: Exception. (line 69) * -speed set write speed: SetWrite. (line 211) @@ -4384,33 +4379,33 @@ File: xorriso.info, Node: ConceptIdx, Prev: CommandIdx, Up: Top * ACL, _definiton: Extras. (line 38) * ACL, control handling, -acl: Loading. (line 142) * ACL, set in ISO image, -setfacl: Manip. (line 73) -* ACL, set in ISO image, -setfacl_list: Manip. (line 100) -* ACL, set in ISO image, -setfacl_r: Manip. (line 97) +* ACL, set in ISO image, -setfacl_list: Manip. (line 101) +* ACL, set in ISO image, -setfacl_r: Manip. (line 98) * ACL, show in ISO image, -getfacl: Navigate. (line 69) * ACL, show in ISO image, -getfacl_r: Navigate. (line 76) * Appendable media, _definition: Media. (line 38) -* Appended Filesystem Image, -append_partition: Bootable. (line 202) -* Backslash Interpretation, _definition: Processing. (line 49) +* Appended Filesystem Image, -append_partition: Bootable. (line 199) +* Backslash Interpretation, _definition: Processing. (line 48) * Backup, enable fast incremental, -disk_dev_ino: Loading. (line 189) * Backup, enable features, -for_backup: Loading. (line 184) -* Backup, scdbackup checksum tag, -scdbackup: Emulation. (line 169) +* Backup, scdbackup checksum tag, -scdbackup: Emulation. (line 168) * Blank media, _definition: Media. (line 29) * Blind growing, _definition: Methods. (line 40) * Bootability, control, -boot_image: Bootable. (line 26) * Bugs, reporting: Bugreport. (line 6) * cdrecord, Emulation: Emulation. (line 111) * Character Set, _definition: Charset. (line 6) -* Character Set, for input, -in_charset: Loading. (line 92) +* Character Set, for input, -in_charset: Loading. (line 91) * Character Set, for input/output, -charset: Charset. (line 43) * Character Set, for output, -out_charset: SetWrite. (line 185) -* Character set, learn from image, -auto_charset: Loading. (line 99) +* Character set, learn from image, -auto_charset: Loading. (line 97) * Character Set, of terminal, -local_charset: Charset. (line 47) * Closed media, _definition: Media. (line 43) * Comment, #: Scripting. (line 140) * Control, signal handling, -signal_handling: Exception. (line 69) * Create, new ISO image, _definiton: Methods. (line 6) -* Cylinder alignment, _definiton: Bootable. (line 169) -* Cylinder size, _definiton: Bootable. (line 158) +* Cylinder alignment, _definiton: Bootable. (line 167) +* Cylinder size, _definiton: Bootable. (line 156) * Damaged track and session, close, -close_damaged: Writing. (line 122) * Delete, from ISO image, -rm: Manip. (line 21) * Delete, from ISO image, -rm_r: Manip. (line 28) @@ -4420,19 +4415,19 @@ File: xorriso.info, Node: ConceptIdx, Prev: CommandIdx, Up: Top * Dialog, enable dialog mode, -dialog: DialogCtl. (line 7) * Dialog, line editing, -use_readline: DialogCtl. (line 28) * Dialog, terminal geometry, -page: DialogCtl. (line 19) -* Directories, copy, -cp_clone: Insert. (line 182) +* Directories, copy, -cp_clone: Insert. (line 183) * Directory, copy, -clone: Insert. (line 171) * Directory, create, -mkdir: Insert. (line 166) * Directory, delete, -rmdir: Manip. (line 32) * disk_path, _definition: Insert. (line 6) * Drive, _definiton: Drives. (line 6) -* Drive, accessability, -drive_class: Loading. (line 54) +* Drive, accessability, -drive_class: Loading. (line 53) * Drive, classify stdio, -early_stdio_test: Loading. (line 251) * Drive, demand real MMC, -ban_stdio_write: Loading. (line 246) * Drive, eject tray, -eject: Writing. (line 36) -* Drive, for input and output, -dev: AqDrive. (line 10) -* Drive, for input, -indev: AqDrive. (line 22) -* Drive, for output, -outdev: AqDrive. (line 29) +* Drive, for input and output, -dev: AqDrive. (line 12) +* Drive, for input, -indev: AqDrive. (line 24) +* Drive, for output, -outdev: AqDrive. (line 31) * Drive, get drive list, -devices: Inquiry. (line 7) * Drive, list supported media, -list_profiles: Writing. (line 136) * Drive, reduce activity, -calm_drive: Loading. (line 235) @@ -4440,10 +4435,10 @@ File: xorriso.info, Node: ConceptIdx, Prev: CommandIdx, Up: Top * Drive, write and eject, -commit_eject: Writing. (line 40) * El Torito, _definiton: Extras. (line 19) * Emulation, -as: Emulation. (line 13) -* Emulation, .mkisofsrc, -read_mkisofsrc: Emulation. (line 147) +* Emulation, .mkisofsrc, -read_mkisofsrc: Emulation. (line 146) * Emulation, cdrecord, -as: Emulation. (line 111) * Emulation, mkisofs, -as: Emulation. (line 16) -* Emulation, pacifier form, -pacifier: Emulation. (line 159) +* Emulation, pacifier form, -pacifier: Emulation. (line 158) * Examples: Examples. (line 6) * Filter, _definition: Filter. (line 6) * Filter, apply to file tree, -set_filter_r: Filter. (line 85) @@ -4451,17 +4446,17 @@ File: xorriso.info, Node: ConceptIdx, Prev: CommandIdx, Up: Top * Filter, ban registration, -close_filter_list: Filter. (line 52) * Filter, register, -external_filter: Filter. (line 20) * Filter, show chain, -show_stream: Navigate. (line 162) -* Filter, show chains of tree, -show_stream_r: Navigate. (line 177) +* Filter, show chains of tree, -show_stream_r: Navigate. (line 176) * Filter, unregister, -unregister_filter: Filter. (line 48) * Filter, zisofs parameters, -zisofs: SetWrite. (line 199) * Group, global in ISO image, -gid: SetWrite. (line 195) * Group, in ISO image, -chgrp: Manip. (line 50) * Group, in ISO image, -chgrp_r: Manip. (line 55) * Growing, _definition: Methods. (line 19) -* Hard links, control handling, -hardlinks: Loading. (line 110) -* hidden, set in ISO image, -hide: Manip. (line 170) +* Hard links, control handling, -hardlinks: Loading. (line 109) +* hidden, set in ISO image, -hide: Manip. (line 171) * Image, _definition: Model. (line 9) -* Image, demand volume id, -assert_volid: Loading. (line 84) +* Image, demand volume id, -assert_volid: Loading. (line 83) * Image, discard pending changes, -rollback: Writing. (line 9) * Image, set abstract file name, -abstract_file: SetWrite. (line 160) * Image, set application id, -application_id: SetWrite. (line 119) @@ -4497,16 +4492,16 @@ File: xorriso.info, Node: ConceptIdx, Prev: CommandIdx, Up: Top * Insert, pathspecs, -add: Insert. (line 42) * Insert, piece of data file, -cut_out: Insert. (line 126) * iso_rr_path, _definition: Insert. (line 7) -* Jigdo Template Extraction, -jigdo: Jigdo. (line 34) +* Jigdo Template Extraction, -jigdo: Jigdo. (line 33) * Jigdo Template Extraction, _definition: Jigdo. (line 6) * List delimiter, _definiton: Processing. (line 8) * MBR, _definiton: Extras. (line 26) -* MBR, set, -boot_image system_area=: Bootable. (line 123) +* MBR, set, -boot_image system_area=: Bootable. (line 121) * MD5, control handling, -md5: Loading. (line 155) * Media, erase, -blank: Writing. (line 45) * Media, format, -format: Writing. (line 72) * Media, list formats, -list_formats: Writing. (line 110) -* MIPS boot file, activation: Bootable. (line 178) +* MIPS boot file, activation: Bootable. (line 176) * mkisofs, Emulation: Emulation. (line 16) * Modifying, _definition: Methods. (line 27) * Multi-session media, _definition: Media. (line 7) @@ -4527,13 +4522,13 @@ File: xorriso.info, Node: ConceptIdx, Prev: CommandIdx, Up: Top * Navigate, set ISO working directory, -cd: Navigate. (line 7) * Navigate, tell disk working directory, -pwdx: Navigate. (line 23) * Navigate, tell ISO working directory, -pwd: Navigate. (line 20) -* Next writeable address, -grow_blindly: AqDrive. (line 44) +* Next writeable address, -grow_blindly: AqDrive. (line 46) * Overwriteable media, _definition: Media. (line 14) * Ownership, global in ISO image, -uid: SetWrite. (line 191) * Ownership, in ISO image, -chown: Manip. (line 42) * Ownership, in ISO image, -chown_r: Manip. (line 47) -* Partition offset, _definiton: Bootable. (line 148) -* Partition table, _definiton: Bootable. (line 130) +* Partition offset, _definiton: Bootable. (line 146) +* Partition table, _definiton: Bootable. (line 128) * Pathspec, _definition: SetInsert. (line 120) * Pattern expansion, _definition: Processing. (line 22) * Pattern expansion, for disk paths, -disk_pattern: Insert. (line 31) @@ -4568,7 +4563,7 @@ File: xorriso.info, Node: ConceptIdx, Prev: CommandIdx, Up: Top * Program, set name, -prog: Frontend. (line 30) * Program, show current settings, -status: Scripting. (line 29) * Program, status history, -status_history_max: Scripting. (line 38) -* Quoted input, _definiton: Processing. (line 43) +* Quoted input, _definiton: Processing. (line 42) * Recovery, retrieve blocks, -check_media: Verify. (line 21) * Rename, in ISO image, -mv: Manip. (line 35) * Restore, copy file into disk file, -paste_in: Restore. (line 117) @@ -4589,21 +4584,21 @@ File: xorriso.info, Node: ConceptIdx, Prev: CommandIdx, Up: Top * Session, mount command line, -mount_cmd: Inquiry. (line 31) * Session, mount parameters, -mount_opts: Inquiry. (line 47) * Session, select as input, -load: Loading. (line 11) -* SUN Disk Label, production: Bootable. (line 189) -* SUN SPARC boot images, activation: Bootable. (line 223) -* System area, _definiton: Bootable. (line 123) +* SUN Disk Label, production: Bootable. (line 187) +* SUN SPARC boot images, activation: Bootable. (line 220) +* System area, _definiton: Bootable. (line 121) * Table-of-content, search sessions, -rom_toc_scan: Loading. (line 210) * Table-of-content, show, -toc: Inquiry. (line 18) -* Timestamps, set in ISO image, -alter_date: Manip. (line 146) -* Timestamps, set in ISO image, -alter_date_r: Manip. (line 166) +* Timestamps, set in ISO image, -alter_date: Manip. (line 147) +* Timestamps, set in ISO image, -alter_date_r: Manip. (line 167) * Tree, disk, traverse, -findx: Navigate. (line 105) * Tree, ISO, traverse and alter, -find: CmdFind. (line 7) * Verify, check blocks, -check_media: Verify. (line 21) * Verify, compare ISO and disk file, -compare: Navigate. (line 139) * Verify, compare ISO and disk tree, -compare_r: Navigate. (line 152) * Verify, compare ISO and disk, -compare_l: Navigate. (line 157) -* Verify, file checksum, -check_md5: Verify. (line 146) -* Verify, file tree checksums, -check_md5_r: Verify. (line 162) +* Verify, file checksum, -check_md5: Verify. (line 144) +* Verify, file tree checksums, -check_md5_r: Verify. (line 160) * Verify, preset -check_media, -check_media_defaults: Verify. (line 40) * Write, block size, -dvd_obs: SetWrite. (line 238) * Write, bootability, -boot_image: Bootable. (line 26) @@ -4623,9 +4618,9 @@ File: xorriso.info, Node: ConceptIdx, Prev: CommandIdx, Up: Top * Write, simulation, -dummy: SetWrite. (line 251) * xattr, _definiton: Extras. (line 52) * xattr, control handling, -xattr: Loading. (line 150) -* xattr, set in ISO image, -setfattr: Manip. (line 110) -* xattr, set in ISO image, -setfattr_list: Manip. (line 126) -* xattr, set in ISO image, -setfattr_r: Manip. (line 123) +* xattr, set in ISO image, -setfattr: Manip. (line 111) +* xattr, set in ISO image, -setfattr_list: Manip. (line 127) +* xattr, set in ISO image, -setfattr_r: Manip. (line 124) * xattr, show in ISO image, -getfattr: Navigate. (line 80) * xattr, show in ISO image, -getfattr_r: Navigate. (line 84) @@ -4635,56 +4630,56 @@ Tag Table: Node: Top420 Node: Overview1375 Node: Model3264 -Node: Media6150 -Node: Methods8812 -Node: Drives11370 -Node: Extras14678 -Node: Processing18167 -Node: Dialog21667 -Node: Options23330 -Node: AqDrive24938 -Node: Loading27846 -Node: Insert42182 -Node: SetInsert51801 -Node: Manip60375 -Node: CmdFind69060 -Node: Filter80363 -Node: Writing84720 -Node: SetWrite91955 -Node: Bootable106001 -Node: Jigdo119321 -Node: Charset123585 -Node: Exception126344 -Node: DialogCtl132484 -Node: Inquiry135071 -Node: Navigate139454 -Node: Verify147394 -Node: Restore155989 -Node: Emulation162649 -Node: Scripting172522 -Node: Frontend178672 -Node: Examples179971 -Node: ExDevices181142 -Node: ExCreate181780 -Node: ExDialog183054 -Node: ExGrowing184316 -Node: ExModifying185118 -Node: ExBootable185619 -Node: ExCharset186168 -Node: ExPseudo186996 -Node: ExCdrecord187894 -Node: ExMkisofs188209 -Node: ExGrowisofs189547 -Node: ExException190682 -Node: ExTime191136 -Node: ExIncBackup191595 -Node: ExRestore195519 -Node: ExRecovery196488 -Node: Files197054 -Node: Seealso198352 -Node: Bugreport198940 -Node: Legal199521 -Node: CommandIdx200451 -Node: ConceptIdx215192 +Node: Media6148 +Node: Methods8814 +Node: Drives11363 +Node: Extras14671 +Node: Processing18136 +Node: Dialog21606 +Node: Options23269 +Node: AqDrive24877 +Node: Loading27914 +Node: Insert42181 +Node: SetInsert51886 +Node: Manip60454 +Node: CmdFind69181 +Node: Filter80443 +Node: Writing84781 +Node: SetWrite92010 +Node: Bootable106056 +Node: Jigdo119274 +Node: Charset123520 +Node: Exception126279 +Node: DialogCtl132392 +Node: Inquiry134979 +Node: Navigate139307 +Node: Verify147218 +Node: Restore155756 +Node: Emulation162416 +Node: Scripting172219 +Node: Frontend178347 +Node: Examples179646 +Node: ExDevices180817 +Node: ExCreate181455 +Node: ExDialog182729 +Node: ExGrowing183991 +Node: ExModifying184793 +Node: ExBootable185294 +Node: ExCharset185843 +Node: ExPseudo186663 +Node: ExCdrecord187561 +Node: ExMkisofs187876 +Node: ExGrowisofs189214 +Node: ExException190349 +Node: ExTime190803 +Node: ExIncBackup191262 +Node: ExRestore195186 +Node: ExRecovery196144 +Node: Files196712 +Node: Seealso198010 +Node: Bugreport198598 +Node: Legal199179 +Node: CommandIdx200109 +Node: ConceptIdx214850  End Tag Table diff --git a/xorriso/xorriso.texi b/xorriso/xorriso.texi index cb6952a1..ed743044 100644 --- a/xorriso/xorriso.texi +++ b/xorriso/xorriso.texi @@ -242,13 +242,13 @@ one and the modifications. See paragraph Creating, Growing, Modifying, Blind Growing below. @c man .PP @sp 1 -@command{xorriso} adopts the concept of multi-session by loading an eventual -image directory tree, allowing to manipulate it by several actions, and to -write the new image to the target media. +@command{xorriso} adopts the concept of multi-session by loading an +image directory tree if present, +by allowing to manipulate it by several actions, +and by writing the new image to the target media. @c man .br The first session of a @command{xorriso} run begins by the definition of -the input -drive with the eventual ISO image or by the definition of an output drive. +the input drive with the ISO image or by the definition of an output drive. The session ends by command -commit which triggers writing. A -commit is done automatically when the program ends regularly. @c man .PP @@ -305,7 +305,7 @@ With used CD-RW and DVD-RW it can be achieved by action -blank "as_needed". Overwriteable media are considered blank if they are new or if they have been marked as blank by @command{xorriso}. Action -blank "as_needed" can be used to do this marking on overwriteable -media, or to apply eventual mandatory formatting to new media. +media, or to apply mandatory formatting to new media if necessary. @* @sp 1 @cindex Appendable media, _definition @@ -354,7 +354,7 @@ They have quite different capabilities and constraints. @sp 1 @cindex Growing, _definition The method of @strong{growing} adds new data to the existing media. These -data comprise of eventual new file content and they override the existing +data comprise of new file content and they override the existing ISO 9660 + Rock Ridge directory tree. It is possible to hide files from previous sessions but they still exist on media and with many types of optical media it is quite easy to recover them by mounting older sessions. @@ -551,7 +551,7 @@ It uses this extension if enabled by option @strong{-acl}. @* AAIP enhanced images are supposed to be mountable normally, but one cannot -expect that the mounted filesystem will show and respect the eventual ACLs. +expect that the mounted filesystem will show and respect the ACLs. For now, only @command{xorriso} is able to retrieve those ACLs. It can bring them into effect when files get restored to an ACL enabled file system or it can @@ -559,8 +559,8 @@ print them in a format suitable for tool setfacl. @* Files with ACL show as group permissions the setting of entry "mask::" if that entry exists. Nevertheless the non-listed group members get handled -according to entry "group::". @command{xorriso} brings "group::" into effect -before eventually removing the ACL from a file. +according to entry "group::". When removing ACL from a file, +@command{xorriso} brings "group::" into effect. @c man .PP @sp 1 @cindex xattr, _definiton @@ -610,14 +610,14 @@ appears among the arguments of such a command. @cindex Pattern expansion, _definition @strong{Pattern expansion} converts a list of pattern words into a list of existing file addresses. -Eventual unmatched pattern words appear themselves in that result list, though. +Unmatched pattern words appear themselves in that result list, though. @* Pattern matching supports the usual shell parser wildcards '*' '?' '[xyz]' and respects '/' as separator which may only be matched literally. @* It is a property of some particular commands and not a general feature. It gets controlled by commands -iso_rr_pattern and -disk_pattern. -Commands which eventually use pattern expansion all have variable argument +Commands which may use pattern expansion all have variable argument lists which are marked in this man page by "[***]" rather than "[...]". @* Some other commands perform pattern matching unconditionally. @@ -652,10 +652,10 @@ as in $'...' of bash. It is not enabled by default. See option -backslash_codes. @c man .PP @sp 1 -When the program begins then it first looks for argument -no_rc. If this is +When the program starts then it first looks for argument -no_rc. If this is not present then it looks for its startup files and -eventually reads their content as command input lines. Then it interprets -the program arguments as commands and parameters and finally it enters +reads their content as command input lines. Then it interprets +the program arguments as commands and parameters. Finally it enters dialog mode if command -dialog "on" was executed up to then. @c man .PP @sp 1 @@ -748,20 +748,24 @@ inner dashes are interpreted as underscores. @section Aquiring source and target drive @c man .B Aquiring source and target drive: @c man .PP -Before aquiring a drive one will eventually enable options which influence -the behavior of image loading. See next option group. +The effect of aquiring a drive may depend on several options in the +next paragraph "Influencing the behavior of image loading". +If desired, their enabling commands have to be performed before the +commands which aquire the drive. @table @asis @sp 1 @c man .TP @item -dev address @kindex -dev aquires one drive for input and output @cindex Drive, for input and output, -dev -Set input and output drive to the same address and load an eventual ISO image. +Set input and output drive to the same address and load an ISO image if it +is present. If there is no ISO image then create a blank one. Set the image expansion method to growing. @* This is only allowed as long as no changes are pending in the currently -loaded ISO image. Eventually one has to perform -commit or -rollback first. +loaded ISO image. If changes are pending, then one has to perform -commit +or -rollback first. @* Special address string "-" means standard output, to which several restrictions apply. See above paragraph "Libburn drives". @@ -772,7 +776,8 @@ without aquiring a new one. @item -indev address @kindex -indev aquires a drive for input @cindex Drive, for input, -indev -Set input drive and load an eventual ISO image. If the new input drive differs +Set input drive and load an ISO image if present. +If the new input drive differs from -outdev then switch from growing to modifying or to blind growing. It depends on the setting of -grow_blindly which of both gets activated. The same rules and restrictions apply as with -dev. @@ -856,11 +861,11 @@ will be reset to "auto". @item -displacement [-]lba @kindex -displacement compensate altered image start address @cindex Session, altered start address, -displacement -Compensate an eventual displacement of the image versus the start address +Compensate a displacement of the image versus the start address for which the image was prepared. This affects only loading of ISO images and reading of their files. The multi-session method of growing is not allowed as long as -displacement is non-zero. I.e. -indev and -outdev must be -different. Eventually the displacement is reset to 0 before the drive +different. The displacement gets reset to 0 before the drive gets re-aquired after writing. @* Examples: @@ -897,7 +902,7 @@ If a drive path matches no list then it is considered "harmless". By default these are all paths which do not begin with directory "/dev". @* A path matches a list if one of its parent paths or itself matches a list -entry. An eventual address prefix "stdio:" or "mmc:" will be ignored when +entry. Address prefix "stdio:" or "mmc:" will be ignored when testing for matches. @* By pseudo-class "clear_list" and pseudo-patterns "banned", "caution", @@ -927,8 +932,7 @@ input media and does not discard an already loaded image. @kindex -in_charset sets input character set @cindex Character Set, for input, -in_charset Set the character set from which to convert file names when loading an -image. This has eventually to be done before specifying -dev , -indev or --rollback. See paragraph "Character sets" for more explanations. +image. See paragraph "Character sets" for more explanations. When loading the written image after -commit the setting of -out_charset will be copied to -in_charset. @c man .TP @@ -936,9 +940,9 @@ will be copied to -in_charset. @kindex -auto_charset learns character set from image @cindex Character set, learn from image, -auto_charset Enable or disable recording and interpretation of the output character -set name in an xattr attribute of the image root directory. If enabled then -an eventual recorded character set name gets used as input character set -when reading an image. +set name in an xattr attribute of the image root directory. If enabled and +if a recorded character set name is found, then this name will be used as +namoe of the input character set when reading an image. @* Note that the default output charset is the local character set of the terminal where @command{xorriso} runs. Before attributing this local @@ -955,7 +959,8 @@ In default mode "off", iso_rr files lose their inode numbers at image load time. Each iso_rr file object which has no inode number at image generation time will get a new unique inode number if -compliance is set to new_rr. @* -Mode "on" preserves eventual inode numbers from the loaded image. +Mode "on" preserves inode numbers from the loaded image if such numbers +were recorded. When committing a session it searches for families of iso_rr files which stem from the same disk file, have identical content filtering and have identical properties. The family members all get the same inode number. @@ -1005,12 +1010,12 @@ See also options -getfattr, -setfattr and above paragraph about xattr. @kindex -md5 controls handling of MD5 sums @cindex MD5, control handling, -md5 Enable or disable processing of MD5 checksums for the overall session and for -each single data file. If enabled then images get loaded only if eventual -checksums tags of superblock and directory tree match properly. The MD5 +each single data file. If enabled then images with checksum tags get loaded +only if the tags of superblock and directory tree match properly. The MD5 checksums of data files and whole session get loaded from the image if there are any. @* -With options -compare and -update the eventually recorded MD5 of a file +With options -compare and -update the recorded MD5 of a file will be used to avoid content reading from the image. Only the disk file content will be read and compared with that MD5. This can save much time if -disk_dev_ino "on" is not suitable. @@ -1047,7 +1052,7 @@ Currently this is a shortcut for: -hardlinks on -acl on -xattr on -md5 on. @kindex -disk_dev_ino fast incremental backup @cindex Backup, enable fast incremental, -disk_dev_ino Enable or disable processing of recorded file identification numbers -(dev_t and ino_t). They are eventually stored as xattr and allow +(dev_t and ino_t). If enabled they are stored as xattr and allow to substantially accelerate file comparison. The root node gets a global start timestamp. If during comparison a file with younger timestamps is found in the ISO image, then it is suspected to have inconsistent content. @@ -1074,7 +1079,7 @@ too. Read-only drives do not tell the actual media type but show any media as ROM (e.g. as DVD-ROM). The session history of MMC multi-session media might be truncated to first and last session or even be completely false. -(The eventual emulated history of overwriteable media is not affected by this.) +(The emulated history of overwriteable media is not affected by this.) @* To have in case of failure a chance of getting the session history and especially the address of the last session, there is a scan for ISO 9660 @@ -1163,8 +1168,9 @@ If other file types collide then the setting of command decides. @* Renaming of files has similar collision handling, but directories can only -be replaced, not merged. Note that -mv inserts the source objects into an -eventual existing target directory rather than attempting to replace it. +be replaced, not merged. Note that if the target directory exists, then -mv +inserts the source objects into this directory rather than attempting +to replace it. @c man .PP @sp 1 The commands in this section alter the ISO image and not the local filesystem. @@ -1194,7 +1200,7 @@ Insert the given files or directory trees from filesystem into the ISO image. @* If -pathspecs is set to "on" then pattern expansion is always disabled and -character '=' has a special meaning. It eventually separates the ISO image path +character '=' has a special meaning. It separates the ISO image path from the disk path: @* iso_rr_path=disk_path @@ -1207,9 +1213,10 @@ If no '=' is given then the word is used as both, iso_rr_path and disk path. If in this case the word does not begin with '/' then -cdx is prepended to the disk_path and -cd is prepended to the iso_rr_path. @* -If -pathspecs is set to "off" then eventual -disk_pattern expansion applies. -The resulting words are used as both, iso_rr_path and disk path. Eventually --cdx gets prepended to disk_path and -cd to iso_rr_path. +If -pathspecs is set to "off" then -disk_pattern expansion applies, if enabled. +The resulting words are used as both, iso_rr_path and disk path. Relative +path words get prepended the setting of -cdx to disk_path and the setting +of -cd to iso_rr_path. @c man .TP @item -add_plainly mode @kindex -add_plainly inserts one or more paths @@ -1217,7 +1224,7 @@ The resulting words are used as both, iso_rr_path and disk path. Eventually If set to mode "unknown" then any command word that does not begin with "-" and is not recognized as known command will be subject to a virtual -add command. I.e. it will be used as pathspec or as disk_path and added to the image. -Eventually -disk_pattern expansion applies to disk_paths. +If enabled, -disk_pattern expansion applies to disk_paths. @* Mode "dashed" is similar to "unknown" but also adds unrecognized command words even if they begin with "-". @@ -1360,8 +1367,8 @@ other file causes a FAILURE event. @cindex Directory, copy, -clone Create a copy of the ISO file object iso_rr_path_original with the new address iso_rr_path_copy. If the original is a directory then copy all -files and directories underneath. An eventual boot catalog file gets -not copied but is silently ignored. +files and directories underneath. If iso_rr_path_original is a boot catalog +file, then it gets not copied but is silently ignored. @* The copied ISO file objects have the same attributes. Copied data files refer to the same content source as their originals. @@ -1374,7 +1381,7 @@ already exists in the ISO tree. @kindex -cp_clone copies ISO directory tree @cindex Directories, copy, -cp_clone Create copies of one or more ISO file objects as with command -clone. -Eventually merge directories with existing ones, but do not overwrite +In case of collision merge directories with existing ones, but do not overwrite existing ISO file objects. @* The rules for generating the copy addresses are the same as with @@ -1405,8 +1412,8 @@ up to 2g -1 @minus{}@minus{}. Newer ones are good up to 4g -1 @minus{}@minus{}. You need quite a new Linux kernel to read correctly the final bytes of a file >= 4g if its size is not aligned to 2048 byte blocks. @* -@command{xorriso}'s own data read capabilities are not affected by eventual -operating system size limits. They apply to mounting only. Nevertheless, +@command{xorriso}'s own data read capabilities are not affected by +operating system size limits. Such limits apply to mounting only. Nevertheless, the target filesystem of an -extract must be able to take the file size. @c man .TP @item -not_mgt code[:code[...]] @@ -1457,7 +1464,7 @@ get reported with -compare and deleted from the image with -update. @cindex Insert, file exclusion absolute, -not_paths Add the given paths to the list of excluded absolute disk paths. If a given path is relative, then the current -cdx is prepended to form an absolute path. -Eventual pattern matching happens at definition time and not when exclusion +Pattern matching, if enabled, happens at definition time and not when exclusion checks are made. @* (Do not forget to end the list of disk_paths by "@minus{}@minus{}") @@ -1552,7 +1559,7 @@ like with program mkisofs -graft-points. It also disables -disk_pattern expansion for command -add. @* "off" disables pathspecs of the form target=source -and eventually enables -disk_pattern expansion. +and re-enables -disk_pattern expansion. @c man .TP @item -overwrite "on"|"nondir"|"off" @kindex -overwrite enables overwriting in ISO @@ -1718,8 +1725,8 @@ Like -chmod but affecting all files below eventual directories. @item -setfacl acl_text iso_rr_path [***] @kindex -setfacl sets ACL in ISO image @cindex ACL, set in ISO image, -setfacl -Attach the given ACL to the given iso_rr_paths after deleting their eventually -existing ACLs. +Attach the given ACL to the given iso_rr_paths. If the files already have +ACLs, then those get deleted before the new ones get into effect. If acl_text is empty, or contains the text "clear" or the text "@minus{}@minus{}remove-all", then the existing ACLs will be removed and no new ones will be @@ -1857,7 +1864,7 @@ Like -alter_date but affecting all files below eventual directories. @cindex hidden, set in ISO image, -hide Prevent the names of the given files from showing up in the directory trees of ISO 9660 and/or Joliet when the image gets written. -The eventual data content of such hidden files will be included in the +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. @* @@ -1911,7 +1918,7 @@ Can be true only for data files which stem not from the loaded image. @item -type type_letter : Matches files of the given type: "block", "char", "dir", "pipe", "file", "link", "socket", "eltorito", -"Xotic" which eventually matches what is not matched by the other types. +and "Xotic" which matches what is not matched by the other types. @* Only the first letter is interpreted. E.g.: -find / -type d @* @@ -1997,10 +2004,10 @@ Normal precedence is: -not, -or , -and. @c man \fB\-if\fR ... \fB\-then\fR\ ... \fB\-elseif\fR ... \fB\-then\fR ... @c man \fB\-else\fR ... \fB\-endif\fR : @c man-ignore-lines 1 -@item -if ... -then\ ... -elseif ... -then ... -else ... -endif : +@item -if ... -then ... -elseif ... -then ... -else ... -endif : Enclose one or more sub expressions. If the -if expression matches, then the -then expression is evaluated as the result of the whole expression -up to -endif. Else the next -elseif expression is evaluated and eventually +up to -endif. Else the next -elseif expression is evaluated and if it matches, its -then expression. Finally in case of no match, the -else expression is evaluated. There may be more than one -elseif. Neither -else nor -elseif are mandatory. @@ -2088,7 +2095,7 @@ removes an eventual marking from action "update_merge". @* @item report_damage classifies files whether they hit a data block that is -marked as damaged. The result is printed together with the eventual address +marked as damaged. The result is printed together with the address of the first damaged byte, the maximum span of damages, file size, and the path of the file. @* @@ -2103,25 +2110,25 @@ different extent number in column "xt". prints access permissions in ACL text form to the result channel. @* @item setfacl -attaches ACLs after removing eventually exiting ones. The new +attaches ACLs after removing existing ones. The new ACL is given in text form as defined with option -setfacl. @* E.g.: -exec setfacl u:lisa:rw,u::rw,g::r,o::@minus{},m::rw @minus{}@minus{} @* @item getfattr -prints eventual xattr name-value pairs from user namespace +prints xattr name-value pairs from user namespace to the result channel. @* @item get_any_xattr -prints eventual xattr name-value pairs from any namespace +prints xattr name-value pairs from any namespace except ACL to the result channel. This is mostly for debugging of namespace "isofs". @* @item get_md5 -prints eventual recorded MD5 sum together with file path. +prints the MD5 sum, if recorded, together with file path. @* @item check_md5 -compares eventual recorded MD5 sum with the file content +compares the MD5 sum, if recorded, with the file content and reports if mismatch. @* E.g.: -find / -not -pending_data -exec check_md5 FAILURE @minus{}@minus{} @@ -2228,7 +2235,7 @@ Options are: "suffix=..." sets a file name suffix. If it is not empty then it will be appended to the file name or removed from it. @* - "remove_suffix" will remove an eventual file name suffix + "remove_suffix" will remove a file name suffix rather than appending it. @* "if_nonempty" will leave 0-sized files unfiltered. @@ -2292,7 +2299,7 @@ with files from the loaded ISO image if the write method of growing is in effect (i.e -indev and -outdev are identical). @* The reserved filter name "@minus{}@minus{}remove-all-filters" revokes -filtering. This will revoke eventual suffix renamings as well. +filtering. This will revoke suffix renamings as well. Use "@minus{}@minus{}remove-all-filters+" to prevent any suffix renaming. @c man .TP @@ -2319,8 +2326,8 @@ Discard the manipulated ISO image and reload it from -indev. @item -commit @kindex -commit writes pending ISO image @cindex Write, pending ISO image, -commit -Perform the write operation. Afterwards eventually make the --outdev the new -dev and load the image from there. +Perform the write operation. Afterwards, if -outdev is readable, make it +the new -dev and load the image from there. Switch to growing mode. (A subsequent -outdev will activate modification mode or blind growing.) -commit is performed automatically at end of program if there @@ -2358,7 +2365,7 @@ Note: It is not possible yet to effectively eject disk files. @cindex Drive, write and eject, -commit_eject Combined -commit and -eject. When writing has finished do not make -outdev the new -dev, and load no ISO image. Rather eject --indev and/or -outdev. Eventually give up any non-ejected drive. +-indev and/or -outdev. Give up any non-ejected drive. @c man .TP @item -blank mode @kindex -blank erases media @@ -2871,7 +2878,7 @@ because they appear to inadverted readers as one single session. But with multi-session media CD-R[W], DVD-R[W], DVD+R, it implies that the whole bootable system has to reside already in the first session and that the last session still has to bear all files which the booted system expects -after eventually mounting the ISO image. +after mounting the ISO image. @* If a boot image from ISOLINUX or GRUB is known to be present on media then it is advised to patch it @@ -2898,7 +2905,7 @@ and announced by an MBR partition table entry. "discard"|"keep"|"patch"|"show_status"|bootspec|"next" @* @sp 1 -Define the handling of an eventual set of El Torito boot images which +Define the handling of a set of El Torito boot images which has been read from an existing ISO image or define how to make a prepared boot image file set bootable. Such file sets get produced by ISOLINUX or GRUB. @* @@ -2939,8 +2946,8 @@ and their designated fate. @* @sp 1 -A @strong{bootspec} is a word of the form name=value and is used to describe -the parameters of a boot image by an El Torito record and eventually a MBR. +A @strong{bootspec} is a word of the form name=valuei. It is used to describe +the parameters of a boot image by an El Torito record or a MBR. The names "dir", "bin_path", "efi_path" lead to El Torito bootable images. Name "system_area" activates a given file as MBR. @* @@ -3008,8 +3015,7 @@ They get attributed to the boot image entry in the catalog. @* @strong{next} ends the definition of a boot image and starts a new one. Any following -bootimage bootspecs will affect the new image. -The first "next" discards eventually loaded boot images and their -catalog. +The first "next" discards loaded boot images and their catalog. @* @strong{discard} gives up an existing boot catalog and its boot images. @* @@ -3051,7 +3057,7 @@ and sizes as if it had been processed by "partition_table=on". If so, then those parameters get updated when the new System Area is written. @* Special "system_area=/dev/zero" causes 32k of NUL-bytes. -Use this to discard an MBR which eventually was loaded with the ISO image. +Use this to discard an MBR which was loaded with the ISO image. @* @cindex Partition offset, _definiton @strong{partition_offset=}2kb_block_adr causes a partition table with a single @@ -3095,15 +3101,13 @@ Mode "off" disables alignment for any type. MIPS Big Endian boot file and causes 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 eventually provided by -system_area=. +It will overwrite the first 512 bytes of any data provided by system_area=. Up to 15 boot files can be declared by mips_path=. @* @strong{mipsel_path=}iso_rr_path declares 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 eventually -provided by system_area=. +It will overwrite the first 512 bytes of any data provided by system_area=. Only a single boot file can be declared by mipsel_path=. @* @cindex SUN Disk Label, production @@ -3111,8 +3115,7 @@ Only a single boot file can be declared by mipsel_path=. given text as ASCII label. This boot block format allows to append images for partitions 2 to 8. Partition 1 will always be the ISO image. See option -append_partition. -The first 512 bytes of any data eventually provided -by system_area= will be overwritten. +The first 512 bytes of any data provided by system_area= will be overwritten. @* @strong{mips_discard} and @strong{sparc_discard} revoke any boot file declarations made by mips_path= or mipsel_path=. They also disable production @@ -3190,14 +3193,14 @@ 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 file address is decisive for To=From mapping, not for file recognition. -After eventual To=From mapping, the file address gets written into the .jigdo +After To=From mapping, the file address gets written into the .jigdo 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 @command{xorriso} will refuse to write to non-blank targets, it will disable multi-session emulation, and -eventual padding will be counted as part of the ISO image. +padding will be counted as part of the ISO image. @* @table @asis @sp 1 @@ -3440,11 +3443,11 @@ signals (e.g. from program "kill" or from keys Ctrl+C) or on signals caused by severe program errors. @* Mode "on" is the default. It uses the signal handler of libburn which produces -ugly messages but puts much effort in releasing eventually used optical drives +ugly messages but puts much effort in releasing optical drives before @command{xorriso} ends. @* Mode "off" as first -signal_handling among the start arguments prevents all -own signal precautions of @command{xorriso}. Eventually inherited signal +own signal precautions of @command{xorriso}. Inherited signal handler settings stay as they are. @* It works like "sig_dfl" if given after other signal handling was already @@ -3582,7 +3585,7 @@ their libburn standard device files. @* This is only possible when no ISO image changes are pending. After this option was executed, there is no drive current -and no image loaded. Eventually one has to aquire a drive again. +and no image loaded. @* In order to be visible, a device has to offer rw-permissions with its libburn standard device file. Thus it might be only the @@ -3608,7 +3611,7 @@ with only one or two sessions on it. The last of these sessions is supposed to be the most recent real session then. @* Some read-only drives and media show no usable session history at all. -Eventually option -rom_toc_scan might help. +Option -rom_toc_scan might help. @c man .TP @item -mount_cmd drive entity id path @kindex -mount_cmd composes mount command line @@ -3918,9 +3921,10 @@ composed from disk_path by replacing disk_prefix by iso_rr_prefix. @cindex Filter, show chain, -show_stream Display the content stream chain of data files in the ISO image. The chain consists of the iso_rr_name and one or more streams, separated by " < " marks. -A stream consists of one or more texts eventually in ''-quotation marks, -eventually separated by ":" characters. The first text describes the stream -type, the following ones describe its individual properties. +A stream description consists of one or more texts, separated by ":" +characters. +The first text tells the stream type, the following ones, if ever, describe its +individual properties. Frequently used types are: @* disk:'disk_path' for local filesystem objects. @@ -3966,7 +3970,7 @@ They work independently of the media type and can detect transmission errors. @kindex -check_media reads media block by block @cindex Verify, check blocks, -check_media @cindex Recovery, retrieve blocks, -check_media -Try to read data blocks from the indev drive, eventually copy them to a +Try to read data blocks from the indev drive, optionally copy them to a disk file, and finally report about the encountered quality. Several options may be used to modify the default behavior. @* @@ -3984,14 +3988,14 @@ allowed to be unreadable (e.g. gaps between tracks). Alternatively it is possible to report damaged files rather than blocks. @* If -md5 is "on" then the default mode what=tracks looks out for libisofs -checksum tags for the ISO session data and eventually checks them +checksum tags for the ISO session data and checks them against the checksums computed from the data stream. @c man .TP @item -check_media_defaults [option [option ...]] @minus{}@minus{} @kindex -check_media_defaults sets -check_media options @cindex Verify, preset -check_media, -check_media_defaults Preset options for runs of -check_media, -extract_cut and best_effort -file extraction. Eventual options given with -check_media will override the +file extraction. Options given with -check_media will override the preset options. -extract_cut will override some options automatically. @* An option consists of a keyword, a "=" character, and a value. Options @@ -4076,13 +4080,13 @@ recorded MD5 checksums. Severity "ALL" disables this event. tries to read the file given by disk_path as sector bitmap and to store such a map file after the scan run. The bitmap tells which blocks have been read successfully in previous runs. -It allows to do several scans on the same media, eventually with intermediate +It allows to do several scans on the same media, even with intermediate eject, in order to collect readable blocks whenever the drive is lucky enough to produce them. The stored file contains a human readable TOC of tracks and their start block addresses, followed by binary bitmap data. @* @item map_with_volid="on" -examines tracks whether they are ISO images and eventually +examines tracks whether they are ISO images and prints their volume ids into the human readable TOC of sector_map=. @* @item patch_lba0="on" @@ -4339,7 +4343,7 @@ of mkisofs emulation in the context of a @command{xorriso} run. @* Other than with the "cdrecord" personality there is no automatic -commit at the end of a "mkisofs" option list. Verbosity settings -v (= "UPDATE") and --quiet (= "SORRY") persist. The output file, eventually chosen with -o, +-quiet (= "SORRY") persist. The output file persists until things happen like -commit, -rollback, -dev, or end of @command{xorriso}. -pacifier gets set to "mkisofs" if files are added to the image. @@ -4364,7 +4368,7 @@ standard output. -print-size inhibits automatic image production at program end. This ban is lifted only if the pending image changes get discarded. @* -Eventual padding is counted as part of the ISO image if not option --emul-toc +Padding is counted as part of the ISO image if not option --emul-toc is given. @* If no -iso-level is given, then level 1 is chosen when the first file or @@ -4467,7 +4471,7 @@ The scope is only a single data track per session to be written to blank, overwriteable, or appendable media. The media gets closed if closing is applicable and not option -multi is present. @* -An eventually acquired input drive is given up. +If an input drive was aquired, then it is given up. This is only allowed if no image changes are pending. @* dev= must be given as @command{xorriso} device address. Addresses like 0,0,0 @@ -4490,7 +4494,7 @@ are aliases for "cdrecord". If @command{xorriso} is started with one of the leafnames "xorrecord", "cdrskin", "cdrecord", or "wodim", then it automatically prepends -as "cdrskin" to the command line arguments. I.e. all arguments will be interpreted cdrecord -style until "@minus{}@minus{}" is encountered and an eventual commit happens. +style until "@minus{}@minus{}" is encountered. From then on, options are interpreted as @command{xorriso} options. @* @minus{}@minus{}no_rc as first argument of such a program start @@ -4556,8 +4560,7 @@ Program scdbackup_verify will recognize and verify tag resp. record. @cindex Process, disable startup files, -no_rc @* Only if used as first command line argument this option -prevents reading and interpretation of eventual startup -files. See section FILES below. +prevents reading and interpretation of startup files. See section FILES below. @c man .TP @item -options_from_file fileaddress @kindex -options_from_file reads commands from file @@ -4740,7 +4743,7 @@ Only "-scsi_log" with dash "-" is recognized that way. @cindex Process, end program and write, -end @cindex Program, end and write, -end @* -End program after writing eventually pending changes. +End program after writing pending changes. @c man .TP @item -rollback_end @kindex -rollback_end ends program without writing @@ -4753,7 +4756,7 @@ Discard pending changes. End program immediately. @cindex Comment, # Only in dialog or file execution mode, and only as first non-whitespace in line: -Do not execute the line but eventually store it in history. +Do not execute the line but store it in readline history. @end table @c man .TP @c man .B Support for frontend programs via stdin and stdout: @@ -5092,7 +5095,7 @@ set ISO-8859-1 but that the readers expected UTF-8. Now a new session with the same files gets added with converted file names. In order to avoid any weaknesses of the local character set, this command pretends that it uses already the final target set UTF-8. -Therefore strange file names may appear in eventual messages which +Therefore strange file names may appear in messages, which will be made terminal-safe by option -backslash_codes. @* @sp 1 @@ -5425,7 +5428,7 @@ $ xorriso -outdev /dev/sr0 -toc @sp 1 Then load the desired session and copy the file trees to disk. Enable restoring of ACL, xattr and hard links. -Avoid to eventually create /home/thomas/restored without rwx-permission. +Avoid to create /home/thomas/restored without rwx-permission. @* @sp 1 $ xorriso -for_backup \ @@ -5462,7 +5465,7 @@ $ xorriso -abort_on NEVER -indev /dev/sr0 \ data_to="$HOME"/dvd_copy sector_map="$HOME"/dvd_copy.map @minus{}@minus{} @* @sp 1 -This can be repeated several times, eventually with -eject or with other +This can be repeated several times, if necessary with -eject or with other -indev drives. See the human readable part of "$HOME"/dvd_copy.map for addresses which can be used on "$HOME"/dvd_copy with mount option -o sbsector= resp. -s. diff --git a/xorriso/xorriso_eng.html b/xorriso/xorriso_eng.html index 75a00ec7..50b0a25e 100644 --- a/xorriso/xorriso_eng.html +++ b/xorriso/xorriso_eng.html @@ -78,13 +78,13 @@ but rather not with CD, DVD-R, DVD+R, BD-R.

Optional supporting software:

libreadline and libreadline-dev
-
eventually make dialog more convenient.
+
make dialog more convenient.
libacl and libacl-devel
-
eventually allow on GNU/Linux to get and set ACLs.
+
allow on GNU/Linux to get and set ACLs.
zlib and zlib-devel
-
eventually allow zisofs, gzip compression, and Jigdo file production.
+
allow zisofs, gzip compression, and Jigdo file production.
libbz2 and libbz2-devel
-
eventually allow bzip2 compression of Jigdo template files.
+
allow bzip2 compression of Jigdo template files.

@@ -185,7 +185,7 @@ may accept pathspecs of form target=source as known from program mkisofs.
$ xorriso -indev /dev/sr0 -du / -- -toc 2>&1 | less
Make re-usable media writable again, delete any ISO 9660 image, -eventually prepare yet unused BD-RE:
+prepare yet unused BD-RE:
$ xorriso -outdev /dev/sr0 -blank as_needed -eject all
@@ -261,7 +261,7 @@ Important: -indev and -outdev have to be different drives. arguments have to be given in one single line. Backslash may be used to mark a line as incomplete so it gets continued by the next input line.
-Command -end stops the program run. It will write eventually pending changes +Command -end stops the program run. It will write pending changes to media, if that has not already been done by a previous -commit.
$ xorriso -dialog on
enter option and arguments :
@@ -455,7 +455,7 @@ This can bring effective read performance near to the raw media reading speed. (detached GPG signature for verification by gpg --verify xorriso-1.0.8.tar.gz.sig xorriso-1.0.8.tar.gz
-after eventual gpg --keyserver keys.gnupg.net --recv-keys ABC0A854). +after gpg --keyserver keys.gnupg.net --recv-keys ABC0A854).
Also on @@ -585,6 +585,9 @@ xorriso command -add_plainly "any" did not add all files to the image
  • The attempt to blank already blanked DVD-RW was not gracefully blocked
    • +
  • +-as mkisofs -isohybrid-mbr without -no-pad was not cylinder aligned +
    • @@ -593,6 +596,7 @@ The attempt to blank already blanked DVD-RW was not gracefully blocked
    Enhancements towards stable version 1.0.8:
    • New option -signal_handling
      • +
    • New option -close_damaged
      • diff --git a/xorriso/xorriso_timestamp.h b/xorriso/xorriso_timestamp.h index 268384f8..b044d88e 100644 --- a/xorriso/xorriso_timestamp.h +++ b/xorriso/xorriso_timestamp.h @@ -1 +1 @@ -#define Xorriso_timestamP "2011.06.07.144548" +#define Xorriso_timestamP "2011.06.17.143813" diff --git a/xorriso/xorrisofs.1 b/xorriso/xorrisofs.1 index 31b4b0a1..636c3abd 100644 --- a/xorriso/xorrisofs.1 +++ b/xorriso/xorrisofs.1 @@ -270,7 +270,8 @@ The default for \-root is "/". 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 will eventually get adjusted. +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. @@ -301,7 +302,7 @@ device number after each reboot, then this comparison will see all files as changed and thus prevent any incremental size saving. .TP \fB--old-root-no-md5\fR -Disable recording and eventual use of MD5 checksums for data file content. +Disable recording and use of MD5 checksums for data file content. If neither checksums and nor disk inode numbers are recorded, then option \-old\-root will have to read ISO image file content when comparing it with disk file content. @@ -512,7 +513,7 @@ restore them when extracting files from the ISO image. .br 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 eventually raise alert on mismatch. +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: .br @@ -558,7 +559,7 @@ excluded from the Joliet tree. \fB\-hide\fR disk_path_pattern Make files invisible in the directory tree of ISO 9660 and Rock Ridge, if their disk_path matches the given shell parser pattern. -The eventual data content of such hidden files will be included in the +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. .br @@ -733,7 +734,7 @@ that points to an EFI image. Consider to use \-\-efi\-boot rather than \-e. .TP \fB--efi-boot\fR iso_rr_path -Perform eventual necessary \-eltorito\-alt\-boot, option \-e with the given +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. .TP @@ -880,15 +881,14 @@ 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 mutually exclusive with production of other boot blocks like MBR. -It will overwrite the first 512 bytes of any data eventually provided by \-G. +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. .TP \fB\-mipsel-boot\fR 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 eventually -provided by \-G. +It will overwrite the first 512 bytes of any data provided by \-G. Only a single boot file can be declared by \-mipsel\-boot. .TP \fB\-B\fR disk_path[,disk_path ...] @@ -968,11 +968,11 @@ 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 file address is decisive for To=From mapping, not for file recognition. -After eventual To=From mapping, the file address gets written into the .jigdo +After To=From mapping, the file address gets written into the .jigdo file. Jigdo restore tools will convert these addresses into really reachable data source addresses from which they can read. .br -If the list of jigdo parameters is not empty, then eventual padding will be +If the list of jigdo parameters is not empty, then padding will be counted as part of the ISO image. .br .TP @@ -1042,8 +1042,7 @@ add 150 (= 300 KiB) to the resulting number. .TP \fB--no_rc\fR Only if used as first argument this option -prevents reading and interpretation of eventual startup -files. See section FILES below. +prevents reading and interpretation of startup files. See section FILES below. .TP \fB\-help\fR .br @@ -1408,7 +1407,7 @@ 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. .br CAUTION: -This will overwrite any eventual partitioning on the USB stick and make +This will overwrite any partitioning on the USB stick and make remaining data unaccessible. .br So first make sure you got the correct address of the intended device. diff --git a/xorriso/xorrisofs.info b/xorriso/xorrisofs.info index 6b2b9b66..7fc30144 100644 --- a/xorriso/xorrisofs.info +++ b/xorriso/xorrisofs.info @@ -289,10 +289,10 @@ File: xorrisofs.info, Node: SetInsert, Next: SetProduct, Prev: Loading, Up: 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 - will eventually get adjusted. 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. + 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 @@ -320,10 +320,10 @@ File: xorrisofs.info, Node: SetInsert, Next: SetProduct, Prev: Loading, Up: size saving. --old-root-no-md5 - Disable recording and eventual use of MD5 checksums for data file - content. If neither checksums and nor disk inode numbers are - recorded, then option -old-root will have to read ISO image file - content when comparing it with disk file content. + Disable recording and use of MD5 checksums for data file content. + If neither checksums and nor disk inode numbers are recorded, then + option -old-root will have to read ISO image file content when + comparing it with disk file content.  File: xorrisofs.info, Node: SetProduct, Next: SetCompl, Prev: SetInsert, Up: Options @@ -524,8 +524,8 @@ File: xorrisofs.info, Node: SetExtras, Next: SetHide, Prev: SetCompl, Up: Op --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 eventually raise alert - on mismatch. See man xorriso, options -check_media, check_md5_r. + 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 @@ -571,8 +571,8 @@ File: xorrisofs.info, Node: SetHide, Next: ImageId, Prev: SetExtras, Up: Opt -hide disk_path_pattern Make files invisible in the directory tree of ISO 9660 and Rock Ridge, if their disk_path matches the given shell parser pattern. - The eventual data content of such hidden files will be included in - the resulting image, even if they do not show up in any directory. + 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. This command does not apply to the boot catalog. @@ -736,9 +736,9 @@ Sytem Area. --efi-boot rather than -e. --efi-boot iso_rr_path - Perform eventual necessary -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. + 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. -boot-load-size number Set the number of 512-byte blocks for boot images which emulate a @@ -882,15 +882,14 @@ not combinable and also not combinable with MBR. 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 mutually exclusive with production of other boot blocks like MBR. - It will overwrite the first 512 bytes of any data eventually - provided by -G. Up to 15 boot files can be declared by multiple - -mips-boot options. + 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 eventually provided by - -G. Only a single boot file can be declared by -mipsel-boot. + 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 @@ -965,11 +964,11 @@ 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 file address is decisive for To=From mapping, not for file recognition. -After eventual To=From mapping, the file address gets written into the -.jigdo 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 eventual padding -will be counted as part of the ISO image. +After To=From mapping, the file address gets written into the .jigdo +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. -jigdo-jigdo disk_path Set the disk_path for the .jigdo file with the checksums and @@ -1042,7 +1041,7 @@ File: xorrisofs.info, Node: Miscellaneous, Next: ExSimple, Prev: Jigdo, Up: --no_rc Only if used as first argument this option prevents reading and - interpretation of eventual startup files. See section FILES below. + interpretation of startup files. See section FILES below. -help List supported options to stderr. Original mkisofs options bear @@ -1363,8 +1362,8 @@ $ xorrisofs -o output.iso \ 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 eventual partitioning on the USB stick -and make remaining data unaccessible. +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: @@ -1526,7 +1525,7 @@ File: xorrisofs.info, Node: CommandIdx, Next: ConceptIdx, Prev: Legal, Up: T (line 86) * -appid set Application Id: ImageId. (line 46) * -b El Torito PC-BIOS boot image: Bootable. (line 32) -* -B SUN SPARC boot images: SystemArea. (line 117) +* -B SUN SPARC boot images: SystemArea. (line 116) * -biblio set Biblio File path: ImageId. (line 72) * -boot-info-table Patch El Torito boot image: Bootable. (line 80) * -boot-load-size El Torito boot image load size: Bootable. (line 63) @@ -1592,7 +1591,7 @@ File: xorrisofs.info, Node: CommandIdx, Next: ConceptIdx, Prev: Legal, Up: T (line 64) * -md5-list set path of readable .md5: Jigdo. (line 73) * -mips-boot MIPS Big Endian boot image: SystemArea. (line 103) -* -mipsel-boot MIPS Little Endian boot image: SystemArea. (line 111) +* -mipsel-boot MIPS Little Endian boot image: SystemArea. (line 110) * -N omit version number in ISO file names: SetCompl. (line 67) * -no-emul-boot El Torito boot image emulation: Bootable. (line 72) * -no-pad do not add zeros to ISO tree: SetProduct. (line 76) @@ -1629,8 +1628,8 @@ File: xorrisofs.info, Node: CommandIdx, Next: ConceptIdx, Prev: Legal, Up: T (line 21) * -rock Rock Ridge (is always enabled): SetExtras. (line 12) * -root redirect ISO root directory: SetInsert. (line 64) -* -sparc-boot SUN SPARC boot images: SystemArea. (line 129) -* -sparc-label SUN Disk Label text: SystemArea. (line 132) +* -sparc-boot SUN SPARC boot images: SystemArea. (line 128) +* -sparc-label SUN Disk Label text: SystemArea. (line 131) * -sysid set System Id: ImageId. (line 49) * -transparent-compression enable recognition of zisofs files: SetInsert. (line 61) @@ -1674,10 +1673,10 @@ File: xorrisofs.info, Node: ConceptIdx, Prev: CommandIdx, Up: Top (line 80) * Bootability, control, --efi-boot: Bootable. (line 58) * Bootability, control, -b, -eltorito-boot: Bootable. (line 32) -* Bootability, control, -B, -sparc-boot: SystemArea. (line 117) +* Bootability, control, -B, -sparc-boot: SystemArea. (line 116) * Bootability, control, -e: Bootable. (line 50) * Bootability, control, -mips-boot: SystemArea. (line 103) -* Bootability, control, -mipsel-boot: SystemArea. (line 111) +* Bootability, control, -mipsel-boot: SystemArea. (line 110) * Bootability, fill System Area e.g. by MBR, -G, --embedded-boot, -generic-boot: SystemArea. (line 17) * Bootability, install ISOLINUX isohybrid MBR, -isohybrid-mbr: SystemArea. @@ -1687,7 +1686,7 @@ File: xorrisofs.info, Node: ConceptIdx, Prev: CommandIdx, Up: Top (line 72) * Bootability, patch System Area partition table, --protective-msdos-label: SystemArea. (line 41) -* Bootability, SUN Disk Label text, -sparc-label: SystemArea. (line 132) +* Bootability, SUN Disk Label text, -sparc-label: SystemArea. (line 131) * Bugs, reporting: Bugreport. (line 6) * Character Set, for disk file names, -input-charset: Charset. (line 17) @@ -1808,29 +1807,29 @@ Node: Xorriso4990 Node: Options6129 Node: Loading6846 Node: SetInsert9140 -Node: SetProduct13542 -Node: SetCompl17249 -Node: SetExtras19568 -Node: SetHide22442 -Node: ImageId23450 -Node: Bootable26954 -Node: SystemArea31038 -Node: Charset37400 -Node: Jigdo38425 -Node: Miscellaneous42710 -Node: Examples43883 -Node: ExSimple44369 -Node: ExGraft44848 -Node: ExMkisofs46095 -Node: ExGrowisofs47346 -Node: ExIncBackup48518 -Node: ExIncBckAcc51567 -Node: ExBootable53242 -Node: Files55343 -Node: Seealso56417 -Node: Bugreport56936 -Node: Legal57517 -Node: CommandIdx58325 -Node: ConceptIdx69658 +Node: SetProduct13556 +Node: SetCompl17263 +Node: SetExtras19582 +Node: SetHide22445 +Node: ImageId23444 +Node: Bootable26948 +Node: SystemArea31013 +Node: Charset37347 +Node: Jigdo38372 +Node: Miscellaneous42639 +Node: Examples43803 +Node: ExSimple44289 +Node: ExGraft44768 +Node: ExMkisofs46015 +Node: ExGrowisofs47266 +Node: ExIncBackup48438 +Node: ExIncBckAcc51487 +Node: ExBootable53162 +Node: Files55254 +Node: Seealso56328 +Node: Bugreport56847 +Node: Legal57428 +Node: CommandIdx58236 +Node: ConceptIdx69569  End Tag Table diff --git a/xorriso/xorrisofs.texi b/xorriso/xorrisofs.texi index 1393b4f4..d419b932 100644 --- a/xorriso/xorrisofs.texi +++ b/xorriso/xorrisofs.texi @@ -430,7 +430,8 @@ The default for -root is "/". 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 will eventually get adjusted. +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. @@ -467,7 +468,7 @@ files as changed and thus prevent any incremental size saving. @item @minus{}@minus{}old-root-no-md5 @kindex @minus{}@minus{}old-root-no-md5 disable MD5 with -old-root @cindex Incremental insertion, disable MD5, @minus{}@minus{}old-root-no-md5 -Disable recording and eventual use of MD5 checksums for data file content. +Disable recording and use of MD5 checksums for data file content. If neither checksums and nor disk inode numbers are recorded, then option -old-root will have to read ISO image file content when comparing it with disk file content. @@ -751,7 +752,7 @@ restore them when extracting files from the ISO image. @* 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 eventually raise alert on mismatch. +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: @* @@ -813,7 +814,7 @@ excluded from the Joliet tree. @cindex Hiding, from ISO and Rock Ridge, -hide Make files invisible in the directory tree of ISO 9660 and Rock Ridge, if their disk_path matches the given shell parser pattern. -The eventual data content of such hidden files will be included in the +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. @* @@ -1040,7 +1041,7 @@ Consider to use @minus{}@minus{}efi-boot rather than -e. @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 eventual necessary -eltorito-alt-boot, option -e with the given +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. @c man .TP @@ -1227,7 +1228,7 @@ 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 mutually exclusive with production of other boot blocks like MBR. -It will overwrite the first 512 bytes of any data eventually provided by -G. +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. @c man .TP @item -mipsel-boot iso_rr_path @@ -1236,8 +1237,7 @@ Up to 15 boot files can be declared by multiple -mips-boot options. 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 eventually -provided by -G. +It will overwrite the first 512 bytes of any data provided by -G. Only a single boot file can be declared by -mipsel-boot. @c man .TP @item -B disk_path[,disk_path ...] @@ -1339,11 +1339,11 @@ 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 file address is decisive for To=From mapping, not for file recognition. -After eventual To=From mapping, the file address gets written into the .jigdo +After To=From mapping, the file address gets written into the .jigdo 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 eventual padding will be +If the list of jigdo parameters is not empty, then padding will be counted as part of the ISO image. @* @table @asis @@ -1444,8 +1444,7 @@ add 150 (= 300 KiB) to the resulting number. @kindex @minus{}@minus{}no_rc do not execute startup files @cindex Startup files, suppress, @minus{}@minus{}no_rc Only if used as first argument this option -prevents reading and interpretation of eventual startup -files. See section FILES below. +prevents reading and interpretation of startup files. See section FILES below. @c man .TP @item -help @kindex -help list supported options @@ -1898,7 +1897,7 @@ 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 eventual partitioning on the USB stick and make +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.