Defined the term LBA in man xorriso

master
Thomas Schmitt 9 years ago
parent 93b2c7e513
commit 524f64509d
  1. 10
      xorriso/xorriso.1
  2. 111
      xorriso/xorriso.info
  3. 12
      xorriso/xorriso.texi

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

@ -258,14 +258,17 @@ File: xorriso.info, Node: Drives, Next: Extras, Prev: Methods, Up: Top
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.
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.
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.
All drive file objects have to offer rw-permission to the user of
All drive file objects have to offer rw-permission to the user of
`xorriso'. Even those which will not be useable for reading an ISO
image.
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
(*LBA*) which gives the number of a particular data block.
MMC compliant (i.e. optical) drives on GNU/Linux usually get
addressed by the path of their block device or of their generic
@ -5373,54 +5376,54 @@ Node: Model3405
Node: Media6311
Node: Methods8982
Node: Drives11557
Node: Extras14872
Node: Processing19324
Node: Dialog22944
Node: Commands24622
Node: ArgSort26299
Node: AqDrive27791
Node: Loading30836
Node: Insert47765
Node: SetInsert57964
Node: Manip66541
Node: CmdFind76321
Node: Filter91363
Node: Writing95919
Node: SetWrite106050
Node: Bootable126375
Node: Jigdo142765
Node: Charset147012
Node: Exception149774
Node: DialogCtl155894
Node: Inquiry158492
Node: Navigate164809
Node: Verify173107
Node: Restore182139
Node: Emulation189226
Node: Scripting199528
Node: Frontend207299
Node: Examples216906
Node: ExDevices218084
Node: ExCreate218743
Node: ExDialog220028
Node: ExGrowing221293
Node: ExModifying222098
Node: ExBootable222602
Node: ExCharset223154
Node: ExPseudo224046
Node: ExCdrecord224944
Node: ExMkisofs225261
Node: ExGrowisofs226601
Node: ExException227736
Node: ExTime228190
Node: ExIncBackup228649
Node: ExRestore232629
Node: ExRecovery233562
Node: Files234132
Node: Seealso235431
Node: Bugreport236154
Node: Legal236735
Node: CommandIdx237746
Node: ConceptIdx254408
Node: Extras15072
Node: Processing19524
Node: Dialog23144
Node: Commands24822
Node: ArgSort26499
Node: AqDrive27991
Node: Loading31036
Node: Insert47965
Node: SetInsert58164
Node: Manip66741
Node: CmdFind76521
Node: Filter91563
Node: Writing96119
Node: SetWrite106250
Node: Bootable126575
Node: Jigdo142965
Node: Charset147212
Node: Exception149974
Node: DialogCtl156094
Node: Inquiry158692
Node: Navigate165009
Node: Verify173307
Node: Restore182339
Node: Emulation189426
Node: Scripting199728
Node: Frontend207499
Node: Examples217106
Node: ExDevices218284
Node: ExCreate218943
Node: ExDialog220228
Node: ExGrowing221493
Node: ExModifying222298
Node: ExBootable222802
Node: ExCharset223354
Node: ExPseudo224246
Node: ExCdrecord225144
Node: ExMkisofs225461
Node: ExGrowisofs226801
Node: ExException227936
Node: ExTime228390
Node: ExIncBackup228849
Node: ExRestore232829
Node: ExRecovery233762
Node: Files234332
Node: Seealso235631
Node: Bugreport236354
Node: Legal236935
Node: CommandIdx237946
Node: ConceptIdx254608

End Tag Table

@ -50,7 +50,7 @@
@c man .\" First parameter, NAME, should be all caps
@c man .\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
@c man .\" other parameters are allowed: see man(7), man(1)
@c man .TH XORRISO 1 "Version 1.3.3, Nov 27, 2013"
@c man .TH XORRISO 1 "Version 1.3.3, Dec 01, 2013"
@c man .\" Please adjust this date whenever revising the manpage.
@c man .\"
@c man .\" Some roff macros, for reference:
@ -409,15 +409,19 @@ 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.
@c man .PP
@sp 1
@*
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.
@*
@c man .PP
@sp 1
All drive file objects have to offer rw-permission to the user of
@command{xorriso}.
Even those which will not be useable for reading an ISO image.
@*
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
(@strong{LBA}) which gives the number of a particular data block.
@c man .PP
@sp 1
MMC compliant (i.e. optical) drives on GNU/Linux usually get addressed by

Loading…
Cancel
Save