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

Avoided the use of the term 'eventual' for the meaning 'if applicable'.

Browse Source
This commit is contained in:
Thomas Schmitt
2011-06-17 14:39:24 +00:00
parent dfccac8ba7
commit 75a626d4d4
14 changed files with 627 additions and 621 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
libisoburn/trunk/xorriso/README_gnu_xorriso
View File

@ -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=.