More hunt for "allow to"

This commit is contained in:
2015-09-01 06:59:24 +00:00
parent 7651adf8e2
commit 9992ddf00c
17 changed files with 80 additions and 80 deletions

View File

@ -128,10 +128,10 @@ the archivers afio and star. Not suitable seems GNU tar.
.br
In general there are two approaches for writing media:
.br
A permissive mode depicted by option
A permissive mode selected by option
.B -tao
which needs no predicted track size and is able to make use of
eventual multi-session capabilities.
which needs no predicted track size and can use
multi-session capabilities if offered by drive and medium.
.br
A more restrictive mode
.B -sao
@ -156,7 +156,7 @@ read-only. Closing is done automatically unless option
is given which keeps the media appendable.
.br
Write mode
-tao s able to use track sources of unpredictable length (like stdin) and
-tao is able to use track sources of unpredictable length (like stdin) and
to write further sessions to appendable media.
-sao produces audio sessions with seamless tracks but needs predicted track
sizes and cannot append sessions to media.

View File

@ -39,8 +39,8 @@ About any CD, DVD, or BD recorder produced in the recent ten years.
<BR>
<A HREF="http://libburnia-project.org">libburn</A>
supports recorders which are compliant to standards MMC-1 for CD and
MMC-5 for DVD or BD. Linux, FreeBSD, Solaris, and NetBSD allow to access drives
connected via SCSI, PATA (aka IDE, ATA), USB, or SATA.
MMC-5 for DVD or BD. Linux, FreeBSD, Solaris, and NetBSD can communicate
with drives connected via SCSI, PATA (aka IDE, ATA), USB, or SATA.
<BR>
</P>
@ -474,7 +474,7 @@ cdrecord but not vice versa.
<BR>
<BR>
I was a long time user of cdrecord and it worked fine for me.
Especially i do appreciate its write mode -tao which allows to pipe arbitrary
Especially i do appreciate its write mode -tao which can pipe arbitrary
data on CD and CD-RW via stdin. cdrecord is reliable, versatile and well
maintained. So for me - there would be no problem with using it for
burning CDs.

View File

@ -1 +1 @@
#define Cdrskin_timestamP "2015.08.30.185714"
#define Cdrskin_timestamP "2015.09.01.065852"

View File

@ -23,11 +23,6 @@ About libburn API for burning CD, DVD, and BD: http://api.libburnia-project.org
--------------------------------------------------------------------------
For yet unsupported media types see the advice to use dvd+rw-tools at
the end of this text.
--------------------------------------------------------------------------
About the command line options of cdrskin:
They are described in detail in [http://scdbackup.sourceforge.net/man_1_cdrskin_devel.html#OPTIONS section OPTIONS] of
@ -61,7 +56,7 @@ Some are of general user interest, though:
--------------------------------------------------------------------------
--devices allows the sysadmin to scan the system for possible drives
--devices can be used by the sysadmin to scan the system for possible drives
and displays their detected properties.
The drives are listed one per line, with fields:
libburn-drive-number, sysadmin-device-file, permissions, vendor, type
@ -172,7 +167,7 @@ media with a single session and track on it. blank= invalidates ISO images.
--------------------------------------------------------------------------
assert_write_lba=<lba> allows to ensure that the start block address which
assert_write_lba=<lba> ensures that the start block address which
was used with the formatter program (e.g. mkisofs -C) matches the start block
address which will be used by the upcoming burn.
@ -220,7 +215,7 @@ With a very fat fs=# buffer (128 MB for 12x CD is not unrealistic) this
can cause a big delay until burning finally starts and takes its due time.
fifo_start_at=<num> makes cdrskin start burning after the given number of bytes
is read rather than waiting for the FIFO to be completely full resp. the data
is read rather than waiting for the FIFO to be completely full or the data
stream to end. It risks a few drive buffer underruns at the beginning of burn
- but modern drives stand this.