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

Defined the term LBA in man xorriso

Browse Source
This commit is contained in:
Thomas Schmitt
2013-12-01 08:30:54 +00:00
parent 36b7a1b110
commit 064fde8b1f
3 changed files with 72 additions and 61 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
libisoburn/trunk/xorriso/xorriso.1
View File

@ -9,7 +9,7 @@
.\" First parameter, NAME, should be all caps
.\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
.\" other parameters are allowed: see man(7), man(1)
.TH XORRISO 1 "Version 1.3.3, Nov 27, 2013"
.TH XORRISO 1 "Version 1.3.3, Dec 01, 2013"
.\" Please adjust this date whenever revising the manpage.
.\"
.\" Some roff macros, for reference:
@ -282,14 +282,18 @@ and the burn program is desired. \-C $msc1,$msc2 is equivalent to:
Input drive, i.e. source of an existing or empty ISO image, can be any random
access readable libburn drive: optical media with readable data,
blank optical media, regular files, block devices.
.PP
.br
Output drive, i.e. target for writing, can be any libburn drive.
Some drive types do not support the method of growing but only the methods
of modifying and blind growing. They all are suitable for newly created images.
.br
.PP
All drive file objects have to offer rw\-permission to the user of
\fBxorriso\fR.
Even those which will not be useable for reading an ISO image.
.br
With any type of drive object, the data are considered to be organized in
blocks of 2 KiB. Access happens in terms of Logical Block Address
(\fBLBA\fR) which gives the number of a particular data block.
.PP
MMC compliant (i.e. optical) drives on GNU/Linux usually get addressed by
the path of their block device or of their generic character device. E.g.