Avoided the use of the term 'eventual' for the meaning 'if applicable'.
This commit is contained in:
@ -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.
|
||||
|
Reference in New Issue
Block a user