Made number transition to 0.4.7

This commit is contained in:
2008-05-10 13:40:55 +00:00
parent 692864c1fe
commit f3a901a887
12 changed files with 138 additions and 107 deletions

View File

@ -4,7 +4,7 @@
cdrskin. By Thomas Schmitt <scdbackup@gmx.net>
Integrated sub project of libburnia-project.org but also published via:
http://scdbackup.sourceforge.net/cdrskin_eng.html
http://scdbackup.sourceforge.net/cdrskin-0.4.5.tar.gz
http://scdbackup.sourceforge.net/cdrskin-0.4.7.tar.gz
Copyright (C) 2006-2008 Thomas Schmitt, provided under GPL version 2.
------------------------------------------------------------------------------
@ -20,10 +20,10 @@ By using this software you agree to the disclaimer at the end of this text
Compilation, First Glimpse, Installation
Obtain cdrskin-0.4.5.tar.gz, take it to a directory of your choice and do:
Obtain cdrskin-0.4.7.tar.gz, take it to a directory of your choice and do:
tar xzf cdrskin-0.4.5.tar.gz
cd cdrskin-0.4.5
tar xzf cdrskin-0.4.7.tar.gz
cd cdrskin-0.4.7
Within that directory execute:
@ -53,9 +53,9 @@ try whether command
ldconfig
makes it accessible. With the statically linked binary this should not matter.
You may as well do the few necessary actions manually. If cdrskin was
already installed by a previous version, or by "make install" in the course
of this installation, then find out where:
With that static binary you may as well do the few necessary actions manually.
If cdrskin was already installed by a previous version, or by "make install"
in the course of this installation, then find out where:
which cdrskin
Copy your standalone binary to exactly the address which you get as reply.
E.g.:
@ -262,17 +262,27 @@ I myself am not into audio. So libburn-hackers@pykix.org might be the
best address for suggestions, requests and bug reports.
DVD+RW and DVD-RAM
DVD+RW , DVD-RAM , BD-RE
DVD+RW and DVD-RAM media get treated as blank media regardless wether they
These random access media get treated as blank media regardless wether they
hold data or not. Options -audio and -multi are not allowed. Only one track
is allowed. -toc does not return information about the media content.
Speed is counted in DVD units (i.e. 1x = 1,385,000 bytes/second). Currently
there is no difference between -sao and -tao. If ever, then -tao will be the
mode which preserves the current behavior.
Speed is counted in DVD units (i.e. 1x = 1,385,000 bytes/second) or BD units
(1x = 4,495,625 bytes/second). Currently there is no difference between -sao
and -tao. If ever, then -tao will be the mode which preserves the current
behavior.
BD-RE media need formatting before first use. cdrskin option "blank=as_needed"
recognizes unformatted BD-RE and applies a lengthy formatting run.
During write operations DVD-RAM and BD-RE automatically apply defect
management. This usually slows them down to half nominal speed. If drive
and media produce flawless results anyway, then one can try to reach full
nominal speed by option "stream_recording=on".
In this case bad blocks are not detected during write and not even previously
known bad blocks are avoided. So you have to make your own readability tests
and go back to half speed as soon as the first read errors show up.
Program growisofs can append to an ISO filesystem on DVD+RW by additionally
manipulating the first session. Meanwhile cdrskin can do the same.
Option --grow_overwriteable_iso allows -multi (although unneeded), enables
-msinfo and -toc, and makes blank=fast an invalidator for ISO filesystems
on overwriteable media.
@ -341,11 +351,11 @@ Incremental Streaming afterwards. So blank=fast will do full blanking.
blank=deformat_sequential_quickest is faster but might yield DAO-only media.
DVD+R and DVD+R/DL
DVD+R and DVD+R DL
From the view of cdrskin they behave much like DVD-R. Each track gets wrapped
into an own session, though.
DVD+R/DL appear as extra large DVD+R. cdrskin does not allow to set the address
DVD+R DL appear as extra large DVD+R. cdrskin does not allow to set the address
of the layer break where ia reading drive might show some delay while switching
between both media layers.
@ -399,7 +409,7 @@ are the cause. Any mistake of the burn program is supposed to be caught
by the drive's firmware and to lead to mere misburns.
The worst mishaps which hit the author implied the need to reboot the
system because of drives gnawing endlessly on ill media. Permanent hardware
damage did not occur in 1.5 years of development.
damage did not occur in 2.5 years of development.
------------------------------------------------------------------------------