Small correction in API introduction text

master
Thomas Schmitt 15 years ago
parent 25fd92f2c4
commit b45fd0553e

@ -77,21 +77,22 @@ fulfill, or else will refuse to start the write run.
Setup for Growing, Modifying or Blind Growing
The connector function family offers two alternative API calls for performing
The connector function family offers alternative API calls for performing
the setup for several alternative image generation strategies.
Growing:
If input and output drive is the same, then isoburn_prepare_disc() is to
If input and output drive are the same, then isoburn_prepare_disc() is to
be used. It will lead to an add-on session on appendable or overwriteable
media with existing ISO image. With blank media it will produce a first
session.
Modifying:
If the output drive is not the input drive, then it has to bear blank media
or overwriteable without a valid ISO image. To prepare for such an image
generation run, use isoburn_prepare_new_image(). The run will copy file data
from an eventual input drive with valid image, add any newly introduced data
from the local filesystem, and produce a first session on output media.
If the output drive is not the input drive, and if it bears blank media
or overwriteable without a valid ISO image, then one may produce a consolidated
image with old and new data. This will copy file data from an eventual input
drive with valid image, add any newly introduced data from the local
filesystem, and produce a first session on output media.
To prepare for such an image generation run, use isoburn_prepare_new_image().
Blind Growing:
This method reads the old image from one drive and writes the add-on session
@ -101,7 +102,8 @@ will be stdio:/dev/fd/1 (i.e. stdout) being piped into some burn program
like with this classic gesture:
mkisofs -M $dev -C $msc1,$nwa | cdrecord -waiti dev=$dev
Blind growing is prepared by the call isoburn_prepare_blind_grow().
The input drive should be released immediately after this call.
The input drive should be released immediately after this call in order
to allow the consumer of the output stream to access that drive for writing.
After either of these setups, some peripheral libburn drive parameter settings
like burn_write_opts_set_simulate(), burn_write_opts_set_multi(),

@ -1 +1 @@
#define Xorriso_timestamP "2008.07.10.141731"
#define Xorriso_timestamP "2008.07.10.141913"

Loading…
Cancel
Save