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

Corrected statement about sort weight of files which are loaded from ISO image

This commit is contained in:
Thomas Schmitt 2013-05-24 11:17:51 +00:00
parent b454ffeef7
commit db040c6e42
3 changed files with 57 additions and 42 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
xorriso/xorriso.1
View File

@ -1985,7 +1985,12 @@ The number may range from \-2147483648 to 2147483647. The higher it is, the
lower will be the block address of the file data in the emerging ISO image. lower will be the block address of the file data in the emerging ISO image.
Currently the boot catalog has a hardcoded weight of 1 billion. Currently the boot catalog has a hardcoded weight of 1 billion.
Normally it should occupy the block with the lowest possible address. Normally it should occupy the block with the lowest possible address.
Data files get added or loaded with initial weight 0. .br
Data files which are loaded by \-indev or \-dev get a weight between 1 and
2 exp 28 = 268,435,456, depending on their block address. This shall keep
them roughly in the same order if the write method of modifying is applied.
.br
Data files which are added by other commands get an initial weight of 0.
.br .br
E.g.: \-exec sort_weight 3 \-\- E.g.: \-exec sort_weight 3 \-\-
.br .br

85
xorriso/xorriso.info
View File

@ -1766,8 +1766,13 @@ File: xorriso.info, Node: CmdFind, Next: Filter, Prev: Manip, Up: Commands
higher it is, the lower will be the block address of the file higher it is, the lower will be the block address of the file
data in the emerging ISO image. Currently the boot catalog data in the emerging ISO image. Currently the boot catalog
has a hardcoded weight of 1 billion. Normally it should has a hardcoded weight of 1 billion. Normally it should
occupy the block with the lowest possible address. Data occupy the block with the lowest possible address.
files get added or loaded with initial weight 0. Data files which are loaded by -indev or -dev get a weight
between 1 and 2 exp 28 = 268,435,456, depending on their
block address. This shall keep them roughly in the same order
if the write method of modifying is applied.
Data files which are added by other commands get an initial
weight of 0.
E.g.: -exec sort_weight 3 -- E.g.: -exec sort_weight 3 --
show_stream show_stream
shows the content stream chain of a data file. shows the content stream chain of a data file.
@ -5250,43 +5255,43 @@ Node: Insert46505
Node: SetInsert56704 Node: SetInsert56704
Node: Manip65281 Node: Manip65281
Node: CmdFind74790 Node: CmdFind74790
Node: Filter89495 Node: Filter89786
Node: Writing94051 Node: Writing94342
Node: SetWrite103439 Node: SetWrite103730
Node: Bootable122190 Node: Bootable122481
Node: Jigdo138580 Node: Jigdo138871
Node: Charset142827 Node: Charset143118
Node: Exception145589 Node: Exception145880
Node: DialogCtl151709 Node: DialogCtl152000
Node: Inquiry154307 Node: Inquiry154598
Node: Navigate160624 Node: Navigate160915
Node: Verify168922 Node: Verify169213
Node: Restore177954 Node: Restore178245
Node: Emulation185041 Node: Emulation185332
Node: Scripting195165 Node: Scripting195456
Node: Frontend202326 Node: Frontend202617
Node: Examples210401 Node: Examples210692
Node: ExDevices211579 Node: ExDevices211870
Node: ExCreate212238 Node: ExCreate212529
Node: ExDialog213523 Node: ExDialog213814
Node: ExGrowing214788 Node: ExGrowing215079
Node: ExModifying215593 Node: ExModifying215884
Node: ExBootable216097 Node: ExBootable216388
Node: ExCharset216649 Node: ExCharset216940
Node: ExPseudo217470 Node: ExPseudo217761
Node: ExCdrecord218368 Node: ExCdrecord218659
Node: ExMkisofs218685 Node: ExMkisofs218976
Node: ExGrowisofs220025 Node: ExGrowisofs220316
Node: ExException221160 Node: ExException221451
Node: ExTime221614 Node: ExTime221905
Node: ExIncBackup222073 Node: ExIncBackup222364
Node: ExRestore226053 Node: ExRestore226344
Node: ExRecovery226986 Node: ExRecovery227277
Node: Files227556 Node: Files227847
Node: Seealso228855 Node: Seealso229146
Node: Bugreport229578 Node: Bugreport229869
Node: Legal230159 Node: Legal230450
Node: CommandIdx231170 Node: CommandIdx231461
Node: ConceptIdx247472 Node: ConceptIdx247763
 
End Tag Table End Tag Table

7
xorriso/xorriso.texi
View File

@ -2381,7 +2381,12 @@ The number may range from -2147483648 to 2147483647. The higher it is, the
lower will be the block address of the file data in the emerging ISO image. lower will be the block address of the file data in the emerging ISO image.
Currently the boot catalog has a hardcoded weight of 1 billion. Currently the boot catalog has a hardcoded weight of 1 billion.
Normally it should occupy the block with the lowest possible address. Normally it should occupy the block with the lowest possible address.
Data files get added or loaded with initial weight 0. @*
Data files which are loaded by -indev or -dev get a weight between 1 and
2 exp 28 = 268,435,456, depending on their block address. This shall keep
them roughly in the same order if the write method of modifying is applied.
@*
Data files which are added by other commands get an initial weight of 0.
@* @*
E.g.: -exec sort_weight 3 @minus{}@minus{} E.g.: -exec sort_weight 3 @minus{}@minus{}
@* @*