summaryrefslogtreecommitdiff
path: root/FAQ
diff options
context:
space:
mode:
authorIgor Pashev <pashev.igor@gmail.com>2012-12-31 05:04:42 +0400
committerIgor Pashev <pashev.igor@gmail.com>2012-12-31 05:04:42 +0400
commit71dc8760ff4de5f365330d1bc571d934deb54af9 (patch)
tree7346d42a282562a3937d82307012b5857d642ce6 /FAQ
downloadcdrkit-71dc8760ff4de5f365330d1bc571d934deb54af9.tar.gz
Imported Upstream version 1.1.11upstream/1.1.11upstream
Diffstat (limited to 'FAQ')
-rw-r--r--FAQ33
1 files changed, 33 insertions, 0 deletions
diff --git a/FAQ b/FAQ
new file mode 100644
index 0000000..cc31a21
--- /dev/null
+++ b/FAQ
@@ -0,0 +1,33 @@
+Frequently Asked Questions about cdrkit
+=======================================
+
+Q: What does "wodim" stand for?
+A: It is not a forest troll and not a winner of the inpronounceability
+ contest. It was simply the next alternative to wom (Writes Optical Media)
+ which was unfortunately already used by other software products.
+
+Q: What this name of ... mean?
+A: Terminology: some names are based on pure imagination, some on
+ abbreviations, some on permutations of chars in descriptions.
+
+ genisoimage: Generate ISO IMAGEs
+ icedax: InCrEdible Audio eXtractor
+ librols: LIB Remains Of LibSchily
+ libusal: LIB Unified/Universal Scsi Access Layer
+ netscsid: NET SCSI Daemon
+ readom: READ Optical Media (see also wodim)
+ wodim: see above
+
+Q: Are there additional depedencies, compared to cdrtools?
+A: Yes. Libcap is required on Linux plattform. Libmagic is needed to support
+ content-based creator/type tables with HFS (optional). Libiconv is needed to
+ support iconv-based filename converstion, eg. from UTF-8 ins Joliet's UCS-2
+ unicode (optional, on plattform where iconv is not already included in the libc
+ system library).
+
+Q: Burning dies with (logical unit communication crc error (ultra-dma/32)).
+ Reason? Solutions?
+A: Try enabling DMA for your device. Some CDROM readers/writters seem to send
+ non-critical UDMA control/error codes without beeing in DMA mode and so
+ those messages are not interpreted by the kernel but delivered to the
+ applications instead.