libburnia/libisoburn
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Switched to usage of libjte-2.0.0. New -jigdo parameters "checksum_algorithm", "demand_checksum", "checksum_path". New -as mkisofs options-jigdo-checksum-algorithm, "-checksum-list", "-jigdo-force-checksum".

Browse Source
This commit is contained in:
Thomas Schmitt
2019-11-24 13:34:30 +01:00
parent c4894d8ae3
commit 1557304c96
12 changed files with 326 additions and 182 deletions
Download Patch File Download Diff File Expand all files Collapse all files

126
xorriso/xorriso.info
View File

@@ -3184,18 +3184,22 @@ symbolic file addresses. The .template file contains the compressed ISO
image with reference tags instead of the content bytes of the listed
files.
Input for this process are the normal arguments for a 'xorriso' session
on a blank -outdev, and a .md5 file which lists those data files which
may be listed in the .jigdo file and externally referenced in the
.template file. Each designated file is represented in the .md5 file by
a single text line:
MD5 as 32 hex digits, 2 blanks, size as 12 decimal digits or blanks, 2
on a blank -outdev, and a checksum file which lists those data files
which may be listed in the .jigdo file and externally referenced in the
.template file. Each designated file is represented in the checksum
file by a single text line:
Checksum as hex digits, 2 blanks, size as 12 decimal digits or blanks, 2
blanks, symbolic file address
The file address in an .md5 line has to bear the same basename as the
disk_path of the file which it shall match. The directory path of the
file address is decisive for To=From mapping, not for file recognition.
After To=From mapping, the file address gets written into the .jigdo
file. Jigdo restore tools will convert these addresses into really
reachable data source addresses from which they can read.
The kind of checksum is chosen by -jigdo "checksum_algorithm" with
values "md5" (32 hex digits) or "sha256" (64 hex digits). It will also
be used for the file address lines in the .jigdo file. The default is
"md5".
The file address in a checksum file 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 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 padding will be counted as part of the ISO image.
@@ -3207,6 +3211,11 @@ and padding will be counted as part of the ISO image.
they are recognized by the -as mkisofs emulation command.
Parameter *clear* with any value empties the whole list. No .jigdo
and .template file will be produced.
*checksum_algorithm* chooses the checksum algorithm which shall be
used for the data file entries in the .jigdo file and is expected
in the checksum file. Permissible are "md5" or "sha256". Default
is "md5".
Alias: -jigdo-checksum-algorithm
*template_path* sets the disk_path for the .template file with the
holed and compressed ISO image copy.
Alias: -jigdo-template
@@ -3214,7 +3223,11 @@ and padding will be counted as part of the ISO image.
checksums and download addresses for filling the holes in
.template.
Alias: -jigdo-jigdo
*md5_path* sets the disk_path where to find the .md5 input file.
*checksum_path* sets the disk_path where to find the checksum file
with symbolic file addresses and checksums according to
*checksum_algorithm*.
Alias: md5_path
Alias: -checksum-list
Alias: -md5-list
*min_size* sets the minimum size for a data file to be listed in
the .jigdo file and being a hole in the .template file.
@@ -3223,17 +3236,20 @@ and padding will be counted as part of the ISO image.
with the absolute disk_path of any data file. A match causes the
file to stay in .template in any case.
Alias: -jigdo-exclude
*demand_md5* adds a regular expression pattern which will get
*demand_checksum* adds a regular expression pattern which will get
compared with the absolute disk_path of any data file that was not
found in the .md5 list. A match causes a MISHAP event.
found in the checksum list file as of "checksum_path". A match
causes a MISHAP event.
Alias: demand_md5
Alias: -jigdo-force-checksum
Alias: -jigdo-force-md5
*mapping* adds a string pair of the form To=From to the parameter
list. If a data file gets listed in the .jigdo file, then it is
referred by the file address from its line in the .md5 file. This
file address gets checked whether it begins with the From string.
If so, then this string will be replaced by the To string and a ':'
character, before it goes into the .jigdo file. The From string
should end by a '/' character.
referred by the file address from its line in the checksum file.
This file address gets checked whether it begins with the From
string. If so, then this string will be replaced by the To string
and a ':' character, before it goes into the .jigdo file. The From
string should end by a '/' character.
Alias: -jigdo-map
*compression* chooses one of "bzip2" or "gzip" for the compression
of the template file. The jigdo file is put out uncompressed.
@@ -5408,7 +5424,7 @@ File: xorriso.info, Node: CommandIdx, Next: ConceptIdx, Prev: Legal, Up: Top
* -iso_nowtime fixed "now" time for ISO 9660 objects: Loading.
(line 217)
* -iso_rr_pattern controls pattern expansion: Manip. (line 10)
* -jigdo clears JTE or or adds parameter to JTE: Jigdo. (line 33)
* -jigdo clears JTE or or adds parameter to JTE: Jigdo. (line 37)
* -joliet enables production of Joliet tree: SetWrite. (line 10)
* -launch_frontend starts frontend program at pipes: Frontend.
(line 141)
@@ -5703,7 +5719,7 @@ File: xorriso.info, Node: ConceptIdx, Prev: CommandIdx, Up: Top
* Interval reader for system area and partitions: Bootable. (line 32)
* ISO 9660, _definition: Model. (line 6)
* iso_rr_path, _definition: Insert. (line 7)
* Jigdo Template Extraction, -jigdo: Jigdo. (line 33)
* Jigdo Template Extraction, -jigdo: Jigdo. (line 37)
* Jigdo Template Extraction, _definition: Jigdo. (line 6)
* LBA, _definition: Drives. (line 17)
* libisofs, fixed "now" time: Loading. (line 217)
@@ -5884,39 +5900,39 @@ Node: Writing110455
Node: SetWrite120602
Node: Bootable145360
Node: Jigdo172315
Node: Charset176574
Node: Exception179903
Node: DialogCtl186032
Node: Inquiry188634
Node: Navigate197516
Node: Verify205973
Node: Restore216444
Node: Emulation225121
Node: Scripting235577
Node: Frontend243360
Node: Examples252986
Node: ExDevices254164
Node: ExCreate254825
Node: ExDialog256125
Node: ExGrowing257396
Node: ExModifying258205
Node: ExBootable258715
Node: ExCharset259270
Node: ExPseudo260166
Node: ExCdrecord261093
Node: ExMkisofs261413
Node: ExGrowisofs263310
Node: ExException264463
Node: ExTime264921
Node: ExIncBackup265379
Node: ExRestore269405
Node: ExRecovery270351
Node: Files270923
Node: Environ272257
Node: Seealso273005
Node: Bugreport273722
Node: Legal274313
Node: CommandIdx275325
Node: ConceptIdx292868
Node: Charset177318
Node: Exception180647
Node: DialogCtl186776
Node: Inquiry189378
Node: Navigate198260
Node: Verify206717
Node: Restore217188
Node: Emulation225865
Node: Scripting236321
Node: Frontend244104
Node: Examples253730
Node: ExDevices254908
Node: ExCreate255569
Node: ExDialog256869
Node: ExGrowing258140
Node: ExModifying258949
Node: ExBootable259459
Node: ExCharset260014
Node: ExPseudo260910
Node: ExCdrecord261837
Node: ExMkisofs262157
Node: ExGrowisofs264054
Node: ExException265207
Node: ExTime265665
Node: ExIncBackup266123
Node: ExRestore270149
Node: ExRecovery271095
Node: Files271667
Node: Environ273001
Node: Seealso273749
Node: Bugreport274466
Node: Legal275057
Node: CommandIdx276069
Node: ConceptIdx293612

End Tag Table