Imported Upstream version 1.1.11upstream/1.1.11upstream

11 files changed, 1418 insertions, 0 deletions

diff --git a/doc/READMEs/README.ATAPI b/doc/READMEs/README.ATAPI
new file mode 100644
index 0000000..8b2e601
--- /dev/null
+++ b/doc/READMEs/README.ATAPI
@@ -0,0 +1,589 @@
+
+The file attached below provides a short explanation about the nature of ATAPI
+and the support for it on various platforms. However, it was written for an
+old version of cdrtools by Joerg Schilling and completed with even older guides
+supplied by other authors, therefore parts of the content are no longer true or
+are not applicable anymore. Read and interpret with care!
+
+See README.ATAPI.setup for a quick setup guide for Linux.
+
+Eduard Bloch, 2006
+
+# @(#)README.ATAPI	1.3 04/05/20 Copyright 1997-2004 J. Schilling
+
+People (with a Linux only background) often ask me why do you depend on 
+"ATAPI-SCSI emulation", why don't you support generic IDE?
+
+	Well first a statement: There is no single IDE burner out!
+	Even a CD-ROM cannot be used decently if you use only IDE commands.
+	Opening/closing the door, playing audio and similar things
+	cannot be done using vanilla IDE commands - you will need SCSI commands
+	to do this. But how do we do this with a drive that uses an IDE
+	interface?
+
+		ATAPI stands for ATA Packet Interface
+
+	The ATAPI standard describes method of sending SCSI commands over IDE
+	transport with some small limitations to the "real" SCSI standard.
+	SCSI commands are send via IDE transport using the 'ATA packet'
+	command. There is no SCSI emulation - ATAPI drives include native
+	SCSI command support. For this reason, sending SCSI commands to ATAPI
+	drives is the native method of supporting ATAPI devices. Just imagine
+	that IDE is one of many SCSI low level transport mechanisms.
+
+	This is a list of some known SCSI transports:
+
+	-	Good old Parallel SCSI 50/68 pin (what most people call SCSI)
+	-	SCSI over fiber optics (e.g. FACL - there are others too)
+	-	SCSI over a copper variant of FCAL (used in modern servers)
+	-	SCSI over IEEE 1394 (Fire Wire)
+	-	SCSI over USB
+	-	SCSI over IDE (ATAPI)
+
+	As you now see, the use of the naming convention "ATAPI-SCSI emulation"
+	is a little bit misleading. It should rather be called:
+		"IDE-SCSI host adapter emulation"
+
+Some naming explanations:
+
+	ATA	Attachment Adapter
+	IDE	Integrated Drive Electronics (A Drive that includes ATA)
+	ATAPI	ATA Packet Interface
+
+When wodim has problems with ATAPI drives on Linux this usually is a Linux 
+kernel problem. The Linux kernel maintainers unfortunately refuse to correct
+their current IDE driver system setup which does not support ATAPI by default.
+ATAPI _is_ SCSI over IDE transport. It is hard to understand why Linux still
+uses a default driver setup that is designed for IDE CD-ROM drives made
+before 1994 (using a IDE compat mode that only allows to use the drive
+read-only) and does not handle to send SCSI commands to ATAPI drives by
+default. This makes it hard for people who just started with Linux to do
+CD-writing on Linux if they own an ATAPI drive. Both Linus Torvalds and
+Alan Cox admit that they don't own a CD/DVD writer, how should they know about
+the problems?
+
+There are bugs with the DMA implementation that are known for many years
+but they don't get fixed.
+
+/*--------------------------------------------------------------------------*/
+Which Operating systems support ATAPI
+
+-	AIX: Status unknown! Please report your experience...
+
+-	Apple Mac OS X (Darwin): Supported
+
+-	BeOS (libscg maps ATAPI to SCSI bus # >= 8
+
+-	BSD/OS: Status unknown! Please report your experience...
+
+-	FreeBSD:
+		-	YES for the latest default kernel.
+			It includes finally ATAPI-Cam
+
+		-	NO for the older kernels.
+			Yes, if you install a kernel patch from
+			Thomas Quinot <thomas@cuivre.fr.eu.org>
+			See http://www.cuivre.fr.eu.org/~thomas/atapicam/
+			and README.FreeBSD
+
+-	HP-UX: It looks like ATAPI does not work correctly due to kernel bugs.
+
+	New information:
+	HP supports a HP A7853A B/C class machine (s700_800) with HP-UX-11.x
+	You need to install a patch:
+
+	Patch Name: PHKL_27224 Patch Description: s700_800 11.00 IDE/ATAPI 
+	cumulative patch
+
+
+-	Linux (unfortunately not in the default configuration)
+
+	-	It works more or less if you include ide-scsi
+
+	-	Linux-2.4.xx includes a CDROM Packet interface in the
+		IDE CD driver. For this driver libscg now includes
+		support in pre-alpha status. Use wodim dev=ATAPI -scanbus
+		to check for drives and e.g. wodim dev=ATAPI:0,0 ....
+		for writing. Note that this interface is not integrated into
+		the standard libscg device naming scheme. Support for
+		this interface has been included because it is the only
+		way to use a PCCARD/PCMCIA writer - trying to use ide-scsi
+		on a PCATA interface will cause a Linux kernel panic
+		or will block all ATAPI drives.
+
+	-	Starting with Linux-2.5.45, there is a new experimental
+		ATAPI interface initiated by Linus Torvalds. Unfortunately,
+		this interface does not fit well into the rest of the Linux
+		SCSI kernel transport naming scheme. Wodim allows to
+		use this interface by calling e.g. wodim dev=ATA:1,0,0 ...
+
+	All Linux ATAPI transport implementations do not support DMA.
+	Current exceptions are:
+
+	-	ide-scsi with block size 2048 and if DMA has been enabled
+
+	-	The new experimental ATAPI interface starting with Linux-2.5.45
+		allows DMA if DMA has been enabled and the sector size is a
+		multiple of 4. This allows to use DMA for audio CDs and
+		when writing any type of CD in RAW mode.
+
+		Note that is a bad idea to first implement a new kernel
+		interface that also implements the named DMA implementation
+		bugs and later fix the DMA bug _only_ for this new
+		interface. It looks like the Linux kernel folks are not
+		very cooperative :-(
+
+	RAW mode is needed for many new and cheap drives that have bugs when
+	writing in cooked mode. If there is no DMA, you cannot write faster
+	than approx 16x.
+	
+
+-	NetBSD (releases 1.3 and newer)
+
+-	NeXT: Status unknown! Please report your experience...
+
+-	OpenBSD: (release 2.6 and newer)
+
+-	OS/2 (you need to fetch and install ATAPI support first)
+	see: http://www.leo.org/pub/comp/os/os2/leo/drivers/dasd/daniatapi.zip/
+
+-	OSF-1 / True64 Status unknown! Please report your experience...
+
+-	SCO-OpenServer: Supported with 5.0.6 and non-public patch or with
+			5.0.7. I don't know whether you need a patch for 5.0.7
+
+-	SCO-UnixWare: partial support with UnixWare 7.1.3 - some SCSI commands
+			that are needed for cdda2wav and DVD writing are blocked.
+			7.1.4 will have full ATAPI support.
+
+-	SGI/IRIX: Status unknown! Please report your experience...
+
+-	Solaris (you may need to use the USCSI transport interface to address 
+	ATAPI if the IDE hostadapter idriver implementation does not follow 
+	Sun's internal standards).
+
+	ATAPI works fine on Solaris 7 sparc and on Solaris 7/8 intel.
+	
+	On Solaris 8 (intel) and newer, the ATAPI/SCSI subsystem is integrated
+	correctly according to Sun's SCSA white paper, so the 'scg' driver works.
+	This is not true for Solaris on sparc where the ATAPI driver do not conform
+	to Sun's internal structuring rules. You need to use the USCSI interface
+	on for ATAPI drives on Solaris sparc for this reason.
+ 
+	Solaris 8 sparc has a ATA DMA bug that prevents wodim from working at all.
+	There is a fix from Sun available: the patch 108974-16 
+	Solaris 9 sparc works again, it has the fix for the ATA DMA bug included.
+
+	Newer versions of Solaris 9 disable DMA for CD-ROM drives on IDE.
+	Read README.solaris-x86-ATAPI-DMA to learn how this may be circumvented.
+
+-	VMS: works on recent versions!
+
+-	Win32 using a recent ASPI Layer supports ATAPI
+	You nay need to exclude mini port drivers (see README.win32).
+
+	Newer wodim versions also support the SPTI (SCSI Pass through ioctl).
+	Libscg uses SPTI by default if you are running NT-5.x or newer and are
+	administrator. With NT-4.x it may be possible to run wodim dev=SPTI:1,0.0 ...
+	But there are reports for blue screens (kernel crashes).
+
+-	DOS DOS-7 from win98 includes a ATAPI aware aspi
+	For other versions have a look at README.msdos and use e.g. "oakaspi".
+
+/*--------------------------------------------------------------------------*/
+General hints:
+
+***********************
+NOTE: IDE/ATAPI doesn't have disconnect/reconnect! you cannot expect the needed 
+	performance for CD-writing if you connect source and destination drive
+	to the same IDE cable.
+***********************
+
+If you never like to directly write a CD from CD-ROM source, this configuration
+seems to be the best:
+
+IDE 0	MSTR	->	HD1
+IDE 0	SLAV	->	HD2
+
+IDE 1	MSTR	->	CD-writer
+IDE 1	SLAV	->	CD-ROM
+
+If you like to write from both HD source and CD-ROM source, you should have
+the following configuration:
+
+IDE 0	MSTR	->	HD1	(does _not_ hold CD mastering data)
+IDE 0	SLAV	->	CD-Writer
+
+IDE 1	MSTR	->	HD2	(holds CD mastering data)
+IDE 1	SLAV	->	CD-ROM
+
+If cou cannot set up a decent cabling (e.g. because you use a notebook)
+you may try to use wodim -immed ...
+It runs slow commands in quick (immediate) return background mode and
+tries to wait between the write commands to allow to free the IDE cable
+so the wodim read process may fill the FIFO from the other drive
+on the same IDE cable.
+
+/*--------------------------------------------------------------------------*/
+The rest of this file is only valid for Linux!
+
+This was taken out of mails from From: Dave Cohen <dcohen@richmond.infi.net>
+and From: Gadi Oxman <gadio@netvision.net.il>
+(slightly modified marked ***JS *** except typo corrects)
+
+As all current Linux versions have ATAPI support for wodim,
+I removed the patch section. If you are running a Linux version
+that does not support ATAPI<->SCSI command transport, please upgrade.
+
+The basic driver design in Solaris would also allow to use ATAPI
+drives but unfortunately, Sun made a mistake in the mid-level design.
+If you want to use ATAPI drives with Solaris, ask Sun why they don't
+support SCSI passthrough to IDE although they are using a common driver
+concept.
+
+Please use cdrecord-1.6 final or later (if available), it includes the
+modifications needed for ATAPI drives and is still working with other 
+SCSI drives. Older revisions of cdrecord do not support ATAPI drives.
+
+If you are using Linux Kernel version prior to 2.1.73 or prior to
+2.0.35, please upgrade before you try to compile and use wodim.
+
+In any case, you need to configure a kernel with ATAPI/SCSI hostadapter
+emulation. Read carefully the following instructions:
+
+In any case, you need to disable generic IDE/ATAPI CDROM support in 
+order to make ATAPI SCSI emulation working.
+
+Many people ask why I use ATAPI-SCSI emulation.
+
+	The use of the naming convention "ATAPI-SCSI emulation" is a
+	little bit misleading. It should rather be called:
+		"SCSI host adapter emulation"
+
+	The ATAPI standard describes method of sending SCSI commands over IDE
+	with some small limitations to the "real" SCSI standard.
+	For this reason ATAPI-SCSI emulation is the native method of
+	supporting ATAPI devices.
+
+If you have problems to talk to the device when it is jumpered as "slave"
+try to use it  as "master". If you connect a hard disk to the same IDE
+cable as the CD writer or if you try to read/write data from another drive
+that is connected to the same IDE cable as the CD writer you may get
+problems too.
+
+NOTICE:
+
+With the newer 2.1.x or 2.2.x kernels it seems to be possible to run 
+SCSI/ATAPI hostadapter emulation and generic IDE at the same time by 
+selectively telling the kernel what to use for which drive.  However,
+this would not be needed if the Linux SCSI CD-ROM driver would be more 
+up to date and supports standard conforming drives.
+
+Jörg Schilling <schilling@fokus.fhg.de>
+
+--------------------------------------------------
+Here is a hint from Alan Brown <alanb@manawatu.gen.nz>:
+
+To allow ATAPI cd and ide-scsi support on the same machine, add 
+`hd<x>=ide-scsi` to the lilo.conf append entry, or use 
+`hd<x>=ide-scsi` at the bootup lilo prompt. 
+
+I have my HP-7200 RW drive as the primary drive on the second IDE 
+bus, so the statement used is "hdc=ide-scsi" 
+
+--------------------------------------------------
+
+Hope that the following  is helpful to you.
+
+I recently purchased a HP-7110i CD-RW, which is the U.S. only version of
+what you have. The HP 7100 and 7110  CD rewritables use the ATAPI
+standard. Originally, the drives were not supported under Linux (due to
+some inconsistencies with SCSI translations between the kernel and the
+CD), but that problem has just recently been fixed. There are some kernel
+and wodim patches that have been made to support this device that have
+yet to be officially incorporated into cdwrite and the kernel. In order to
+get your drive supported under Linux, you will have to do the following:
+
+1. Get the proper version of cdrecord.
+
+As of this writing, I am just getting ready to test Joerg's new cdrecord.
+I am currently operational on cdrecord-1.5, so I know that works, and I
+have attached patches for that version. 
+ 
+If you are in a hurry, you can download ver. 1.5, apply patches, and
+rock-n-roll. You may want to wait, though.  Up to you ;). The version with
+ATAPI support is cdrecord-1.6alpha5. I'm not sure if the current kernel
+patches are valid for this version, but i'll know soon enough.
+**** They are valid **** JS
+
+BTW, the new version of xcdroast now supports cdrecord - this version
+is in beta testing, too (currently uses cdrecord-1.5 but cdrecord-1.6a5
+should work with the current xcdroast too).  
+
+2. Upgrade to kernel version 2.0.31
+
+IDE/SCSI translation was first added in this kernel. Because your CD-RW is
+an ATAPI device, it will support SCSI command sets.  The translation
+allows you to map the device as a SCSI generic device. This will allow
+cdrecord to recognize it as a SCSI device.
+**** 2.0.31 still needs patches, get 2.0.35 or later **** JS
+
+3. Get the patches and apply them
+
+Attached find kernel patches for kernel sources ide.h and ide-scsi.c, and
+cdrecord source scsi_cdr.c (version 1.5 only). 
+**** Get cdrecord-1.6 or later **** JS
+
+3. Recompile kernel with SCSI emulation support
+
+If you do a "make menuconfig" or "make xconfig", select SCSI emulation
+under the category "Floppy, IDE, and other block devices".
+
+WARNING:
+Do not install SCSI support as a module - there is a bug in the makefile
+structure that will cause the compile to fail.  Compile directly into the
+kernel.   
+
+4. WARNING: Disable generic IDE/ATAPI CDROM support	*** JS ***
+
+If you don't do this, the SCSI emulation will not work  *** JS ***
+
+5. This is important too:
+You also need to enable SCSI and SCSI generic support   *** JS ***
+
+6. Make sure that /dev/sg* exists.
+If they are missing, create them.
+
+Dave Cohen
+dcohen@richmond.infi.net 
+(Patch instructions below)
+
+-----------------------------------------------------------------
+From: Danilo Fiorenzano <shade@juliet.gppsd.ab.ca>
+
+Anyway, here's what I did, using kernel version 2.0.33  I believe this
+is the proper way to get an HP-7100i to work (and as far as I can tell,
+any other IDE CD-writer unit):
+
+1) patch the kernel as described by README.ATAPI
+
+2) save your current kernel config to an alternate file, then run
+   "make mrproper"
+
+3) run 'make menuconfig' or 'make xconfig', then choose "load config
+   from alternate file" to restore the original configuration
+
+4) In "Floppy, IDE and other block devices", disable "IDE/ATAPI CD-ROM
+   support" and enable instead "scsi emulation"
+
+5) in "SCSI support" enable "SCSI support", "SCSI CD-ROM support" and
+   "SCSI generic support", everything directly in the kernel.
+
+6) compile, install kernel/modules, reboot.  Now, if everything went
+   fine, your CDROM units should show up with a message like:
+ "hdb: HP CD-Writer+ 7100, ATAPI CDROM drive - enabling SCSI emulation"
+
+7) run "wodim -scanbus" to make sure wodim can see the unit and
+   talk to it.  The end.
+
+Don't forget that now -all- of your CD drives are seen as -SCSI- units
+by all programs (/dev/scd0 etc.), so you might want to relink
+/dev/cdrom to the proper scd<n> in order to get xcdplay or whatever to
+work again.
+
+
+-------------------------------------------------------------------------------
+NOTE: 
+
+1)	Current wodim releases support ATAPI
+
+2)	Linux 2.0.35 or Linux 2.1.73 or later include ATAPI support
+-------------------------------------------------------------------------------
+From whampton@staffnet.com Fri Jan 14 05:21:34 2000
+From: "W. Wade, Hampton IV" <whampton@staffnet.com>
+
+You may wish to include/append these notes to your ATAPI notes....
+
+I have my 4X Acer CD-R/RW ATAPI drive working with Linux.   My platform
+is
+RedHat 6.1 with kernel 2.2.14.  My first ATAPI CD device is a DVD with
+the second
+the CD-R.  I made the following changes:
+
+Steps:
+
+1.  Identify which device is the CD-R -- in my case the fourth ATAPI
+device, /dev/hdd.
+
+2.  Compile the kernel to include ATAPI CDROM and SCSI emulation:
+
+     Under the block devices menu:
+                Y or M     Include IDE/ATAPI CDROM support
+                Y or M     SCSI emulation
+
+3.  Build and install the upgraded kernel.
+
+4.  If you selected modules, add them to the /etc/conf.modules file.
+
+5.  In the /etc/lilo.conf file add an append line for ide-scsi, in my
+case:
+        append = "hdc=ide-scsi hdd=ide-scsi"
+
+6.  Reboot to the new kernel and make sure the ide-scsi module is loaded
+
+        /sbin/lsmod | grep ide-scsi
+
+7.  Make a link from the proper SCSI device to a symbolic, e.g.,
+/dev/cdrom:
+      In my case the DVD is the first CD, hence appears as /dev/scd0 to
+scd7
+      (cat /proc/scsi/scsi to get a full list of devices -- the first
+CD-ROM will
+      appear as scd0, etc.)  With the current ATAPI-SCSI module, each CD
+
+      device appears as 8 SCSI devices (different logical units).  If
+you have
+      two devices, like I do, you may have to make a node for the second
+device.
+      In my case I had to make scd8:
+
+            cd /dev
+            mknod scd8 b 11 8
+
+        Then make links, in my case:
+
+            ln -s scd0 cdrom
+            ln -s scd8 cdr
+
+        Note, many CD-ROM player programs expect the audio CD drive to
+        be located at /dev/cdrom (xplaycd, etc.), hence this link is
+recommended.
+
+        If you try to use /dev/hdc (or wherever your CD or CD-R is)
+after loading
+        the ide-scsi module, you may not be able to mount CD's or play
+audio
+        discs -- you have to use the new SCSI names for the device.
+
+8.  Fix your /etc/fstab file to mount the /dev/cdrom and /dev/cdr
+
+
+/*--------------------------------------------------------------------------*/
+From: Eduard Bloch <edi@gmx.de>
+
+Situation:
+   Linux: Kernel 2.2.15 (Debian package kernel-image-2.2.15)
+   Distribution: Debian Potato (deep freeze), i386
+   Devices: one CDRW-Writer, one CDROM-drive, both ATAPI
+
+1. Become root, try "grep hd.: /var/log/kern.log" to find out where your
+   ATAPI-devices are connected to (hd?-names).
+2. Edit your boot configuration file, eg. /etc/lilo.conf if you use
+   lilo or the batch-file if you boot via loadlin.
+3. Find a line where you can append additional kernel parameters, eg.
+   "append=" in lilo.conf or the loadlin-line in the batch file.
+4. Append sth. like this: "hdb=ide-scsi hdc=ide-scsi max_scsi_luns=1"
+   The hdX-parameters defines devices that should be mapped to SCSI
+   latter. You may do it with non-writers too, since the emulation layer
+   is almost complete, or let them out so the devices will use their
+   native drivers.
+5. Save the file, reinstall the bootloader (ie. running "/sbin/lilo")
+6. Call "modconf", load "sg" and "ide-scsi" from the SCSI-section
+7. Reboot Debian, watch while booting, you should see a line like this
+   "Detected scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0".
+   Your old ATAPI devices virtually don't exist any longer, use the
+   SCSI equivalents instead.
+8. Become root, setup devices:
+      cd /dev
+      MAKEDEV sg scd
+      ln -s scd0 cdrom # NOTE: or cdrw, first check which drive is here
+      ln -s scd1 cdrw  # NOTE: see above, maybe cdrom
+   Check the new SCSI settings:
+      wodim -scanbus
+   Setup wodim's environment - edit /etc/wodim.conf:
+      CDR_DEVICE=cdrw
+      cdrw=1,0,0        4       8m
+      cdrom=1,2,0       0       0m
+   Input the right values, the fields are described in the manpage
+   of wodim. Alternatively, you may use this values as
+   wodim-parameter or take a frontend with an own configuration
+   scheme, then you don't need to modify /etc/wodim.conf.
+9. It's done! Insert a CD and try "wodim -v -toc"
+/*--------------------------------------------------------------------------*/
+He had constant buffer underrun problems:
+
+From: "Trenton D. Adams" <trenton.adams@telusplanet.net>
+
+I enabled DMA, and 32-bit mode on the CD-Writer using "hdparm". 
+This fixed the writing problem.
+
+/*--------------------------------------------------------------------------*/
+From: "Mario Moder" <clay-man@freenet.de>
+-----
+TEAC CD-W54E
+
+I recently installed a TEAC CD-W54E (an ATAPI CD-RW-Recorder) and I had
+problems with buffer underruns and other errors when burning a CD (with
+Linux and Windows 2000). My system has an old ASUS P/I-P55T2P4 Pentium
+mainboard with Intel PCI-Bus-Master-IDE (I think the chipset is an Intel
+430HX and the IDE controller is an 82371SB). The harddisk is the master on
+the primary IDE channel, and the CD-Recorder is the master on the secondary
+IDE channel.
+
+After turning off DMA for the CD-Recorder AND the harddisk, the drive had no
+longer problems with burning a CD. You can try the following things to make
+it work, if you have similar problems with a similar hardware configuration:
+
+For Linux (Kernel 2.2.19):
+Turn off "Enable DMA by default" in the kernel (and then compile a new
+kernel), if you had it turned on or use "hdparm" to turn of DMA for both the
+CD-Recorder and the harddisk
+
+For Windows 2000:
+In the Device Manager go to "IDE ATA/ATAPI-Controller" and open the
+properties for the first and second IDE channel. There you change the mode
+of the devices from DMA to PIO.
+-----
+
+/*--------------------------------------------------------------------------*/
+
+Hints for the Linux Packet code in ide-cdrom.c:
+
+	WARNING! It seems that this driver does not allow to send all
+	SCSI commands. A command that definitely fails is READ FULL TOC.
+	For this reason, you cannot read those 'defective' audio CDs
+	with broken TOC when you use this interface.
+
+	Thanks to Alexander Kern <alex.kern@gmx.de> for the idea and first 
+	code fragments for supporting the CDROM_SEND_PACKET ioctl() from 
+	the cdrom.c kernel driver. Please note that this interface in principle 
+	is completely unneeded but the Linux kernel is just a cluster of 
+	code and does not support planned orthogonal interface systems. 
+	For this reason we need CDROM_SEND_PACKET in order to work around a 
+	bug in the linux kernel that prevents to use PCATA drives because 
+	the kernel panics if you try to put ide-scsi on top of the PCATA 
+	driver. 
+
+	The code is currently in "status nascendi" but usable with some trade offs.
+
+	To use: call e.g.
+
+		wodim -scanbus dev=ATAPI:
+
+		wodim -dao -v speed=24 dev=ATAPI:0,0 ....
+
+	Be careful! This code is only needed in order to be able to use
+	PCATA CD-writers on notebooks because there is a severe kernel bug.
+	Unfortunately, this bug causes the kernel to hang (and force you
+	to reboot) if you try to call:
+
+		wodim -scanbus
+
+	without the dev=ATAPI: option. 
+
+	In this case wodim will hang infintely and unkillable 
+	in open("/dev/sg1", 2) => you need to reboot :-(
+
+	Repeat by: Insert a PCATA CD-Writer in a Sony VAIO notebook and run
+			wodim -scanbus. 
+
diff --git a/doc/READMEs/README.ATAPI.setup b/doc/READMEs/README.ATAPI.setup
new file mode 100644
index 0000000..e283342
--- /dev/null
+++ b/doc/READMEs/README.ATAPI.setup
@@ -0,0 +1,87 @@
+Howto setup an ATAPI CD-RW/DVD+-RW recorder on Debian/Ubuntu
+============================================================
+
+This guide should be applicable to most kernel 2.6 using distributions of
+GNU/Linux. For installations with kernel 2.4, continue reading below.
+
+Kernel 2.6.*
+============
+
+If you have just one CD writer in your computer, CD-writing should work out of
+the box. There should be a symbolic link /dev/cdrw which points to your actual
+CD-Writer's device (e. g. /dev/hdb). If the link is not present (eg.  the
+system is not using udev/devfs) or if you want to use a different device as
+default, you can configure the device in /etc/wodim.conf:
+
+  CDR_DEVICE=/dev/hdd
+
+would configure the default device to be /dev/hdd, i. e. the slave
+device on the secondary IDE bus.
+
+You can always override this default setting with wodim's "dev"
+option:
+
+    wodim dev=/dev/hdc ...
+
+Only users part of the system group "cdrom" are able to write CDs.
+If you wish to allow non-root users to write CDs then add your users to the
+cdrom group ("adduser user cdrom") and let the user completely logout and
+re-login.
+Note: with certain kernel versions wodim can fail with this message:
+"wodim: Operation not permitted. Cannot send SCSI cmd via ioctl"
+In this case it still does need the suid bit - please send patches if you have
+identified the reason of that problem.
+
+Kernel 2.4.* (for 2.5/2.6, see above)
+=====================================
+
+Where we start:
+   Linux: Kernel 2.4.20-bf2.4 (Debian package kernel-image-2.4.20-bf2.4)
+   Distribution: Debian Woody 3.0r2, i386
+   Devices: one CDRW-Writer, one CDROM-drive, both ATAPI
+
+1. Become root, try "grep hd.: /var/log/kern.log" to find out where your
+   ATAPI-devices are connected to (hd?-names).
+2. Edit your boot configuration file, eg. /etc/lilo.conf if you use
+   lilo or the batch-file if you boot via loadlin.
+3. Find a line where you can append additional kernel parameters, eg.
+   "append=" in lilo.conf or the loadlin-line in the batch file.
+4. Append sth. like this: "hdb=ide-scsi hdc=ide-scsi max_scsi_luns=1"
+   The hdX-parameters defines devices that should be mapped to SCSI
+   latter. You may do it with non-writers too, since the emulation layer
+   is almost complete. Or omit some so the devices will use their
+   native drivers (eg. ide-cd).
+5. Save the file, reinstall the bootloader (ie. running "/sbin/lilo")
+6. Call "modconf" in a console or xterm, enter the section 
+   "kernel/drivers/scsi", load "sg" and "ide-scsi"
+7. Reboot Debian, watch while booting, you should see a line like this:
+   "Detected scsi CD-ROM sr0 at scsi0, channel 0, id 0, lun 0".
+   Your old ATAPI devices virtually don't exist any longer, you cannot refer to
+   /dev/hd* as CDROM drives. Use the SCSI equivalents instead, /dev/sr*.
+8. Become root, setup devices:
+      cd /dev
+      MAKEDEV sg scd
+      ln -s scd0 cdrom # NOTE: or cdrw, first check which drive is here
+      ln -s scd1 cdrw  # NOTE: see above, maybe cdrom
+   Check the new SCSI settings:
+      wodim -scanbus
+   Setup wodim's environment - edit /etc/wodim.conf:
+      CDR_DEVICE=cdrw
+      cdrw=1,0,0        4       8m
+      cdrom=1,2,0       0       0m
+   Insert the right values, the fields are described in the manpage
+   of wodim. Alternatively, you may use these values as
+   wodim-parameter or take a frontend with an own configuration
+   scheme, then you don't need to modify /etc/wodim.conf.
+   The columns must be separated by tabs.
+9. It's done! Insert a CD and try "wodim -v -toc". To create your first CD-ROM, try:
+   
+   mkisofs -v -r -J /directory/to/be/written | wodim -v -dummy -
+
+   (read wodim(1), "man 1 wodim", for details)
+
+10. If you wish to allow non-root users to write CDs, you must give them 
+    permissions to do so. Set suid-root permissions on the executable,
+    then add your users to the cdrom group ("adduser user cdrom") and
+    let the user completely logout and re-login.
+
diff --git a/doc/READMEs/README.audio b/doc/READMEs/README.audio
new file mode 100644
index 0000000..7e2d7c9
--- /dev/null
+++ b/doc/READMEs/README.audio
@@ -0,0 +1,50 @@
+Why do I hear only noise from my first audio CD?
+
+You may have a byte swapping problem, try wodim -swab
+but note that is is most unlikely that you need to use the -swab
+option from wodim unless your input files are broken.
+It makes more sense to find out why the inout files are not OK.
+
+wodim assumes Motorola/Network byte order (big-endian) on input
+regardless of the byte order of the CD-Recorder. If wodim
+encounters a .wav file, byte order is corrected to match the byte order
+of the .wav file.
+
+wodim by default uses Track at once. This always gives 2 seconds
+pause between two audio tracks and loweres the audio quality.
+
+For best audio CD quality, use wodim -dao (to write in Session At Once)
+ot wodim -raw (to write in RAW mode). Note that there are a lot of drives
+notably from Lite-ON that have defective firmware and will write defective
+CDs if you use either TAO or SAO mode. In RAW mode, wodim has the
+full control over the complete CD and the chance that the CD is OK
+is much higher.
+
+The 2 seconds pause between two audio tracks is the CD ***standard***
+
+The standard says:
+	Each track starts with 2 seconds of silence
+	followed by at least 4 seconds of audio data.
+
+For that reason the 2 second pause is generated by the CD-R drive in 
+Track at once (TAO) mode.
+
+CD's that have no pause between two tracks are illegal (compared to RED BOOK).
+These illegal disks may be made with Disk At Once (DAO) only.
+In DAO mode the writing software needs to send the 2 seconds pause as 
+binary zeroes and therefore is able to create illegal disks by 
+sending audio data instead. 
+
+Some drives don't accept to write illegal disks even in SAO mode.
+In this case, use the RAW mode. In RAW mode, the drive does not even
+"know" what is going on and thus cannot prevent you from writing such
+a disk.
+
+This audio data (the last two seconds of a track in this case)
+however are part of the next track from viewing the TOC of the disk.
+Digital Audio Extraction programs that work correctly (as intended by the
+CD standard) split the content of a CD into files by including the
+pre-gap (usually holding 2 seconds of pause) at the end of the previous
+track.
+
+Eduard Bloch, based on documentation from Joerg Schilling
diff --git a/doc/READMEs/README.cdplus b/doc/READMEs/README.cdplus
new file mode 100644
index 0000000..24deb0d
--- /dev/null
+++ b/doc/READMEs/README.cdplus
@@ -0,0 +1,85 @@
+Wodim and genisoimage allow you to create multi-session CD's with all
+supported drives.
+
+According to www.cd-info.com, a CD+ is a CD with two sessions.
+The first session is an audio session, the second session a data
+session.
+
+Creating a CD+ is first writing an audio session in 
+multi session mode and then writing a data session.
+
+If you like to append a filesystem to a audio CD, first extract the 
+CD by calling:
+
+	icedax -B -vall
+
+This first audio session may be written in TAO mode with the command
+
+	wodim -multi -audio file1 ....
+
+or in DAO mode with the command
+
+	wodim -dao -multi -useinfo -audio file1 ....
+
+To add the second session that contains the data track, you need
+to create an ISO-9660 file system that starts not at sector 0.
+
+With the current genisoimage, you must use the following method:
+
+-	First call wodim -msinfo for your prepared multi-session audio CD.
+
+	you will get something like 0,12345
+
+-	Now call genisoimage:
+
+	genisoimage -o fs.raw -C 0,12345 root_directory_for_new_cd
+
+	replace 0,12345 with your actual wodim -msinfo output.
+
+the image in fs.raw may now be written with wodim as second session.
+
+See my README.multi for more info on how to create multi session CD's
+
+
+The procedure again in short form:
+
+	icedax -vall -B
+
+	wodim -multi -audio audio_tracks ....
+or
+	wodim -dao -useinfo -multi -audio audio_tracks ....
+
+	wodim -msinfo ....
+	(output is e.g. 0,12345)
+
+	genisoimage -R -o cd_plus.raw -C 0,12345 root_dir_of_fs
+
+	wodim -data cd_plus.raw
+or
+	wodim -multi cd_plus.raw
+
+
+Note: If you want to create an HFS hybrid as the data track, then you must
+use the '-part' option to genisoimage. Otherwise, the data track will be mounted
+as an ISO9660/Joliet CD when used on a Mac.
+	
+Jörg
+
+Edited for cdrkit by Christian Fromme <kaner@strace.org> and Eduard Bloch
+
+This describes the programs as shipped with cdrkit, a spinoff from the
+cdrtools project. However, the cdrtools developers are no longer
+involved in the development of this spinoff and therefore shall not
+be made responsible for any problem caused by it. Do not try to get
+support for this program by contacting the original authors.
+
+If you have support questions, send them to
+
+debburn-devel@lists.alioth.debian.org
+
+If you have definitely found a bug, send a mail to this list or to
+
+submit@bugs.debian.org
+
+writing at least a short description into the Subject and "Package: cdrkit" 
+into the first line of the mail body.
diff --git a/doc/READMEs/README.cdtext b/doc/READMEs/README.cdtext
new file mode 100644
index 0000000..33df110
--- /dev/null
+++ b/doc/READMEs/README.cdtext
@@ -0,0 +1,65 @@
+CD-Text Usage (to copy CD-Text from master CD):
+
+	icedax -D 6,0 -vall -B	# To extract audio information
+	wodim dev=6,0 -vv -toc	# To extract CD-Text information
+
+	and then
+
+	wodim dev=6,0 -v -dao textfile=cdtext.dat -useinfo *.wav
+	or
+	wodim dev=6,0 -v -raw96r textfile=cdtext.dat -useinfo *.wav
+
+	If the CD-Text information contains more CRC errors than
+	wodim can correct, you need to reload the CD and to
+	re-read the CD-Text information from the master disk.
+
+	Writing of CD-Text is supported for all drives that support
+	CD-Text in SAO write mode and for all drives that support
+	to write in RAW/RAW96R mode (use -raw96r in this case).
+
+	NOTE: not all writers that support MMC SAO mode support
+		to write CD-Text in this write mode.
+		If you have a drive that does not support CD-Text
+		but supports RAW/RAW96R mode use this mode as
+		in RAW/RAW96R mode the drive does not need to know
+		about CD-Text. This way even old drives like the
+		Plextor PX-R 412C will write CD-Text.
+
+	NOTE that icedax will read CD-Text and fill in the 
+	CD-Text fields in the *.inf files if vou use -vall.
+
+	The new icedax option cddb= allows you to tell icedax to
+	retrieve CDDB information from freedb.freedb.org.
+	cddb=0 means ask if ambiguous, cddb=1 means take first entry.
+	The information in this case is filled into the fields
+	in the *.inf files.
+
+Creating a CD with CD-Text based on CDDB information from freedb.freedb.org:
+
+	Tell icedax to fetch data from freedb.freedb.org, call
+
+	icedax -D 6,0 -vall -B cddb=1	# To extract audio information/fetch CDDB data
+
+	and then call
+
+	wodim dev=6,0 -v -dao -text -useinfo *.wav
+	or
+	wodim dev=6,0 -v -raw96r -text -useinfo *.wav
+
+
+If you like to create your own CD-text data for a CD use the
+following method:
+
+	First extract all tracks with icedax -vall (see above),
+
+	then edit the *.inf Files and add album and song titles.
+
+	Now call wodim as if the *.nf files contain CD-Text 
+	information.
+
+	Note that it is recommended to use less that 160 characters
+	for a single string.
+
+Source: README.cdtext from cdrtools package
+Edited for cdrkit by Christian Fromme <kaner@strace.org> and Eduard Bloch
+
diff --git a/doc/READMEs/README.copy b/doc/READMEs/README.copy
new file mode 100644
index 0000000..dc78169
--- /dev/null
+++ b/doc/READMEs/README.copy
@@ -0,0 +1,53 @@
+Ho to copy CD's and CD-R/CD-RW's
+
+Copying audio CD's:
+
+If you want to copy audio CD's, look for 'icedax'.
+
+Copying data CD's:
+
+The best way to copy a data disk is to copy the raw data on the master CD.
+This may be done by reading the data from the raw device by using 'readom'.
+
+
+NOTE:	All CD-R's written in Track At Once mode end in two unreadable 
+	run-out sectors. If the disk has been written with a Yamaha CD-R100
+	or with a Yamaha CD-R102, there are even more run-out sectors.
+
+For this reason, you will not be able to read such a CD correctly with 'dd'.
+
+I recommend to write all disks in Disk at Once mode if your drive
+is supported in DAO mode with wodim. In addition, you may wish to 
+add padding (see wodim / genisoimage man pages).
+
+If you want to copy such a CD directly with wodim, you may call:
+
+	wodim -v dev=... -isosize /dev/cdrw
+
+But this may fail if the master gives read errors. To copy such a CD to a file
+you may use the program 'readom' from this package
+
+Call 'readom [target] [lun] [scsibusno]' and select function 11.
+Or call readom -help to get alternate usage.
+To prevent readom from reading the run-out sectors, reduce the 
+number of sectors to copy by 2.
+
+Recent readom versions may be called: readom dev=b,t,l f=outfile
+To reduce the numbers of sectors to copy you may use the sectors= option.
+
+If the master disk is made of several partitions (like a Solaris boot CD),
+the best way to copy a CD is to use the program 'readom'. It ignores
+the partition info and does raw SCSI reads.
+
+If you like to copy audio CD's in a way that preserves as much accuracy as
+possible, use:
+
+icedax -vall -D... -B
+wodim -v dev=... -dao -useinfo *.wav
+
+This will preserve pre-gap sizes, indices ...
+
+
+Source: README.copy from cdrtools package, version 2.01.01a08
+Edited for cdrkit by Christian Fromme <kaner@strace.org> and Eduard Bloch <blade@debian.org>
+
diff --git a/doc/READMEs/README.multi b/doc/READMEs/README.multi
new file mode 100644
index 0000000..d7d3457
--- /dev/null
+++ b/doc/READMEs/README.multi
@@ -0,0 +1,209 @@
+Creating multi-session CDs/DVDs Mini Howto FAQ
+
+Multi-session filesystems are a trick that comes from the Kodak photo CD.
+The OS mounts the last session that contains the sum of the current session
+and all previous sessions.
+
+To test (with Linux):
+
+ - create a iso-9660 filesystem image with genisoimage.
+ - genisoimage is included in the cdrkit release.
+ - use the -R flag to add Rock Ridge extensions (this is important).
+
+Assuming that the CD-R drive is connected to target 2 on the SCSI bus.
+
+Write the first session with:
+
+wodim -v speed=2 dev=2,0 -eject -multi isoimage.raw
+
+Note that all Sony drives do no support XA2 disks in firmware - read README.sony
+for more information.
+
+This must be a iso9660 image with Rock Ridge extensions (see above)
+
+Note the number of sectors written and check the disk, it should be mountable.
+
+Next step is to check if wodim is able to retrieve the following data:
+
+	1) The first block (sector) number in the first track of the last session
+	   This must be '0' in our case.
+
+	2) The next writable address in the unwritten session following the current.
+	   This should be the number of sectors written in the first
+	   run + ~ 11400 sectors for about 22MB lead out/in
+
+	   For the first additional session this is 11250 sectors lead-out/lead-in
+	   overhead + 150 sectors for the pre-gap of the first track after the
+	   lead-in = 11400 sectors.
+
+	   For all further session this is 6750 sectors lead-out/lead-in
+	   overhead + 150 sectors for the pre-gap of the first track after the
+	   lead-in = 6900 sectors.
+
+To get this information type:
+
+wodim -msinfo dev=2,0
+
+The output should be two numbers separated by a comma.
+
+	e.g.: 0,204562
+
+The first number is (1), the second number is (2).
+
+2nd session:
+You should create a directory that contains a second directory with data in it
+for this purpose.
+
+	e.g.:
+		first_dir/
+			second_dir/
+				file_1
+				file_2
+				...
+
+call:
+
+On Linux:
+genisoimage -o isoimage_2.raw -R  -C xx,yy -M /dev/cdwriter_blk_dev  first_dir
+
+On SunOS:
+genisoimage -o isoimage_2.raw -R  -C xx,yy -M target,lun first_dir
+
+Note that the name "first_dir" is not important.
+
+If you still keep the old raw image of the first session and there is only
+one previous session on the CD you may also call:
+
+genisoimage -o isoimage_2.raw -R  -C xx,yy -M isoimage.raw first_dir
+
+
+The argument of -C is the output of wodim -msinfo
+-	On Linux, the argument of -M is a device that would allow you to mount 
+	the current CD in the CD-writer
+-	On SunOS, target and lun refer to the SCSI target and lun of the 
+	CD-R device with the same notation as for wodim dev=xxx,yyy .
+
+Note that you can also use the -msifile=... option of wodim to store this data
+in a reliable way. This is usefull for scripting.
+
+If you want to check, whether genisoimage make everything right, you should create 
+another image by using the following command line.
+
+On Linux:
+genisoimage -o isoimage_2.raw -R  -C xx,0 -M /dev/cdwriter_blk_dev  first_dir
+
+On SunOS:
+genisoimage -o isoimage_2.raw -R  -C xx,0 -M target,lun first_dir
+
+Where xx is the first number of the pair returned by wodim -msinfo
+
+You may check ***this** image by mounting it with my "fbk" on Solaris 
+or the loopback driver on Linux.
+
+On Linux type:
+	mount isoimage_2.raw -r -t iso9660 -o loop /mnt
+
+On SunOS type:
+	mount -r -F fbk -o type=hsfs /dev/fbk0:isoimage_3.raw /mnt
+
+For Solaris 8 and later you may also use the Sun lofi driver (see README.sun-lofi)
+
+If you list /mnt, you should see all directories that have been in the first 
+session and the directory "second_dir". If you try to read a file from the
+first session, you will get an I/O error or bad data (depending on the
+block address), don't worry about that. If you try to read a file from
+the second session, you will see everything correctly.
+
+To write the second session to CD, call:
+
+wodim -v speed=2 dev=2,0 -eject -multi isoimage_2.raw
+
+If you mount this CD, you should see the first session and the second directory 
+from 2nd session added to the root directory of the CD.
+
+
+Additional check:
+
+call:
+
+wodim -msinfo dev=2,0
+
+The first number should be the first writable address which was retrieved by the
+first call to wodim -msinfo after creating the first session.
+The second number should be the first number + number of sectors of the second session
++ ~ 11400 sectors.
+
+Note: The first lead-out is 1:30 (6750 sectors) the lead-in is 1:00 (4500 sectors)
+All following sessions need only 0:30 for lead-out (2250 sectors), the lead-in
+is also 1:00. So in theory, the can be 44 sessions on s 74 minute disk if you
+take into account that the minimum track size is 4 seconds.
+
+The total amount of the overhead is 11250 + 150 sectors for the first additional
+session and 6750 + 150 sectors for all subsequent sessions.
+The 150 additional sectors are the pre-gap sectors for the first track after
+the current session.
+
+Some notes on multi-session CD's that contain only Joliet but no Rock Ridge:
+
+Joliet is a really bad idea in general:
+
+-	There is no way to find a relation between a ISO-9660 name and a Joliet
+	name. If the file has a size, you may try to match the starting sector #
+	but if the size in 0 it's impossible.
+
+
+-	Joliet does not allow long filenames (it limits names to 64 chars).
+
+-	Joliet does not allow all (usually used) characters in filenames.
+         
+	All code points between (00)(00) and (00)(1F), inclusive. (Control Characters)
+		(00)(2A) '*'(Asterisk)
+		(00)(2F) '/' (Forward Slash)
+		(00)(3A) ':' (Colon)
+		(00)(3B) ';' (Semicolon)
+		(00)(3F) '?' (Question Mark)
+		(00)(5C) '\' (Backslash) 
+
+	While '/' is not a real problem ;-) other characters may cause trouble.
+ 
+All notes above prevent you from doing reliable multi-session if the CD does
+only contain Joliet but des not contain Rock Ridge attributes.
+
+In addition, please read README.joliet in the genisoimage directory.
+
+This is the answer to a commonly asked question is why can't I continue a
+multisession CD that has been started on a Microsoft system using genisoimage. 
+
+
+Note: It is not possible to create a multi-session HFS CD. If you create
+a multi-session CD using any of the HFS options, then each new HFS
+session will ignore HFS files from any previous sessions. A warning will
+be printed if you attempt this. However, if you use the '-part' option to
+genisoimage for each session you create, then each session will appear as 
+separate volumes when mounted on a Mac. In this case, it is worth using the 
+'-V' or '-hfs-volid' option to give each session a unique volume name,
+otherwise each "volume" will appear on the Desktop with the same name.
+
+
+Joerg Schilling
+
+Edited for cdrkit by Christian Fromme <kaner@strace.org> and Eduard Bloch
+
+
+This describes the programs as shipped with cdrkit, a spinoff from the
+cdrtools project. However, the cdrtools developers are no longer
+involved in the development of this spinoff and therefore shall not
+be made responsible for any problem caused by it. Do not try to get
+support for this program by contacting the original authors.
+
+If you have support questions, send them to
+
+debburn-devel@lists.alioth.debian.org
+
+If you have definitely found a bug, send a mail to this list or to
+
+submit@bugs.debian.org
+
+writing at least a short description into the Subject and "Package: cdrkit" 
+
+
diff --git a/doc/READMEs/README.netscsid b/doc/READMEs/README.netscsid
new file mode 100644
index 0000000..07c3672
--- /dev/null
+++ b/doc/READMEs/README.netscsid
@@ -0,0 +1,145 @@
+The Remote-SCSI protocol gives you SCSI-Anywhere features.
+
+The protocol used by netscsid is based on rscsi from the cdrtools, developed by
+Joerg Schilling. However, no guarantee for the compatibility or reliability can
+be made. This documentation is based on rscsi documentation from Joerg
+Schilling, but is not identical to the original.
+
+There are three possible ways to control access to the remote users:
+
+	-	Let the remote scsi lib log in as a standard user.
+		In this case netscsid will be called via sh -c netscsid /usr/sbin/netscsid
+		NOTE: In this case, netscsid must be installed suid root. 
+		--- This would need to allow any valid local user to access SCSI ----
+		It could be a security problem.
+
+	-	Log in as root and call netscsid via sh -c netscsid
+		NOTE that this will fore you to allow remote logins as root
+		which is considered to be a security hole.
+
+	-	Create one or more special user(s) that have netscsid
+		as login shell with their own home directory.
+		You then may create special .rhosts files for each user.
+		NOTE: In this case, netscsid must be installed suid root. 
+		**** This is the preferred method ****
+
+To enable remote SCSI via the login shell method you should do the following:
+
+  -	Install netscsid into /usr/sbin. It can be set suid-root if neccessary, see
+    security section below.
+
+	-	Install a file /etc/netscsid.conf and define access rights.
+		Without this file, netscsid will not work at all.
+		The template for this file is: netscsid/netscsid.dfl
+ 
+ - For the special user method, create a user account. This can be done with a
+   frontend like adduser or useradd, if available. The user should have /usr/sbin/netscsid as the login shell.
+   If there is no frontend tool, try this:
+
+   +	Add an entry to /etc/passwd in the form:
+
+      netscsid:x:1999:1000:Tape:/home/netscsid:/usr/sbin/netscsid
+
+      (modify this according to your OS). And don't forget to
+      modify /etc/shadow the way it needs to be on your OS.
+
+   +	Create the home directory for this user, adapt the user/group ownership
+      on this directory.
+  
+  - if you use SSH as the login shell (via appropriate RSH environment variable
+    or a symlink to "rsh" which is the case for many Linux distribution),
+    consult the ssh documentation for details.
+    Note that SSH requires sufficiently powered client/server systems to
+    encrypt/decrypt data in realtime.
+
+  - if you use traditional rsh, add a .rhosts file to this directory to allow
+    access to all users you like (see rsh documentation)
+
+NETSCSID Security:
+
+-	When netscsid starts, it checks if /etc/netscsid.conf exists.
+	If not, it dies.
+
+-	If netscsid is not called by a user listed in /etc/netscsid.conf
+	it dies.
+
+-	To access a SCSI target there must be an entry that lists the user
+	rcsi hast been started from, the hostname and the SCSI target.
+
+	netscsid compares the hostname field in /etc/netscsid.conf 
+	to the peername retrived from STDIN:
+
+	- legal host name		IP connection
+	- "ILLEGAL_SOCKET"		Not an IP socket
+	- "NOT_IP"			Not a socket
+
+NETSCSID Security hints:
+
+-	Do not generally allow other users to see your boot disk via NETSCSID.
+  All people who see this disk may edit your passwd file. This especially
+  applies to suid-root usage. For non-suid-root, check the access permissions.
+
+-	If you are in doubt, only export CD-ROM drives, scanners and similar
+	devices that are not directly security sensitive.
+
+If anybody sees a security hole in my security precautions, please send me a mail!
+
+NETSCSID usage:
+
+-	To use remote SCSI devices you need to know how to access a specific remote
+	SCSI target.
+
+	-	dev=REMOTE:host: or dev=REMOTE:host
+		will allow you to do SCSI bus scanning while you log in as yourself
+
+	-	dev=REMOTE:user@host: or dev=REMOTE:user@host
+		will allow you to do SCSI bus scanning while you log in as "user"
+
+		If you use the setup described above, you should use:
+
+			dev=REMOTE:netscsid@babbel:
+
+		to do SCSI Bus scanning on host babbel
+
+	-	To access a specific SCSI device, you must specify
+		dev=REMOTE:host:<target spec> or dev=REMOTE:user@host:<target spec>
+		<target spec> is the SCSI target specification as it is needed
+		on the remote host
+
+			dev=REMOTE:netscsid@babbel:1,3,0
+
+		Will let you log in as netscsid on host babbel and open Target 3 lun 0
+		on SCSI bus #1
+
+	-	If you use wodim -vv ...., wodim will on startup print some 
+		information about the remote libscg version used for the connection.
+
+-	To be able to use the remote SCSI client code from win32 you need to create
+	a file /etc/passwd with a correct entry for the user you are on win32.
+	Call 'id' to get the right user id.
+	Note that remote SCSI has not yet been tested on Win32.
+
+NETSCSID speed:
+
+-	On a Ultra-10 running Solaris 8, the command overhead time is 400 usec.
+	You may achieve up to 9900 kB/s via a 100MB/s ethernet connection
+	between two of such machines.
+
+-	With 100 MB/s, 12x recording should be no problem.
+
+-	With 10 MB/s, 4x recording is the maximum. Do tests before!
+
+-	Logging into a remote machine and running wodim on the remote machine
+	causes the buffer cache on that machine to be trashed. The main user
+	is disturbed.
+
+-	Doing cdrecording via Remote SCSI causes only the netscsid command with less
+	than 200kB to be needed on the remote machine hosting the CD recorder.
+	The main user on that machine is not disturbed.
+	The buffer cache of the machine running wodim is trashed.
+
+-	It is desirable to use a Burn-Proof recorder to make sure that network
+	load will not cause buffer underruns.
+
+
+-	USER= test and test for hostname are using a pattern matcher.
diff --git a/doc/READMEs/README.sony b/doc/READMEs/README.sony
new file mode 100644
index 0000000..3ee6da6
--- /dev/null
+++ b/doc/READMEs/README.sony
@@ -0,0 +1,31 @@
+The Sony CDU-924 was the first drive that has no hardware support
+for CDROM XA2 mode 1. If you want to create a multi session disk,
+you need to switch back to -data (plain CD-ROM)
+
+If you have a Sony drive that gives you problems with multi session disks,
+please always check the following:
+
+	For some Sony drives you may need to call wodim -multi -data
+	if you like to create multi-session CD's.
+
+	Some Sony drives do not allow to write XA2 tracks with
+	hardware support of the drive.
+
+There is currently a bug in the Sony code (for _old_ non MMC drives)
+of wodim that does not allow you to have different track types 
+in one session.
+
+All Sony drives that have CDUxxx type names are _old_ non MMC drives.
+	Here I expect that no XA support is in the firmware.
+
+All Sony drives that have CRXxxx type names are MMC compliant.
+	These drives should support XA-mode2-form1 as it is mandatory with MMC.
+
+NOTE: many HP CD-writers are nased on Sony OEM drives.
+
+
+NOTE: As for 18.5.2001, a fix was introduced that prevented wodim
+	to do multi session with new MMC compliant Sony drives.
+
+---
+Eduard Bloch, based on documentation from Joerg Schilling, cdrtools package 2.01.01a08
diff --git a/doc/READMEs/README.suidroot b/doc/READMEs/README.suidroot
new file mode 100644
index 0000000..b1198d6
--- /dev/null
+++ b/doc/READMEs/README.suidroot
@@ -0,0 +1,29 @@
+
+This is an example of how to install wodim and other cdrkit applications to get
+the root permissions in a safer way.
+
+Usually it is not a good idea to run the applications as root or to
+give users the means to run wodim as root. This gives them an easy way
+to fetch sensitive data by writing it to the disk, or pass arbitrary
+SCSI commands, e.g. formatting a SCSI disk.
+
+This also applies to root-mode wrappers like sudo, they should be used with
+the most possible care.
+
+The alternative way is installing wodim as suid-root application. In this
+mode, wodim checks permission of the device access by comparing the ownership
+of the device node user/group attributes for the real UID/GID of the calling
+user.
+
+To give all user access to use wodim, enter:
+
+   chown root /usr/local/bin/wodim
+   chmod 4711 /usr/local/bin/wodim
+
+To give a restricted group of users access to wodim, add a group
+"cdburners" to your system and add the trusted users to this group.
+Then enter:
+
+   chown root:cdburners /usr/local/bin/wodim
+   chmod 4710 /usr/local/bin/wodim
+
diff --git a/doc/READMEs/README.verify b/doc/READMEs/README.verify
new file mode 100644
index 0000000..28227b7
--- /dev/null
+++ b/doc/READMEs/README.verify
@@ -0,0 +1,75 @@
+Mini-Howto for verifying a selfmade CD
+
+1) verifying the data layer
+
+	To verify if all data on the disk can be read,
+	use SCSI verify. This can be done with the
+	sformat utility.
+
+	use: sformat -verify [target] [lun] [scsibus]
+
+	If the CD-R device is connected to target 2 on SCSI bus 0
+	sformat -verify 2  0
+
+	sformat can be found on ftp://ftp.berlios.de/pub/sformat
+
+	NOTE: Not all CD-ROm drives support verifying
+	NOTE: All TAO tracks end in 2 unreadable run-out sectors
+
+2) verifying the filesystem layer
+
+	A quick check is to mount the CD and to use star to read
+	all files on the filesystem.
+
+	mount -r /dev/cdrom /cdrom      (modify for your OS)
+	cd /cdrom
+	star -cPM . >/dev/null
+
+	If no errors can be found, all files are readable.
+
+	star can be found on ftp://ftp.berlios.de/pub/star
+
+
+	You also may want to compare the filesystem on the CD
+	with the original data. This can be done with star too.
+
+
+	(cd /master_for_cd; star -cPM .)|(cd /cdrom; star -diff -v)
+
+2a) verifying the iso image before creating the CD
+
+	You may check the filesystem image by mounting it with my 
+	"fbk" on Solaris or the loopback driver on Linux.
+
+	On Linux type:
+		mount isoimage.raw -r -t iso9660 -o loop /mnt
+
+	On SunOS type:
+		mount -r -F fbk -o type=hsfs /dev/fbk0:isoimage.raw /mnt
+
+For Solaris 8 and later you may also use the Sun lofi driver (see README.sun-lofi)
+
+	The check the filesystem with:
+
+		(cd /master_for_cd; star -cPM .)|(cd /mnt; star -diff -v)
+
+
+Solaris has a bug with hardlinks. It generates different inode numbers
+for the hardlinks to a file. This makes it impossible for star to 
+check hard links. Use
+
+(cd /master_for_cd; star -cPM .)|(cd /cdrom; star -diff -v diffopts=!hardlink)
+
+in this case.
+
+NOTE: Some operating systems have a read ahead bug that causes I/O errors for
+the last file(s) on a CD. This seems at least to be true for all Linux versions
+and for Solaris 7 FCS. For Solaris 7 there is a patch (107465-02) that you should
+install. This I/O error problem does not occur with DAO disks and with TAO disks
+that have been written with wodim -pad.
+
+Joerg Schilling
+
+Source: README.verify from cdrtools package
+Edited for cdrkit by Christian Fromme <kaner@strace.org> and Eduard Bloch
+