Mentioning BD-R in documentation

README

@@ -4,44 +4,56 @@
 This all is under GPL.
 (See GPL reference, our clarification and commitment at the end of this text)
 ------------------------------------------------------------------------------
-libburnia-project.org
+libburn-project.org
 By Mario Danic <mario.danic@gmail.com> and Thomas Schmitt <scdbackup@gmx.net>
 Copyright (C) 2006-2008 Mario Danic, Thomas Schmitt
-
-Still containing parts of
-Libburn. By Derek Foreman <derek@signalmarketing.com> and
-            Ben Jansens <xor@orodu.net>
+Still containing parts of Libburn. By Derek Foreman <derek@signalmarketing.com>
+and Ben Jansens <xor@orodu.net>
 Copyright (C) 2002-2006  Derek Foreman and Ben Jansens
 
-This libburnia-project.org toplevel README (C) 2006-2008 Thomas Schmitt 
+     http://files.libburnia-project.org/releases/libburn-0.5.8.pl00.tar.gz
+
 ------------------------------------------------------------------------------
 
                            Build and Installation
 
-Our build system is based on autotools. For preparing the build of a SVN 
-snapshot you will need autotools of at least version 1.7. 
-Check out from SVN by
-   svn co http://svn.libburnia-project.org/libburn/trunk libburn
-go into directory libburn and apply autotools by
-   ./bootstrap
+                                From tarball
 
-Alternatively you may unpack a release tarball for which you do not need
-autotools installed.
+Obtain libburn-0.5.8.pl00.tar.gz, take it to a directory of your choice and do:
 
-To build a libburnia-project.org subproject it should be sufficient to go
-into its toplevel directory (here: "libburn") and execute
+   tar xzf libburn-0.5.8.pl00.tar.gz
+   cd libburn-0.5.8
    ./configure --prefix=/usr
    make
 
 To make libburn accessible for running resp. application development,
-and to install the cdrecord compatibility binary cdrskin, do:
-   make install
+and to install the cdrecord compatibility binary cdrskin, do
+(as Superuser):
 
+   make install
 
-Above procedure installs cdrskin depending on libburn.so.4 .
+This procedure installs libburn.so.4 and cdrskin depending on it.
 For a standalone cdrskin binary, see cdrskin/README.
 
 
+                                  From SVN
+
+Our build system is based on autotools. For preparing the build of a SVN 
+snapshot you will need autotools of at least version 1.7. 
+Do in a directory of your choice:
+
+   svn co http://svn.libburnia-project.org/libburn/trunk libburn-0.5.9
+   cd libburn-0.5.9
+   ./bootstrap
+   ./configure --prefix=/usr
+   make
+   make install
+
+Warning: The trunk might contain experimental features which might not
+         persist until next release. 
+
+------------------------------------------------------------------------------
+
 An important part of the project, libisofs, is hosted in a bzr repository at
 launchpad.net :
    bzr branch lp:libisofs
@@ -51,7 +63,6 @@ Another part the project, libisoburn, is hosted in the libburnia SVN, too:
 
 See README files there.
 
-
 ------------------------------------------------------------------------------
 
 
@@ -59,7 +70,7 @@ See README files there.
 
 libburnia-project.org is an open-source software project for reading, mastering
 and writing optical discs.
-For now this means only CD media and all single layer DVD media except DVD+R.
+For now this means CD media, all DVD media except DVD-R DL, all BD media.
 
 The project comprises of several more or less interdependent parts which
 together strive to be a usable foundation for application development.
@@ -68,18 +79,16 @@ classical (and valuable) Linux tools.
 Currently it is supported on Linux with kernels >= 2.4 and on FreeBSD versions 
 with ATAPI/CAM support enabled in the kernel, see atapicam(4).
 
-Our scope is currently Linux 2.4 or 2.6 and FreeBSD versions with ATAPI/CAM
-support enabled in the kernel, see atapicam(4). For ports to other systems
-we would need : login on a development machine resp. a live OS on CD or DVD,
-advise from a system person about the equivalent of Linux sg or FreeBSD CAM,
-volunteers for testing of realistic use cases.
+For ports to other systems we would need : login on a development machine
+resp. a live OS on CD or DVD, advise from a system person about the equivalent
+of Linux sg or FreeBSD CAM, volunteers for testing of realistic use cases.
 
-We have a well tested code base for burning data and audio CDs and many DVD
-types. The burn API is quite comprehensively documented and can be used to
-build a presentable application.
-We have a functional binary which emulates the core use cases of cdrecord in
-order to prove that usability, and in order to allow you to explore libburn's
-scope by help of existing cdrecord frontends.
+We have a well tested code base for burning data and audio CDs, DVDs and BDs.
+The burn API is quite comprehensively documented and can be used to build a
+presentable application.
+We have a functional application which emulates the core use cases of cdrecord
+in order to prove that usability, and in order to allow you to explore
+libburn's scope by help of existing cdrecord frontends.
 
 ISO 9660 filesystems with Rock Ridge and Joliet extensions can be created
 and manipulated quite freely. This capability together with our burn capability
@@ -119,8 +128,9 @@ The project components (list subject to growth, hopefully):
 - xorriso  is an application of all three libraries which creates, loads,
            manipulates and writes ISO 9660 filesystem images with
            Rock Ridge extensions. Manipulation is not only adding or
-           overwriting of files but also deletion, renaming, and attribute
-           changing.
+           overwriting of files but also deleting, renaming, attribute
+           changing, incremental backups, activating boot images, and
+           extracting of files from ISO images to disk.
            See xorriso/README for more.
 
 - "test"   is a collection of application gestures and examples given by the
@@ -336,6 +346,8 @@ Project history as far as known to me:
 - 7th Dec 2008 libburn-0.5.8 prevents a SIGSEGV with wierd CD table-of-content
   and improves BD-RE formatting.
 
+- 9th Dec 2008 Our project received a donation from Thomas Weber.
+
 
 ------------------------------------------------------------------------------
 

cdrskin/README

@@ -274,8 +274,8 @@ 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
+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
@@ -350,14 +350,24 @@ 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 , DVD+R DL , BD-R
 
 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
 of the layer break where a reading drive might show some delay while switching
 between both media layers.
 
+BD-R are sold unformatted blank. If used without initial formatting then the
+drive is supposed to format them to maximum payload size with no Defect
+Management (see also above with BD-RE).
+If Defect Management is desired then BD-R need to be formatted before the
+first attempt to write a session to them.
+blank=format_if_needed    will detect the situation and eventually apply
+                          default sized Defect Management formatting.
+blank=format_defectmgt_*  will apply non-default parameters to formatting.
+
 
                               Emulated Drives
 

cdrskin/cdrskin.1

@@ -2,7 +2,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 CDRSKIN 1 "Oct 15, 2008"
+.TH CDRSKIN 1 "Dec 10, 2008"
 .\" Please adjust this date whenever revising the manpage.
 .\"
 .\" Some roff macros, for reference:
@@ -16,7 +16,7 @@
 .\" .sp <n>    insert n+1 empty lines
 .\" for manpage-specific macros, see man(7)
 .SH NAME
-cdrskin \- burns preformatted data to CD, DVD, and BD-RE via libburn.
+cdrskin \- burns preformatted data to CD, DVD, and BD via libburn.
 .SH SYNOPSIS
 .B cdrskin
 .RI [ options | track_source_addresses ]
@@ -28,14 +28,14 @@ cdrskin \- burns preformatted data to CD, DVD, and BD-RE via libburn.
 .\" respectively.
 .PP 
 \fBcdrskin\fP is a program that provides some of cdrecord's options
-in a compatible way for CD media. With DVD and BD-RE it has its own ways.
+in a compatible way for CD media. With DVD and BD it has its own ways.
 You do not need to be superuser for its daily usage.
 .SS
 .B Overview of features:
 .br
 Blanking of CD-RW and DVD-RW.
 .br
-Formatting of DVD-RW, DVD+RW, DVD-RAM, BD-RE.
+Formatting of DVD-RW, DVD+RW, DVD-RAM, BD.
 .br
 Burning of data or audio tracks to CD,
 .br
@@ -45,7 +45,7 @@ or in Session at Once mode for seamless tracks.
 .br
 Multi session on CD (follow-up sessions in TAO only)
 .br
-or on DVD-R[W] (in Incremental mode) or on DVD+R[/DL].
+or on DVD-R[W] (in Incremental mode) or DVD+R[/DL] or BD-R.
 .br
 Single session on DVD-RW or DVD-R (Disk-at-once).
 .br
@@ -164,10 +164,10 @@ make it completely unreadable. It is no effective privacy precaution.
 Multiple cycles of blanking and overwriting with random numbers might be
 needed.
 .SS
-.B Sequentially Recordable DVD Media:
+.B Sequentially Recordable DVD or BD Media:
 .br
-Currently DVD-RW, DVD-R and DVD+R[/DL] can be used for the Sequential recording
-model.
+Currently DVD-RW, DVD-R , DVD+R[/DL], and BD-R can be used for the Sequential
+recording model.
 .br
 This applies to DVD-RW only if they are in state "Sequential Recording".
 The media must be either blank or appendable.
@@ -201,14 +201,18 @@ unpredicted length and to keep media appendable by option
 The only restriction towards CD-R[W] is the lack of support for -audio tracks.
 Multiple tracks per session are permissible.
 .br
-The write modes for DVD+R[/DL] resemble those with DVD-R except that with +R
-each track gets wrapped in an own session. There is no -dummy writing with
-DVD+R[/DL].
+The write modes for DVD+R[/DL] and BD-R resemble those with DVD-R except that
+each track gets wrapped in an own session. There is no -dummy writing
+with DVD+R[/DL] or BD-R.
 .br
 Quite deliberately write mode -sao insists in the tradition of a predicted
 track size and blank media, whereas -tao writes the tracks open ended and
 allows appendable media.
 .br
+BD-R may be formatted before first use to enable the Defect Management which
+might catch and repair some bad spots at the expense of slow speed
+even with flawless media.
+.br
 .B Note:
 Option -multi might make DVD media unreadable in some DVD-ROM drives.
 Best reader compatibility is achieved without it
@@ -353,7 +357,7 @@ audio track. Same is done for suffix ".au" and SUN Audio.
 Option -audio may be used only with CD media and not with DVD or BD.
 .TP 
 .BI blank= type
-Blank a CD-RW, DVD-RW, or format a DVD-RW, DVD+RW, DVD-RAM, BD-RE.
+Blank a CD-RW, DVD-RW, or format a DVD-RW, DVD+RW, DVD-RAM, BD.
 This is combinable with burning in the same run of cdrskin.
 The type given with blank= selects the particular behavior:
 .RS
@@ -365,7 +369,7 @@ It is a reason to abort if the media cannot assume thoroughly writeable state,
 e.g. if it is non-blank write-once.
 .br
 This leaves unformatted DVD-RW in unformatted blank state. To format DVD-RW use
-blank=format_overwriteable.
+blank=format_overwriteable. Blank unformatted BD-R stay unformatted.
 .br
 (Note: blank=as_needed is not an original cdrecord option.)
 .TP
@@ -394,10 +398,11 @@ This is faster than full blanking but may yield media incapable of
 Incremental Streaming (-tao).
 .TP
 format_if_needed
-Format a media if it is not overwriteably formatted yet, 
+Format a media if it is not formatted yet, 
 and if cdrskin supports formatting for the media type,
 and if formatting will not happen automatically during write.
-This currently applies to unformatted DVD-RW, DVD-RAM and BD-RE.
+This currently applies to unformatted DVD-RW, DVD-RAM, BD-RE,
+and blank unformatted BD-R.
 Eventually the appropriate default formatting is chosen.
 If other media or states are encountered then nothing happens.
 .br
@@ -427,7 +432,7 @@ For DVD+RW this is the only supported explicit formatting type. It provides
 complete "de-icing" so no reader slips on unwritten data areas.
 .TP
 format_defectmgt
-Format DVD-RAM or BD-RE to reserve the default amount of spare blocks for
+Format DVD-RAM or BD to reserve the default amount of spare blocks for
 defect management.
 .br
 The following format_defectmgt_* allow to submit user wishes which
@@ -451,25 +456,24 @@ Whether there happens certification at all depends much on the media state
 and the actually selected format descriptor.
 .TP
 format_defectmgt_max
-Format DVD-RAM or BD-RE to reserve a maximum number of spare blocks.
+Format DVD-RAM or BD to reserve a maximum number of spare blocks.
 .TP
 format_defectmgt_min
-Format DVD-RAM or BD-RE to reserve a minimum number of spare blocks.
+Format DVD-RAM or BD to reserve a minimum number of spare blocks.
 It might be necessary to format format_defectmgt_none first in order to get
 offered the most minmal spare blocks sizes for format_defectmgt_min.
 .TP
 format_defectmgt_none
-Format DVD-RAM or BD-RE to the largest available payload in the hope to disable
-defect management at all. This seems not to have a speed increasing effect,
-though.
+Format DVD-RAM or BD to the largest available payload in the hope to disable
+defect management at all. This may or may not have a speed increasing effect.
 .TP
 format_defectmgt_payload_<size>
-Format DVD-RAM or BD-RE. The text after "format_defectmgt_payload_" gives a
+Format DVD-RAM or BD. The text after "format_defectmgt_payload_" gives a
 number of bytes, eventually with suffixes "s", "k", "m". The largest number
 of spare blocks will be chosen which allows at least the given payload size.
 .TP
 format_by_index_<number>
-Format DVD-RW, DVD+RW, DVD-RAM or BD-RE.
+Format DVD-RW, DVD+RW, DVD-RAM or BD.
 The number after "format_by_index_" is used as index to the list of available
 format descriptors. This list can be obtained by option --list_formats.
 The numbers after text "Format idx" are the ones to be used with
@@ -1182,7 +1186,7 @@ original cdrecord.
 .TP
 .BI stream_recording="on"|"off"
 By setting "on" request that compliance to the desired speed setting is
-preferred over management of write errors. With DVD-RAM and BD-RE this can
+preferred over management of write errors. With DVD-RAM and BD this can
 bring effective write speed near to the nominal write speed of the media.
 But it will also disable the automatic use of replacement blocks
 if write errors occur. It might as well be disliked or ignored by the drive.

cdrskin/wiki_plain.txt

@@ -10,8 +10,8 @@ Schilling's cdrtools. cdrskin strives to be a second source for the services
 traditionally provided by cdrecord. Currently it does CD-R and CD-RW this way.
 Overwriteable media DVD-RAM, DVD+RW, DVD-RW, and BD-RE are handled differently
 than with cdrecord-ProDVD in order to offer TAO-like single track recording.
-Sequential DVD-R[W], DVD+R, DVD+R DL are handled like CD-R[W] with TAO and
-multi-session. Additionally cdrskin offers cdrecord-ProDVD-like mode DAO
+Sequential DVD-R[W], DVD+R, DVD+R DL, BD-R are handled like CD-R[W] with TAO
+and multi-session. Additionally cdrskin offers cdrecord-ProDVD-like mode DAO
 with DVD-R[W].
 
 cdrskin does not contain any bytes copied from cdrecord's sources.